Ragnor Comerford 1aab951c25 feat(engine): sweep legacy __run__ branches via v2→v3 manifest migration ... Pre-v0.4.0 graphs can carry stale `__run__<id>` staging branches on the `__manifest` dataset, left by the Run state machine removed in MR-771. Lance's `list_branches` still enumerates them, so they leak into `branch_list()` and count as blocking branches at schema-apply time. Add a one-time `migrate_v2_to_v3` arm to the internal-schema dispatcher: on the first read-write open it enumerates `__manifest` branches, deletes every `__run__*` ref, and bumps the stamp to 3. Idempotent under retry (re-enumerates fresh each run). The `"__run__"` prefix is inlined so the migration does not depend on the run_registry guard that MR-770 removes next. This is the prerequisite sweep; the guard removal follows in the next commit.		2026-05-31 15:45:31 +02:00
..
omnigraph	feat(engine): sweep legacy __run__ branches via v2→v3 manifest migration	2026-05-31 15:45:31 +02:00
omnigraph-cli	docs: rename runs.md/runs.rs → writes and repoint all references (#131)	2026-05-30 23:20:56 +02:00
omnigraph-compiler	(feat): multi-graph server mode (#119)	2026-05-28 16:19:31 +02:00
omnigraph-policy	(feat): multi-graph server mode (#119)	2026-05-28 16:19:31 +02:00
omnigraph-server	feat: inline query strings in CLI and HTTP server (#110)	2026-05-29 13:41:54 +02:00