neuwirth
/
pmacs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(lane): stop the checkpoint from certifying itself 

Name f441d3d as the latest verified code head, not the lane's current
head. The documentation commit carrying that old wording made it false
on arrival.

Keep the authoritative remote ref as the recovery source so later
documentation-only commits need no self-referential SHA update.
This commit is contained in:
Levi Neuwirth 2026-09-01 21:10:32 +02:00
parent 4e6ca51607
commit 2a90aa2a7a
No known key found for this signature in database
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/active-work.md
View File

@ -347,9 +347,12 @@ At `175cc7b` — B5's own checkpoint, not the lane's current one — all
fmt and `git diff --check` are clean. Four mutations were executed and
each fires its named row: omit accepted-frame reflow, omit
epoch-invalidation reflow, reshape content-only frames, and retain
divider hover on `Absent`. **The lane's current head is `f441d3d` at
312 GPU rows**; recover from the authoritative remote ref above, not
from this commit.
divider hover on `Absent`. **The latest verified code head is `f441d3d`
at 312 GPU rows**; the authoritative remote ref above may be ahead with
documentation-only commits and remains the recovery source. Calling
`f441d3d` the lane's "current head" here would become false in the
commit carrying the sentence — the self-certifying checkpoint defect
this ledger has already recorded elsewhere.
**Landed but NOT yet witnessed** — recovery needs this split, because
"L1–L8 owed" reads as though none of the mechanism exists: