Gap: generated projects have no production build target or Dockerfile

Came out of an ideation session, not a scoped request.

A generated project today has `make run` (which shells out to `gonext dev`) and a `docker-compose.yml` that only brings up Postgres. There is no target that produces the deployable artifact and no Dockerfile, so the path from a scaffolded project to something running in production is undocumented — the only place the real build appears is inside the `smoke` target, which builds to `/tmp`.

Surfaced while discussing distribution: the deploy artifact should be a plain binary built from the project's own `main`, with no `gonext` installed on the server.

Start by tracing the generated project's make run and smoke targets, then inspect docker-compose.yml and the project's main entry point. Clarify the production artifact and container workflow before implementing; done means a generated project has a production build path and Dockerfile, with its deployable binary built from its own main.

Written by the indexing model from the issue text.