GameCult/Epiphany
Archived
Watch
9
0
Fork
You've already forked Epiphany
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Load runtime state before frontier repair

Browse source
This commit is contained in:
Meta Vens 2026-08-08 12:36:03 +01:00
commit f7bcb8ed8a
4 changed files with 16 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

15
notes/fresh-workspace-handoff.md
View file

@ -80,14 +80,15 @@ live v53 plan with explicit supervisor command/admission provenance, derive a
fresh route, replay the exact Hands receipts against that amended route, and
retry Soul. Preserve the original route and every failed Soul launch.
The repair pass is pushed at `12c8241b`. Its read-only route inspection then
found a new live discrepancy before mutation: current source enumerates zero
persisted `RepoFrontierRoute` entries in v53, although coordinator status still
derives `launchVerification` and the accepted gate artifact cites route
The repair pass is pushed at `12c8241b`. The apparent missing-route discrepancy
was local to the new inspector and amendment path: each registered the runtime
store but omitted `pull_all_backing_stores` before typed reads. After restoring
that load, the live typed route decodes exactly as
`repo-frontier-route-fb206aaa609246becc17243c0ac5d98d2e70e30fd1dd3351467885ea6ca88dc2`.
No amendment was attempted. Trace the route write/schema-catalog path and restore
typed route visibility before using the repair command; do not reconstruct
authority from the old JSON artifact.
Its original action is `propose-native-frontier-route-document-chain`; its
original command is the planning sentence beginning `Draft one reviewable
frontier-route plan candidate...`, proving the plan-to-Hands authority defect.
No amendment has yet been attempted.
Build iteration is also an active architectural defect: a tiny
`runtime_spine.rs` diagnostic edit forced 18-29 second debug rebuilds, while