Description
Add a dry-run mode to the `/build-from-schema` pipeline that previews what would be generated without creating any files.
Why
Users evaluating Nerva or working with complex OpenAPI specs want to preview the pipeline output before committing. A dry-run shows the planned directory structure, file list, database schema, and endpoint inventory — enabling informed decisions before generation begins.
Acceptance Criteria
Example Output
```
Pipeline Dry Run — petstore-api.yaml
Endpoints: 12 (4 resources × 3 CRUD operations)
Database tables: 4 (pets, owners, visits, users)
Auth: JWT (login + refresh endpoints)
Tests: ~48 integration tests (estimated)
Files: 22 files across 6 directories
Resources:
pets → GET /v1/pets, POST /v1/pets, GET /v1/pets/:id, ...
owners → GET /v1/owners, POST /v1/owners, ...
No files were created. Run without --dry-run to generate.
```
Description
Add a dry-run mode to the `/build-from-schema` pipeline that previews what would be generated without creating any files.
Why
Users evaluating Nerva or working with complex OpenAPI specs want to preview the pipeline output before committing. A dry-run shows the planned directory structure, file list, database schema, and endpoint inventory — enabling informed decisions before generation begins.
Acceptance Criteria
Example Output
```
Pipeline Dry Run — petstore-api.yaml
Endpoints: 12 (4 resources × 3 CRUD operations)
Database tables: 4 (pets, owners, visits, users)
Auth: JWT (login + refresh endpoints)
Tests: ~48 integration tests (estimated)
Files: 22 files across 6 directories
Resources:
pets → GET /v1/pets, POST /v1/pets, GET /v1/pets/:id, ...
owners → GET /v1/owners, POST /v1/owners, ...
No files were created. Run without --dry-run to generate.
```