[OGAR coordination] OGAR Sprint 5–7 will bind NiblePath / Lance versions / manifest-watch

[AdaWorldAPI]

OGAR (AdaWorldAPI/OGAR) is a graph-ontology
project for the ActiveRecord pattern that uses lance-graph as its substrate. This issue
is coordination, not a feature request — documenting which lance-graph APIs OGAR
Sprint 5–7 will bind to, so breaking changes can be coordinated rather than surprise.

API surface OGAR will bind

OGAR Sprint	lance-graph API	Stability needed
5 (lance-graph-contract SoA integration)	NiblePath segment encoding (27-bit identity), LanceDataset::append, versions() watcher	LOCKED
6 (lance-graph-ontology cache)	manifest-watch event API for cache invalidation	LOCKED
7 (lance-graph-callcenter)	dataset transactional commit boundary; tag-based version retention	LOCKED

Specifically interested in

• [spine] Promote TripletGraph + AriGraph tissue to contract surface; add Spine trait #331 (Spine surface for TripletGraph + AriGraph) — would be consumed by Sprint 5/6 if landed
• Wire Cypher IR -> DataFusion plan execution last mile (read-only) #332 (Cypher IR → DataFusion plan execution) — integrates with lance-graph-planner (Sprint 6)
• unified-bridge crate scaffold: registry + projection orchestrator for Spine impls #333 (unified-bridge crate scaffold) — directly adjacent to OGAR's adapter layer

Coordination convention

OGAR maintains docs/UPSTREAM-DEPS.md
as the single source of truth on cross-repo dependencies. When lance-graph plans a
change that touches the OGAR-bound surface, please cross-reference here so OGAR can
schedule the migration as a follow-up Sprint rather than a blocker.

OGAR's relevant carve-outs

• docs/SOA-IMPLEMENTATION.md — four-layer SoA stack (lance-graph being Layer 0+1)
• docs/IDENTITY-MAPPING.md — identity-string grammar (NiblePath consumer side)
• .claude/PLAN.md Sprint 5/6/7

No action requested — coordination visibility only. Close at will once acknowledged.