lucca-front-migrate-22

Run the official schematics first (`ng g @lucca-front/ng:palettes` and `ng g @lucca-front/ng:file-upload`), then fix the residual cases: `*-rgb` CSS variables, `$palettesDeprecated` config, ActivityFeed structure, and strict-null TypeScript errors. The Skill guides each step and ends with a validation build and report.

It removes deprecated palettes (grey→neutral, primary/secondary→product, lucca→brand), restructures file upload and ActivityFeed components, moves select panels to ListBox, publishes strictNullChecks type definitions, marks ~360 properties readonly, and converts inputs/outputs/view children to signal APIs.

No. Lucca Front 22 requires Angular 22, and the schematics are not guaranteed compatible with earlier versions. Upgrade Angular first with `ng update @angular/core@22 @angular/cli@22`, then run the Lucca Front migration.

Many LF 22 changes are silent behavior shifts with no compile errors: `canClose` guards wrapped in try/catch, `setValue(null)` ignored on legacy selects, invalid date input no longer triggering validation, and DOM nodes removed by template null-narrowing. These must be audited manually even on non-strict projects.

Mutate instead of reassigning: call `.next()` on Subjects rather than replacing them, or redeclare the property in a subclass with `override`. Only full property substitution from outside a component breaks; method assignment and object mutation still compile.

No. Select panel overrides targeting `.optionItem` and its children are never auto-migrated because the correct replacement depends on the project's real DOM and styles. They are detected and listed in the report (e.g. `.optionItem-value` → `.listboxOption-content`) for the developer to apply.