docs(board): E-LANCE7-OBJECTSTORE-SURREALDB + TD-SURREALDB-KVLANCE-LANCE7

Board hygiene for the lance 6→7 / lancedb 0.29→0.30 bump (a07fe26):
- EPIPHANIES: the object_store 0.12→0.13 alignment finding — the surrealdb
  fork's kv-lance =6.0.0 pins were already contradictory with its own
  object_store 0.13, so lance 7 is a coherence fix, not a version chase.
- TECH_DEBT: TD-SURREALDB-KVLANCE-LANCE7 — surrealdb-core kv-lance still on
  =6.0.0/=0.29.0; paid by the companion adaworldapi/surrealdb PR.

https://claude.ai/code/session_012SorR8UbtEvYmbX8cXftj7

Author: claude

.claude/board/EPIPHANIES.md

@@ -864,6 +864,13 @@ AriGraph (`crates/lance-graph/src/graph/arigraph/`) is almost entirely standalon
 - **SPO-vocabulary debt (extends F-WIRE-DTO-DUP-MAP):** ≥4 parallel SPO-triple types (AriGraph `TripletGraph`, `ruff_spo_triplet::Triple`, `odoo_ontology::OntologyTriple`, aerial `CandidateTriple`, osint `extractor::Triplet`) — "one SoA never transformed" wants ONE; unification is the convergence work.
 - **class_id landing (shipping now):** the SoA's class discriminator IS the existing `entity_type: [u16; N]` (= OGIT `EntityTypeId`); expose it as `MailboxSoaView::class_id()` (N1 freeze hook). Metadata resolves one layer up via `lance-graph-ontology::OntologyRegistry` (perf gap: add O(1) `by_entity_type_id` index; today O(n) `enumerate_first_with_entity_type_id`).
 **Cross-ref:** `aerial-arm-ruff-spo-codegen-synergies.md`; `splat-codebook-aerial-wikidata-compression.md`; cognitive-risc-{core,classes,faiss-homology}; PR #437 `MailboxSoaView`.
+## 2026-05-31 — E-LANCE7-OBJECTSTORE-SURREALDB — the lance 6→7 bump is what *aligns* object_store with the surrealdb fork; the fork's `kv-lance` `=6.0.0` pins were already self-contradictory against its own object_store 0.13
+
+**Status:** FINDING (deps; verified against crates.io dep graphs + a lock-only `cargo update`, no compile). User directive: "let's do 7 + 0.3 but we need to test surrealdb."
+
+Bumping lance `=6.0.0 → =7.0.0` + lancedb `=0.29.0 → =0.30.0` (lockstep, 7 crates) looked like "ride the head" — but **testing surrealdb showed it's a *coherence fix*, not a version chase.** The AdaWorldAPI/surrealdb fork's `surrealdb-core` declares `kv-lance = ["dep:lance", "dep:lance-index", "dep:lancedb", …]` with `lance / lance-index = "=6.0.0"` + `lancedb = "=0.29.0"`, **yet its workspace already runs `object_store = "0.13.0"`.** The contradiction: lance 6.0.x requires `object_store ^0.12.3`; only lance 7.0.0 moves to `^0.13.2`. So the fork's `=6.0.0` pins could never coexist with its own object_store 0.13 — **the fork is already shaped for lance 7.**
+
+Evidence (crates.io dep API + lock-only resolve): lancedb `0.29.0 → lance =6.0.0`, `0.30.0 → lance =7.0.0` (no lancedb release ever pinned `=6.0.1` — kills the old TD-LANCE-6.0.1-PIN path); lance 6.0.x → `object_store ^0.12.3`, lance 7.0.0 → `^0.13.2`; resolved lock = lance 7.0.0 / lancedb 0.30.0 / object_store 0.13.2 / arrow 58.3.0 / datafusion 53.1.0 (arrow + datafusion **unchanged** across 6→7). **Lesson: a "test the integration" instinct caught a latent diamond the dep-version-only view missed — `object_store`, not `lance`, was the real coupling.** lance-7 API-level compile is unverified in-sandbox (no `protoc`; lance-encoding build-dep) → CI gates it. Cross-ref: TECH_DEBT TD-SURREALDB-KVLANCE-LANCE7; root `Cargo.toml` RESOLVED(A2/B2); PR #445 (lance-graph), companion PR on adaworldapi/surrealdb.
 
 ---
 

.claude/board/TECH_DEBT.md

@@ -41,6 +41,26 @@ ships; they bite only at the deferred 115M streaming load:
 Cross-ref: #442, #441 (StructuralSignature/ClassView), the D-ARM-14 review, `wikidata-hhtl-load.md`,
 FINDING D-CLS↔D-ARM-14 (EPIPHANIES).
 
+---
+
+### TD-SURREALDB-KVLANCE-LANCE7 (deps — surrealdb-core still pins lance =6.0.0)
+
+**Status: Open.** The 2026-05-31 lance `6.0.0 → =7.0.0` / lancedb `0.29.0 →
+=0.30.0` bump (lance-graph, `claude/jolly-cori-clnf9` → PR #445) moved this
+workspace's `object_store` transitive `0.12 → 0.13.2`. The AdaWorldAPI/surrealdb
+fork's `surrealdb-core` already runs `object_store = "0.13.0"`, but its
+`kv-lance` feature STILL pins `lance = "=6.0.0"`, `lance-index = "=6.0.0"`,
+`lancedb = "=0.29.0"` — which require object_store 0.12, a latent contradiction
+with the fork's own 0.13. Until those three pins move to 7.0.0/0.30.0 the
+`kv-lance` storage engine cannot resolve against this workspace (`=6.0.0` vs
+`=7.0.0` exact-equals). **Paid by** the companion PR on adaworldapi/surrealdb
+(branch `claude/jolly-cori-clnf9`) bumping `surrealdb/core/Cargo.toml`. Cross-ref:
+EPIPHANIES E-LANCE7-OBJECTSTORE-SURREALDB; root `Cargo.toml` RESOLVED(A2/B2).
+(The earlier `TD-LANCE-6.0.1-PIN` — only ever a root Cargo.toml comment, never a
+row here — is moot: no lancedb pinned lance `=6.0.1`; `0.30.0 → 7.0.0` superseded it.)
+
+---
+
 ### TD-ARM-CARRIER-FORK (D-ARM-13 / streaming-arm-nars-discovery-v1)
 
 **Status: Open.** Surfaced by the 3-savant brutal review of D-ARM-13