craft-ts-service-migration

Rewrite business logic as craftService({ name, scope }, function* () { ... }) and replace consumption sites with the generated X() helper, typically called as yield* X(...). Remove direct inject(...) and constructor injection from migrated code.

Adapt each Angular or third-party token exactly once with toCraftService({ name, scope, token }), or use the inject option for tokens requiring inject(...) internally. Expose only a narrowed interface rather than passing through the whole Angular service.

Use scope 'toProvide' or 'manuallyProvidedAtRoot' for dependencies provided per feature, route, or test. Keep route-level providers close to the route that owns the instance and re-export cumulative provider names only when child routes need them.

No. After migration, route DI checks should rely on craft service provider names with ProvidedValues set to never. Treat unions of direct Angular tokens in route files as migration debt unless legacy support is explicitly required.

Enable craft-ts/prefer-craft-service to block new @Injectable app services, craft-ts/prefer-craft-http-client for HTTP access, and brand-angular-gen-deps-required with brand-angular-deps-match to keep GenDeps_* aliases current. Route rules cover exception exhaustiveness and DI checks.