migrate-to-craft-ts

Run npx craft-migrate with --project and --root flags, first in --dry-run mode to review diagnostics, then with --write to apply deterministic changes. Afterwards, manually resolve flagged diagnostics for forms, services, and routes, and finish with --check --fail-on-manual.

Convert Signal Forms to a state call piped through craftPipe with insertForm, mapping validators to cRequired, cMaxLength, and other Craft validators. Use insertSelectFormTree and insertFormAttributes for nested fields, and convert submission.action to a tracked mutation with insertFormSubmit.

The codemod rewrites what it can infer, but application services must be authored with craftService and third-party tokens adapted once with toCraftService. Every generated CRAFT_IMPLEMENTATION_REQUIRED companion must be resolved manually.

Manual work includes unresolved route guards, redirects, lazy collections, inherited providers, dynamic routes, async validators converted to query plus cAsyncValidate, and HTTP mutations whose callback lifecycle semantics must be preserved.

Re-run craft-migrate with --check --fail-on-manual, then run targeted tests, lint, application type-check, architecture tests, the full test suite, and a production build. Report each command's exit code separately rather than relying on filtered output.