Name provider context by arrival order

notes/conceptual-substitution-audit-2026-07-12.md

@@ -948,6 +948,12 @@ and JSON surface: provider-derived IDs use `arrival_latest_*` and
 while locally ordered Imagination consensus retains its legitimate `latest`
 name.
 
+`EpiphanyCultMeshContext` now completes the correction: its five provider
+mirror fields use `arrival_latest_bifrost_*`, and prompt-context plus Verse
+consumers read those names directly. The only remaining Bifrost `LATEST_KEY`
+identifiers describe persisted `/latest` compatibility keys, not chronology
+claims in typed runtime state.
+
 The same inspection found 33 consecutive duplicate `#[cfg(test)]` attributes
 on provider constructors/writers and their re-exports. One gate already makes
 each item test-only; the second owned nothing. The duplicates are removed.

notes/fresh-workspace-handoff.md

@@ -292,6 +292,8 @@ persisted `/latest` key spelling is retained as external storage compatibility,
 not interpreted as provider chronology.
 The Bifrost ledger report also uses `arrival_latest_*` typed fields and
 `arrivalLatestBifrost*` JSON keys; no old report aliases remain.
+`EpiphanyCultMeshContext`, prompt assembly, and Verse consumers now also use
+`arrival_latest_bifrost_*`; only persisted key constants retain `LATEST_KEY`.
 
 The latest structural count is 32 closure family branches, 744 remaining
 substring assertions in the closure region, and 1,284 lines in