fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

method: marking a live row stale; and a quoted heading duplicates an anchor

Browse Source 
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
This commit is contained in:
sylph-decoder
2026-08-30 23:58:14 +00:00
parent 549f5b520b
commit fb6291ffb8
1 changed files with 32 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
docs/re/METHOD.md
View File

@@ -2638,3 +2638,35 @@ negative about the SUBJECT**: `Static.slb` carries no `RIFF`/`seek`/`WAVE`
delimiters, so it resists *static scanning* — which is why the extraction had to be
dynamic, not why the audio was unavailable. The page said both, in two places, and
the wrong one was the heading.
## Marking a live row stale is the same error as leaving a stale one live
Having just audited my own index for stale rows, I told `sylpheed-port` that two of
their `BLOCKED.md` rows were stale. **One was. The other was not** — it reads
*"🟡 (a) ANSWERED, (b) still open"* and cites the question it is carrying, and (b)
is genuinely open. I had matched on the **emoji** and inferred a status without
reading the clause, which is exactly the failure the audit existed to catch, run in
the opposite direction and against someone else's file.
📌 They disagreed in the open rather than accepting it, which is the behaviour that
protects a shared record: **a correction accepted out of politeness puts a false
marker on a good row**, and a false "superseded" is harder to detect later than a
stale row, because nobody re-checks something already marked handled.
⚠️ Note the asymmetry in cost. A stale row wastes a run. A wrongly-superseded row
**removes a live question from both agents' view** — and the row was in the file
whose whole job is to say what is still open.
## A forward marker that quotes a heading duplicates it — and a duplicate disarms a check
I added supersession markers to `HANDOFF.md` because a newest-first document reads
correctly top-down and misleads anyone arriving by grep. The marker quoted the
superseded section's replacement **verbatim**, so that sentence then appeared twice
in the file. `sylpheed-port`'s `contract-check` perturbs the **first** occurrence of
an anchor to prove the check can fail; with a duplicate present it read the
untouched copy and **passed a wrong contract**.
📌 **A duplicated sentence is enough to disarm a check without either agent touching
a checked value** — and this one was created by the fix for a different navigation
problem. Forward markers here now name their target by **date and subject** rather
than reproducing its heading.