omnigraph/omnigraph.example.yaml

version: 1

servers:
  prod:
    endpoint: http://127.0.0.1:8080

graphs:
  local:
    storage: ./repo.omni
  dev:
    server: prod
    bearer_token_env: OMNIGRAPH_BEARER_TOKEN

defaults:
  graph: local
  branch: main

query:
  roots:
    - queries
    - .
docs: document V1a config/CLI (version/storage/servers/--graph); mark RFC landed Sweep `--target` → `--graph` across the user docs (cli-reference, cli, server, policy) and update `omnigraph.example.yaml` to the v1 schema (`version: 1`, `storage:`, `servers:`/`server:`). Add the typed-locator schema (version/storage/ servers/graph_id + strictness) to cli-reference, and a server "embedded graphs only" note. The RFC gets an Implementation-status banner recording V1a as landed and its divergences (`--target` removed outright — no alias; `uri:` deprecation- warned) and corrects the stale `QueryRegistry`/config-location claims (it's in `omnigraph-queries` / `omnigraph-config` now). testing.md gains a Config & CLI note. Past release notes keep `--target` (accurate for those versions); `--target-branch` untouched. 2026-06-04 16:22:17 +02:00			`version: 1`

			`servers:`
			`prod:`
			`endpoint: http://127.0.0.1:8080`

example config: use graphs / cli.graph, matching the MR-603 rename The target → graph rename shipped in PR #17 but omnigraph.example.yaml still used the old form (`targets:` / `cli.target`). Since the serde struct uses `rename = "graphs"` without a `targets` alias, the example wouldn't deserialize against current code. Update the example to the new form. No alias is being added — the deserialization error for old configs is loud and clear, which is the better migration signal for a young project. 2026-04-18 23:40:35 +03:00			`graphs:`
Initial public Omnigraph repository 2026-04-10 20:49:41 +03:00			`local:`
docs: document V1a config/CLI (version/storage/servers/--graph); mark RFC landed Sweep `--target` → `--graph` across the user docs (cli-reference, cli, server, policy) and update `omnigraph.example.yaml` to the v1 schema (`version: 1`, `storage:`, `servers:`/`server:`). Add the typed-locator schema (version/storage/ servers/graph_id + strictness) to cli-reference, and a server "embedded graphs only" note. The RFC gets an Implementation-status banner recording V1a as landed and its divergences (`--target` removed outright — no alias; `uri:` deprecation- warned) and corrects the stale `QueryRegistry`/config-location claims (it's in `omnigraph-queries` / `omnigraph-config` now). testing.md gains a Config & CLI note. Past release notes keep `--target` (accurate for those versions); `--target-branch` untouched. 2026-06-04 16:22:17 +02:00			`storage: ./repo.omni`
Initial public Omnigraph repository 2026-04-10 20:49:41 +03:00			`dev:`
docs: document V1a config/CLI (version/storage/servers/--graph); mark RFC landed Sweep `--target` → `--graph` across the user docs (cli-reference, cli, server, policy) and update `omnigraph.example.yaml` to the v1 schema (`version: 1`, `storage:`, `servers:`/`server:`). Add the typed-locator schema (version/storage/ servers/graph_id + strictness) to cli-reference, and a server "embedded graphs only" note. The RFC gets an Implementation-status banner recording V1a as landed and its divergences (`--target` removed outright — no alias; `uri:` deprecation- warned) and corrects the stale `QueryRegistry`/config-location claims (it's in `omnigraph-queries` / `omnigraph-config` now). testing.md gains a Config & CLI note. Past release notes keep `--target` (accurate for those versions); `--target-branch` untouched. 2026-06-04 16:22:17 +02:00			`server: prod`
Initial public Omnigraph repository 2026-04-10 20:49:41 +03:00			`bearer_token_env: OMNIGRAPH_BEARER_TOKEN`

refactor(config,cli): rename the `cli:` config block to `defaults:` under v1 `defaults:` is the canonical CLI/client-defaults block. The legacy spelling `cli:` is accepted as a serde alias and honored under the legacy schema, but rejected under `version: 1` (pointing at the new spelling) and flagged by a deprecation warning. Generalizes the version-gated key scan into `legacy_top_level_keys`, which now drives both the v1 rejection and the legacy warnings via a shared migration-hint table. Renames the config accessors (cli_* -> default_*) and repoints the CLI call sites; migrates the init scaffold, the example config, and the shared test helpers to `defaults:`. 2026-06-04 21:31:38 +02:00			`defaults:`
example config: use graphs / cli.graph, matching the MR-603 rename The target → graph rename shipped in PR #17 but omnigraph.example.yaml still used the old form (`targets:` / `cli.target`). Since the serde struct uses `rename = "graphs"` without a `targets` alias, the example wouldn't deserialize against current code. Update the example to the new form. No alias is being added — the deserialization error for old configs is loud and clear, which is the better migration signal for a young project. 2026-04-18 23:40:35 +03:00			`graph: local`
Initial public Omnigraph repository 2026-04-10 20:49:41 +03:00			`branch: main`

			`query:`
			`roots:`
			`- queries`
			`- .`