omnigraph/crates/omnigraph-cli/tests
aaltshuler 4c50170c77 feat(config): OMNIGRAPH_NO_LEGACY_CONFIG strict mode (RFC-008 stage 4)
Opt-in: with the env set, loading a legacy omnigraph.yaml is a hard
error pointing at config migrate — the regression guard for migrated
teams (a stray legacy file would otherwise silently outrank operator
config during the window) and the rehearsal for stage 5's removal.
Strict refuses the FILE, never its absence: flag-less invocations on
migrated setups are untouched. Inert unless set.

The RFC's stages-1-3-then-4 release gap collapsed honestly: no version
boundary was crossed between them, so all four ship in the same release
(noted in the RFC).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-06-12 00:03:10 +03:00
..
support feat(cli): keyed credentials — servers:, the token chain, login/logout (RFC-007 PR 2) 2026-06-11 21:24:51 +03:00
cli_cluster.rs refactor(cli): drop cluster init — no replacement scaffold 2026-06-11 23:45:18 +03:00
cli_cluster_e2e.rs refactor(cli): split the test monolith into command-area suites 2026-06-11 15:16:51 +03:00
cli_data.rs feat(cli): the operator config surface — identity and output defaults (RFC-007 PR 1) 2026-06-11 20:29:02 +03:00
cli_queries.rs refactor(cli): split the test monolith into command-area suites 2026-06-11 15:16:51 +03:00
cli_schema_config.rs feat(config): OMNIGRAPH_NO_LEGACY_CONFIG strict mode (RFC-008 stage 4) 2026-06-12 00:03:10 +03:00
system_local.rs feat(cli): operator aliases — pure bindings invoking stored queries (RFC-007 PR 3, part 2) 2026-06-11 22:25:42 +03:00
system_remote.rs feat(cli)!: unified load command; deprecate ingest as an alias 2026-06-11 04:18:00 +03:00