From 549e225505a38e8dcedf136ab356c6ca56ebfa9d Mon Sep 17 00:00:00 2001 From: Levi Neuwirth Date: Wed, 12 Aug 2026 13:54:26 +0200 Subject: [PATCH] docs: remove the #238 lane --- the promised final pre-merge commit The lane recorded this PR while it was under review, because an open PR without a lane is the #171 defect: it drifted 153 commits while invisible in the ledger. Review is done, so the lane goes. **It had to go in a commit rather than "at merge".** GitHub merges the tree as it stands, so leaving it would have landed the words *PR #238 OPEN* on `main` --- a lane advertising an open PR that closed in the same commit, which is the exact staleness class this absorption exists to clear. Rule 4 takes it **outright** rather than rewriting it: a lane is rewritten when its ARC survives its PR, and this one describes a docs pass with nothing left behind it. Every reference to #238 and to the `docs-absorb-237` branch lived inside the lane, so the deletion is self-contained and leaves no dangling pointer. What the lane recorded that outlives it is already elsewhere: the recovery rehearsal and its floor checks are in "Repository authority", and the GUI arc's state is in the Stage 1 lane and the handoff anchor. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_016bqGA6s9tTUFzYpbeW3tai --- docs/active-work.md | 48 --------------------------------------------- 1 file changed, 48 deletions(-) diff --git a/docs/active-work.md b/docs/active-work.md index f6ae35d..cbed93f 100644 --- a/docs/active-work.md +++ b/docs/active-work.md @@ -270,54 +270,6 @@ hazard in a shape that looks committed. **A documented error message that never appears is worse than no documentation**, because the reader waits for a signal that is not coming. -## Docs absorption of #236 and #237 — PR #238 OPEN, docs only - -**Written with the branch's own commit**, because this file's standing -rule is *when a PR is opened, give it a lane* — and a lane recording an -absorption belongs in the absorption, not after it. #171 drifted 153 -commits while invisible here. - -- **PR #238** — https://github.com/levineuwirth/pmacs/pull/238. -- **Branch `docs-absorb-237`**, base `githubsucks/main` @ `d038f71` - exactly. **`githubsucks/docs-absorb-237` is the authoritative tip** — - the ref, not a SHA. -- **Scope: `docs/active-work.md` and `docs/agent-handoff.md` only.** No - `src/`, no `pmacs-gpu/`, **no Stage 1a implementation** — verified with - `git diff --name-only githubsucks/main`, which lists nothing outside - `docs/`. -- **The recovery procedure was RE-RUN from an empty directory on git - 2.55.0, not SHA-swapped**, and that is what licenses advancing the - base at all. It also **discharges the obligation left at `e67ad07`**, - where the base moved without the procedure being exercised. Details in - "Repository authority" above; the floor check was run against **both** - floors, and the documented two-argument worktree trap was reproduced - rather than assumed. -- **Gates: `./scripts/gate`, all eight stages green** (log - `20260812T111504Z-3265400`). No `--acceptance` and no `--protocol` — - docs only, so no suite is touched and no wire moves. That run covered - `502308d`. **Every commit after it is markdown-only** — stated as a - standing property rather than a count, because a count goes stale on - the next commit, which is how the previous version of this sentence - came to say "one commit, 34 lines" when there were two and 38. Check - it with `git diff --name-only 502308d..HEAD`, which must list nothing - outside `*.md`; `git diff --check` and `cargo fmt --check` are clean - at HEAD. -- **One judgement recorded because it exceeded the requested scope and - was approved on review**: §1a's board carried no GUI-arc row, which - contradicted the anchor two sections above it. The row sits where - `COHERENCE.md` §20 Q#GA5 puts the arc — after Priority 1, alongside - P2–P5, interacting only at the **P2 start gate** — and the section's - dateline now says which row is current and which are as of - 2026-08-01. -- **THIS LANE MUST BE DELETED BY A FINAL PRE-MERGE COMMIT ON THIS - BRANCH, and cannot remove itself at merge.** GitHub merges the tree as - it stands, so "removed at merge" would land the words *PR #238 OPEN* - on `main` — a lane advertising an open PR that closed in the same - commit. It stays while the PR is under review, because an open PR - without a lane is the #171 defect; the last commit before merge takes - it out. Rule 4 removes it **outright** rather than rewriting it: it - describes a docs pass, not an arc. - ## GUI arc Stage 1 — 1-pre MERGED as #237 (`d038f71`); 1a is next, NOT STARTED **The lane is rewritten, not removed.** Rule 4 removes a lane when its