refactor(cli): drop cluster init — no replacement scaffold

Andrew's call, and the right one by the repo's own lens: a minimal
cluster.yaml is five lines; a generator is a second copy of the schema to
keep in sync forever, emitting a file that is unusable until hand-edited
anyway (graphs: {} cannot apply or serve). Terraform has no config
scaffolder either. New users copy from the cluster quick-start; migrants
get a ready-to-review cluster.yaml from config migrate. RFC-008 stage 3
becomes purely subtractive.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
aaltshuler 2026-06-11 23:45:18 +03:00
parent 3adbc65af2
commit 5328c91341
5 changed files with 8 additions and 105 deletions

View file

@ -125,9 +125,13 @@ contract), retirement is staged, loud, and tooled:
is the test of the migration map's completeness: any key it cannot
place is a bug in this RFC.
3. **Stop scaffolding** *(landed)*. `omnigraph init` stops generating
`omnigraph.yaml` (it currently scaffolds one into cwd — the source of
the test-pollution bug). `omnigraph cluster init` (new, small) scaffolds
a minimal `cluster.yaml` instead.
`omnigraph.yaml` (it scaffolded one into cwd — the source of the
test-pollution bug). **No replacement scaffold**: a minimal
`cluster.yaml` is five lines; a generator would be a second copy of the
schema to keep in sync, producing a file that is unusable until
hand-edited anyway (Terraform has no config scaffolder either). New
users copy from the cluster quick-start; migrants get a ready-to-review
`cluster.yaml` from `config migrate`.
4. **Opt-in strict.** `OMNIGRAPH_NO_LEGACY_CONFIG=1` turns the warning into
an error — for teams that finished migrating and want regressions caught.
5. **Remove at the next major.** Loading the file becomes an error pointing