Decide standalone-component lint policy for legacy NgModules

[fpigeonjr]

Parent

#580

What to build

Decide and document how the Angular prefer-standalone recommendation applies to this raw-source library and its legacy NgModule consumers. Based on that decision, either define a safe standalone migration path or explicitly configure the rule exception so the 194 current findings do not remain unactionable warnings.

This is a human-in-the-loop architecture decision because changing component standalone semantics may affect the repository's frozen deep-import and consumer-compiled contracts.

Acceptance criteria

• Current consumer and NgModule constraints are evaluated
• The decision to migrate, defer, or disable prefer-standalone is documented with rationale
• If migrating, the work is split into consumer-safe implementation slices
• If deferring or disabling, the ESLint configuration records the intentional exception
• No unactionable prefer-standalone warnings remain in the lint baseline

Blocked by

• Guard the ESLint warning baseline against regressions #581