Fix SQLite bounded adjacency prefix parity

CHANGELOG.md

@@ -2,6 +2,12 @@
 
 ## Unreleased
 
+- Make bounded JSON and SQLite adjacency queries retain the same canonical
+  edge-ID prefix before heuristic filtering. New store snapshots advertise the
+  edge-ordered adjacency capability; older sidecars remain valid recovery
+  inputs but directional store queries fail with an explicit rebuild
+  instruction instead of returning a backend-dependent truncated subset.
+
 - Refactor universal language metadata around `UniversalEvidenceProducer` and
   `UniversalEvidencePipeline`. `UniversalCandidate`/`UniversalComplete` are
   now the clearer lifecycle states `Qualifying`/`Qualified`; the serialized

COMPATIBILITY.md

@@ -647,6 +647,14 @@ stream graph and database digests through fixed-size buffers and traverse the
 reachable immutable tree objects with bounded cache and path memory; they do
 not depend on the whole-JSON reader limit.
 
+Directional adjacency indexes advertise an edge-ID-order capability. Bounded
+JSON and store queries select the same canonical edge-ID prefix across the
+requested relationship kinds before applying heuristic filtering. A sidecar
+without that capability remains available for validation, backup, JSON export,
+and recovery, but directional store queries reject it with a rebuild
+instruction; they never reinterpret endpoint-ordered keys as edge-ordered
+results.
+
 The hard-cut boundary is the sidecar and all disposable indexes. When a
 physical format is invalid or outside the support window, preserve
 `graph.json`, run `scripts/rebuild_compass_store.sh`, or explicitly select

MIGRATION.md

@@ -5,6 +5,26 @@ sidecars. Its output root now preserves the familiar flat artifact shape so
 file-based workflows can transition while Compass's snapshot and store
 layout remains visible and clearly owned.
 
+## Rebuild SQLite adjacency sidecars
+
+Store snapshots now declare edge-ID-ordered directional adjacency so bounded
+JSON and SQLite queries retain the same canonical edge prefix. Existing
+`graph.json` artifacts remain compatible. A SQLite sidecar created before this
+capability can still be validated, backed up, and used to recover canonical
+JSON, but directional store queries reject it with
+`edge_id_ordered_adjacency_unavailable`.
+
+Preserve `graph.json`, then rebuild the disposable sidecar with:
+
+```bash
+compass update --force --store sqlite
+compass store validate compass-out --format json
+```
+
+Use `--engine json` until the rebuild completes. Do not edit or copy SQLite
+tables to add the capability marker; the directional index key order must be
+rebuilt from the validated graph.
+
 ## Frontend graph vocabulary
 
 Recent pre-release builds can add React-oriented `renders` edges and UI/server