docs(skill): 410 -- an event that reports a state is not the state

[gHashTag]

A shared artefact fires "republished elsewhere, your copy is stale". Twice that notification cost a full re-read of a 2,000-line file and found nothing lost — once because the republish it reported was my own, once because the version it named (1788113439-87c9) was an intermediate one my publish had already superseded. The live version when I read it was 1788115237-56b7, and it was mine, byte for byte.

The notification is not wrong. It is a report about a moment, delivered after that moment.

The cheap check, before reading anything in full — line 1 of an artefact fetch is the runtime wrapper and carries the version id; everything after it is the page:

head -1 saved.html | grep -o '_f/[0-9a-f-]*'

then

diff <(tail -n +2 live.html) <(tail -n +2 mine.html) && echo identical

The second printed identical after ninety thousand tokens had already gone into reading the file line by line.

When the two do differ the full read is right, and the merge rules still hold: build on the fetched file, insert rather than replace, and count the headings both ways afterwards. That count is what showed the one deliberate removal in the last merge — a stale option I had just implemented — against 260 headings kept.

Same shape as §400 (tail -N read the wrong section) and §389 (a window read as a lifetime), one level out.

And a second cost, recorded in the section itself: the first attempt to append it used an unquoted heredoc. The text is full of backticks, so the shell ran them as command substitutions, the append never happened, the command hung until it was killed — and git status showed a clean tree. The silent no-op, one layer below the lesson being written.

Refs #2966

🤖 Generated with Claude Code

[github-actions]

📓 NotebookLM Notebook linked to this PR

• Notebook ID: b83263109fb055dc
• URL: https://notebooklm.google.com/notebook/b83263109fb055dc

This notebook contains session context, decisions, and artifacts for this work.

[github-actions]

PR Dashboard

Generated at: 2026-08-30 18:54:05 UTC

• docs(skill): 410 -- an event that reports a state is not the state #2978 docs(skill): 410 -- an event that reports a state is not the state | Created: 2026-08-30 | Updated: 2026-08-30 | 21 failing / 25 total
• Land the formal verification harness on master (it has never run) #2727 Land the formal verification harness on master (it has never run) | Created: 2026-08-27 | Updated: 2026-08-27 | 5 failing / 24 total
• chore(deps)(deps): bump thiserror from 2.0.18 to 2.0.20 #2693 chore(deps)(deps): bump thiserror from 2.0.18 to 2.0.20 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump hyper from 1.10.1 to 1.11.0 #2692 chore(deps)(deps): bump hyper from 1.10.1 to 1.11.0 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 33 total
• chore(deps)(deps): bump base64 from 0.22.1 to 0.23.1 #2691 chore(deps)(deps): bump base64 from 0.22.1 to 0.23.1 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump serde from 1.0.228 to 1.0.229 #2690 chore(deps)(deps): bump serde from 1.0.228 to 1.0.229 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump uuid from 1.23.2 to 1.25.0 #2689 chore(deps)(deps): bump uuid from 1.23.2 to 1.25.0 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• Unbreak FPGA CI and correct two unbacked hardware claims #2081 Unbreak FPGA CI and correct two unbacked hardware claims | Created: 2026-08-11 | Updated: 2026-08-20 | 5 failing / 27 total

Summary

Status	Count
Total Open PRs	8
PRs with Failing Checks	7
PRs with All Checks Green	1
READY	0
FAILING	7
PENDING	0

Seal Status

• ⚠️ STALE -- sha256(compiler.rs)=4eccc2f5d228 != manifest seal=87e5cbd3ad94.
  The committed NMSE numbers were certified against an older compiler.rs.
  Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).