apunkt/omnigraph
1
0
Fork 0
mirror of https://github.com/ModernRelay/omnigraph.git synced 2026-06-24 02:38:06 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

docs(dev): update coherence ledger — cookbooks drift resolved, omnigraph-ts mechanism (#294)
Some checks failed
CI / Classify Changes (push) Has been cancelled
Details
CI / Check AGENTS.md Links (push) Has been cancelled
Details
CI / Container Entrypoint (push) Has been cancelled
Details
Release Edge / Prepare edge release (push) Has been cancelled
Details
CI / Test Workspace (push) Has been cancelled
Details
CI / Test omnigraph-server --features aws (push) Has been cancelled
Details
CI / RustFS S3 Integration (push) Has been cancelled
Details
Release Edge / Build edge omnigraph-linux-x86_64 (push) Has been cancelled
Details
Release Edge / Build edge omnigraph-macos-arm64 (push) Has been cancelled
Details
Release Edge / Build edge omnigraph-windows-x86_64 (push) Has been cancelled
Details
Release Edge / Smoke Windows installer (push) Has been cancelled
Details

Browse source 
- omnigraph-cookbooks `bearer_token_env` chain: RESOLVED by cookbooks PR #26
  (deleted docs/best-practices.md in the 0.7 restructure).
- omnigraph-ts catalog `mcp.expose` description: documented why there is no
  hand-fix — the SDK syncs openapi.json from a *tagged* omnigraph release, and
  the fix landed on main after the v0.7.1 tag, so it flows in on the next SDK
  version bump (v0.7.2+) rather than an out-of-band patch.


Claude-Session: https://claude.ai/code/session_01FQ1Hf4eXLsJmeLUkTYBEw7

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Andrew Altshuler 2026-06-21 00:11:48 +03:00 • committed by GitHub
parent 9c792649e2
commit fff441196c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 13 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

24
docs/dev/docs-issues.md
View file

@ -40,17 +40,19 @@ fixed. Branch `docs/user-coherence-0-7-1`.
`apply_schema_update_and_dependent_query_in_one_run`,
`apply_blocks_graph_delete_without_approval`). Update these comments in a
cluster-crate change.
- **Cross-repo drift from this sweep** (separate repos — track here, fix in a
follow-up in each repo):
- `omnigraph-ts` SDK ships a stale generated `spec/openapi.json` +
`packages/sdk/src/generated/types.gen.ts` still describing the `GET /queries`
catalog as the `mcp.expose` subset. Regenerate from this repo's
`openapi.json` once the SDK's deferred refresh happens (the SDK is known to
lag the API by design).
- `omnigraph-cookbooks/docs/best-practices.md` (~line 372) still describes
client-side auth as resolving through the removed `bearer_token_env` chain.
Update to the keyed-credential model (`OMNIGRAPH_TOKEN_<NAME>` →
credentials file → `OMNIGRAPH_BEARER_TOKEN`).
- **Cross-repo drift from this sweep** (separate repos):
- `omnigraph-ts` SDK — its generated `spec/openapi.json` +
`packages/sdk/src/generated/types.gen.ts` still describe the `GET /queries`
catalog as the `mcp.expose` subset. **No hand-fix:** the SDK's
`scripts/sync-spec.ts` pulls openapi.json from a *tagged* omnigraph release
(`/omnigraph/v{version}/openapi.json`), and the catalog fix landed on main
*after* the v0.7.1 tag — so it is in no tag yet and a hand-edit would be
overwritten on the next sync. It flows in automatically when the SDK bumps
to a tag containing the fix (v0.7.2+). Tracked, not actioned.
- `omnigraph-cookbooks/docs/best-practices.md` `bearer_token_env` chain —
**RESOLVED** by omnigraph-cookbooks PR #26 (2026-06-21), which deleted
`docs/best-practices.md` as part of the 0.7 restructure; the stale chain
survives nowhere on `main`.
## Verification checklist (re-run on the next docs audit)