apunkt/omnigraph
1
0
Fork 0
mirror of https://github.com/ModernRelay/omnigraph.git synced 2026-06-12 01:45:14 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 5

docs(cli): config migrate, cluster init, the legacy-file deprecation notice

Browse source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
aaltshuler 2026-06-11 23:37:12 +03:00
parent 5ba9656666
commit 3adbc65af2
2 changed files with 12 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/dev/rfc-008-deprecate-omnigraph-yaml.md
View file

@ -112,19 +112,19 @@ Two placements worth defending:
Per Hyrum's Law (the repo's own deny-list: shipped observable behavior is
contract), retirement is staged, loud, and tooled:
1. **Warn.** Loading `omnigraph.yaml` emits a one-line deprecation notice
1. **Warn** *(landed)*. Loading `omnigraph.yaml` emits a one-line deprecation notice
naming the replacement for each key actually present in the file (not a
generic banner — the migration map above, applied to *your* file).
Suppressible per-process (`OMNIGRAPH_SUPPRESS_YAML_DEPRECATION=1`) for
CI logs during the window.
2. **Migrate.** `omnigraph config migrate` reads an existing
2. **Migrate** *(landed)*. `omnigraph config migrate` reads an existing
`omnigraph.yaml` and writes the split: the team half as a ready-to-review
`cluster.yaml` (+ moves query/policy files into the checkout layout),
the personal half merged into `~/.omnigraph/config.yaml` — printing a
diff-style summary and touching nothing without `--write`. The command
is the test of the migration map's completeness: any key it cannot
place is a bug in this RFC.
3. **Stop scaffolding.** `omnigraph init` stops generating
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.