From c804dd523cf9c3c79e27fb4907df0c700a77c594 Mon Sep 17 00:00:00 2001 From: Levi Neuwirth Date: Wed, 29 Jul 2026 11:58:11 -0400 Subject: [PATCH] docs(active-work): stop pasting a count that invalidates itself MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The entry pasted `4 0`, measured immediately before the commit that wrote it; at the pushed head the same command said `5 0`. An ahead-count is self-referential in the file that carries it, so the entry now pastes only the merge-base — which is stable — and says to run the count on demand. Behind-count stays the thing that matters, and the merge-base tells you whether it can still be zero. --- docs/active-work.md | 24 +++++++++++++++--------- 1 file changed, 15 insertions(+), 9 deletions(-) diff --git a/docs/active-work.md b/docs/active-work.md index b231127..97d77d5 100644 --- a/docs/active-work.md +++ b/docs/active-work.md @@ -533,17 +533,23 @@ has **no branch and no framing yet**. ``` $ git merge-base HEAD githubsucks/main 5e186c798236e244a0a6f68d5df79458b4856106 - $ git rev-list --left-right --count HEAD...githubsucks/main - 4 0 ``` - **Re-measure before quoting this anywhere.** `main` moved TWICE while - this lane's round-1 fixes were being written — #192 and then #193 — - and each move invalidated the count above. `main` has branch - protection, so a stale base is not merely untidy: all 12 checks must - pass on the merging head, and a conflicting PR builds no merge ref at - all, so a green run from before the move reads as current when it is - not. + That is the whole durable fact, and it is deliberately the ONLY + number pasted here. **An ahead-count cannot be recorded in the file + it counts**: writing it is a commit, so the value is stale by one the + instant it is written, and the previous attempt at this entry proved + it — a pasted `4 0` read `5 0` at the pushed head. Run + `git rev-list --left-right --count HEAD...githubsucks/main` when you + need it; the merge-base above is what tells you whether the answer is + still meaningful. + + **Re-measure the merge-base too before relying on it.** `main` moved + TWICE while this lane's round-1 fixes were being written — #192 and + then #193. `main` has branch protection now, so a stale base is not + merely untidy: all 12 checks must pass on the merging head, and a + conflicting PR builds no merge ref at all, so a green run from before + the move reads as current when it is not. - **The framing's §8 branch plan is superseded and cannot be followed.** It says "one PR — #186, which becomes the implementation PR", written when #186 was still open. #186 merged as framing-only, so the