From d38adcf64a8cb52a9f45ebc9108429fe313e8cef Mon Sep 17 00:00:00 2001 From: sylph-decoder Date: Sun, 30 Aug 2026 23:57:44 +0000 Subject: [PATCH] handoff: stop the forward markers duplicating headings -- a duplicate disarmed a check sylpheed-port's contract-check perturbs the FIRST occurrence of an anchor. My supersession marker quoted the 'EXTRAS resets, the main menu persists' heading verbatim, so the sentence appeared twice and the control read the untouched duplicate and passed a wrong contract. The marker existed because they had told me a grep lands mid-document, so the fix for one navigation problem created another. Pointers now name their targets by date and subject instead of reproducing the heading. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v --- docs/port/HANDOFF.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/docs/port/HANDOFF.md b/docs/port/HANDOFF.md index 330f39d8..3fb2706f 100644 --- a/docs/port/HANDOFF.md +++ b/docs/port/HANDOFF.md @@ -133,13 +133,22 @@ is untested and is the reading that would matter for authoring a default. > * *"the sources disagree"* — **settled**. Initial focus on a fresh boot is > **`NEW GAME`**, measured directly on two fresh boots, both the first menu entry. > The reader that produced the conflicting `TUTORIAL` was two items out. -> → *"the item NAMES below were wrong, and initial focus is NEW GAME"* +> → see the **2026-08-30 (later)** section on the corrected item names. > * *"never once run: whether focus persists"* — **it has been run**. The main menu -> **persists**; `EXTRAS` **resets**. → *"EXTRAS resets, the main menu persists"* +> **persists**; `EXTRAS` **resets**. → see the **2026-08-30** section on the two +> screens differing. > > Kept, not deleted, because it is what you were told at the time and a reader > arriving by grep needs to know it was overtaken. Nothing below this line is > current guidance. +> +> ⚠️ **These pointers name their targets by date and subject rather than quoting +> the headings.** Reproducing a heading verbatim here made that sentence appear +> **twice** in this file, which silently disarmed a `contract-check` anchor of +> `sylpheed-port`'s — it perturbs the *first* occurrence, and the check then read +> the untouched duplicate and passed a wrong contract. The forward marker I added +> to fix one navigation problem created a different one; **a duplicated sentence +> is enough to disarm a check without either of us touching a checked value.** **New, and it is a warning rather than an answer.** `menu-navigation-semantics.md`