feat: per-entity http flag to suppress the generated controller (#93)

[cultron]

Closes #93.

Adds a per-entity http flag (with optional top-level default) that suppresses the generated HTTP controller for an entity while keeping everything else — so a hand-written controller can own the route without a collision with the generated CRUD.

{ "name": "Product", "http": false, "fields": [ /* … */ ] }

When http resolves to false (entity.http ?? <top-level http> ?? true), the generator:

• still emits the entity, service, DTOs, and module — the module keeps TypeOrmModule.forFeature([Entity]) + the service provider/exports (so @InjectRepository and the service stay available);
• omits the controller: it doesn't generate the *.controller.ts/*.controller.spec.ts files and drops the controller import + controllers: [] entry from the module.

REST only — GraphQL uses resolvers, so the flag doesn't apply there.

Changes

• Entity.http + top-level http default (types, parser, GeneratorConfig).
• generate.ts computes the effective flag per entity, skips generateController, and passes includeController to generateModule.
• module-rest.eta conditionalizes the controller import + controllers: [].
• MCP schema reference documents http.

Verification

• E2E: an http: false entity generates entity/service/DTOs/module (with forFeature + service, no controller import / controllers:), while a default entity keeps its controller.
• Build clean · lint 0 errors · jest 16/16 in the generator suite, 184 total (excl. pre-existing pglite/migrate).

Note: merging to main auto-publishes a new @apso/cli (the push-to-main release workflow).

🤖 Generated with Claude Code