Published CLI scaffolds broken TypeScript project: v2 template deps + v1 generator imports

[cultron]

Repro (observed on 0.19.0): apso init --language typescript --skip-platform clones service-template-ts, whose package.json references @apso/crud* as file:../apso-crud — unresolvable outside the monorepo. apso generate then emits @nestjsx/crud imports. Result: 24 TS compile errors on a fresh scaffold.

Fix shipped in the local checkout (template.ts pinning apsoai/service-template for typescript) but hadn't been published at the time. Verify current npm release scaffolds a compiling project; add a smoke test that scaffolds + compiles in CI.

[cultron]

apso-overnight-2: addressed in PR #105 (scaffold-smoke.sh + scaffold-smoke.yml).

Verified current state: a fresh `apso init --language typescript` clones `service-template-ts`, whose package.json still pins `@apso/crud* = file:../apso-crud` (unresolvable outside the monorepo; `@apso/crud` remains E404 on npm as of 2026-07-28). `tsc --noEmit` on the scaffold fails with 11 errors (TS2307 cannot find @apso/crud). So the scaffold does NOT compile yet.

The smoke workflow is intentionally `workflow_dispatch` + weekly schedule, not a `pull_request` gate, so it doesn't red every PR while that's true. Flip the trigger to `pull_request` once the template target is resolved (see #99 / publishing @apso/crud) — at that point this becomes the real regression gate this issue asks for.