Record the ANALYST form of stale_base_branch_reads_as_pending_work: a label authored separately from its measurement

dag/gunbc/recurring_failure_mode/stale_base_branch_reads_as_pending_work.dag

@@ -64,6 +64,38 @@ data stale_base_branch_reads_as_pending_work: RecurringFailureMode = RecurringFa
     "Nothing in this specimen shows a scheduler reviewing a closed pull request, so the closure-semantics claim had no receipt and is withdrawn -- it may well be true of the scheduler and would need a review whose completion genuinely follows a closure. ",
 
     "It is left in the row rather than deleted because a ledger row asserting a behaviour its own cited receipt does not show is the fabricated-citation class appearing INSIDE the row that files its neighbour, and the scoping repair is the same one that spared a true citation six lines above the note this specimen came from: repair the false claim, do not delete the true one beside it.)",
+
+    "**THE ANALYST FORM, BESIDE THE READER FORM ABOVE (amended 2026-09-03, tidy-koi-619 and warm-seal-35, three git specimens inside one evening; a fourth was carried and removed, see below).** Everything above describes the ARTIFACT misleading someone who reads it. This form is the person who MEASURES CORRECTLY AND LABELS THE MEASUREMENT WRONG. ",
+
+    "THE INVALID STATE, SCOPED TO WHAT THIS ROW'S TRIGGER CAN RETIRE: a DIFF DIRECTION labelled as the question it does not answer, when analysing whether a branch's content has already landed. THE GENERAL FORM IS REAL AND IS NOT A LADDER CLASS AT ALL, which is a stronger statement than 'not claimed here' and is made deliberately so that nobody later closes an implied gap with a decoration. Any label authored separately from the measurement it names is a genuine authoring hazard, but ask section 4b's question before filing it: IS THE RED AUTHORABLE? For the general form, no. The labels in the specimens below were echo strings and heredoc headings in SHELL COMMANDS TYPED BY AN AGENT -- not in the corpus, not in any Accepted program, not reachable by any lens over the Node tree. No fixture can express 'an author wrote a heading that misdescribes the command beneath it', because the subject is not a program, it is an author. That places it in section 4b's adjacent column -- OUTSIDE THE MODELED GUARANTEE, which is deliberately not a fifth rung -- and a row whose trigger names a capability that can have no discriminating RED is a decoration that will later be cited as coverage. The DECIDABLE SLICES are already owned and that is the honest state: this row owns diff-direction labelling under a producer that can actually retire it, and per-instrument fixes like `grep -H` or printing the ref expression are invocation-site discipline rather than ladder classes. WHAT WOULD CHANGE THIS: a fixture harness able to express a mislabelled measurement AS SOURCE. Nobody has constructed one; that is the trigger if it exists. This row's own trigger names a producer scoped to 'each file a pull request changes', so it can never retire an instance with no pull request in it, and a row carrying a loss its trigger cannot reach is the grain mismatch DESIGN section 4b(3) names as a review tell. That boundary was established by review 59526 on gunbc#10286, against an earlier revision of this amendment which asserted the general form here. ",
+
+    "It is worse than the reader form rather than milder: the reader form yields a MISSED fact, this yields a SPECIFIC FALSE CLAIM, and a specific false claim gets acted on. ",
+
+    "THE GIT INSTANCE: diff(merge-base, head) is WHAT THE PULL REQUEST DOES and is the only direction that describes a merge; diff(head, main) and two-dot main..branch are WHAT THE BRANCH LACKS. Both readings are true; only the label is wrong. ",
+
+    "SPECIMEN ONE (gunbc#10242 and gunbc#10276): reported that merging two survivor branches would DELETE eight and then four named files, including a witness test that had landed twenty minutes earlier, and posted it on a closed pull request AS A CORRECTION. Measured, the branches' own diffs are 3A/26M/2R/0D and 2M/0D -- zero deletions, and the named test is in neither diff. The 'deletion set' was main's FORWARD MOVEMENT read out of the wrong direction. THE TELL PRESENT AND MISSED: across four branches of one session the counts were 22, 14, 7 and 4, MONOTONE IN BRANCH AGE. A deletion set does not correlate with staleness; a forward-movement set does so by definition. ",
+
+    "SPECIMEN TWO (gunbc#10265, the MIRROR DIRECTION): the rule held correctly, a MERGE-BASE hunk quoted, labelled an answer about MAIN. ",
+
+    "A THIRD SPECIMEN WAS CARRIED HERE AND HAS BEEN REMOVED, and recording the removal is worth more than the specimen was: two greps in ONE shell command over two job logs, output read as belonging to the first. It was included BECAUSE it has no branch in it, on the reasoning that this forecloses the objection that the class is about git. That reasoning was exactly backwards. No branch in it is why it CANNOT belong here: a producer joining branch, main and merge-base cannot make a hand-authored log label unwritable, so the specimen sat under a trigger that could never retire it. It does not get to live under this one, and -- see the invalid-state receipt above -- it does not get its own row either, because its RED is not authorable anywhere a fixture can reach. ",
+
+    "SPECIMEN FOUR (gunbc#10284, the sharpest): `git diff origin/main..$BR --stat` run under an echo string reading 'what the branch would ADD to main', returning 36 files, 743 insertions and 4,680 DELETIONS -- which read for about ten seconds as a mass revert about to be proposed. Two-dot main..branch shows what the branch LACKS; three-dot shows four deletions. THE LABEL WAS WRITTEN BEFORE THE COMMAND RAN, so the output could only confirm it. A PRE-WRITTEN LABEL IS NOT A LABEL, IT IS A HYPOTHESIS WEARING ONE. ",
+
+    "THE REPAIR FOR THE SPECIMENS THIS ROW KEEPS is the trigger already named: the supersession producer's output leaves the analyst nothing to compose or label by hand, which is where all three git specimens failed. The wider repair -- make every producer emit its own identity, so the diff prints the ref expression it evaluated -- would also cover them, but it is a DIFFERENT capability and naming it here would grow this row's trigger past what retires it. ",
+
+    "WHAT DECIDES THIS BELONGS HERE RATHER THAN IN A ROW OF ITS OWN, and it is also the strongest support for this row's existing trigger: THE FIRST TWO SPECIMENS OCCURRED WHILE ANALYSING AN INSTANCE OF THIS VERY CLASS. Both branches were stale-base survivors whose content had already landed. Neither analyst stumbled into a neighbouring failure; each failed AT the class while examining it, having stated the distinction correctly to the other in writing beforehand. The row already argues the trigger must name a PRODUCER rather than reviewer diligence, citing an approval of superseded content; this is stronger, because the approval shows someone MISLED BY THE ARTIFACT while these show two analysts who KNEW THE RULE, HAD JUST WRITTEN IT DOWN, AND STILL MISLABELLED A DIRECTION WITHIN HOURS. If holding the rule is not sufficient, diligence is definitively not the repair. ",
+
+    "THE TRIGGER IS NOT EXTENDED AND MUST NOT BE: the producer already named -- joining branch against main AND against the merge-base and emitting a typed supersession verdict -- covers this form, because its output leaves nothing to COMPOSE OR LABEL BY HAND, and that is where all three kept specimens failed. A trigger that grows to name a second capability is how a row stops being retirable. ",
+
+    "THE FALLBACK WHEN YOU CANNOT TELL WHICH WAY YOU MEASURED, recorded because it is what held while every directional claim beside it was retracted: ZERO BRANCH-ONLY FILES, plus the branch's content verified PRESENT ON MAIN BY CONTENT rather than by ancestry, since a squash destroys ancestry. It needs no direction to be correct and was sufficient to close both pull requests on its own. ",
+
+    "A NEIGHBOUR CITED RATHER THAN RESTATED, because restating a neighbour's fact here is the failure this ledger exists to prevent: the empty-result half is `empty_capture_read_as_clean_result`, and citing it is load-bearing because BOTH AUTHORS OF THIS AMENDMENT INDEPENDENTLY REPORTED AS A FRESH METHOD NOTE A SPECIMEN THAT ROW ALREADY NAMES -- `gh api` job logs writing ZERO BYTES without --allow-escape-sequences, refusing on stderr. One of us was one message from filing a second authority for it. ",
+
+    "TWO OF THIS AMENDMENT'S OWN NEAR-MISSES BELONG TO THAT NEIGHBOUR AND NOT HERE, and measuring them split them: `git show` against an unfetched sha exits 128 and prints 108 bytes of `fatal:` while writing an empty file, later read as zero declarations in an 83-row module; and the `gh api` sweep exited 1 under a `2>/dev/null | grep -c ... || true` that deleted the exit code and the message in the same command that produced the wrong answer. For both, that row's remedy works as written -- consult the typed status. ",
+
+    "A THIRD HAS NO TYPED STATUS TO CONSULT, and it is recorded WITH ITS CONTROL because without the control it is a curiosity and with it a defect. Both arms as a pair: `gh run list --commit` on a ref that does not exist, and on a REAL commit that genuinely has no runs, both return rc=0, three bytes of stdout `[]` and zero bytes of stderr -- BYTE-IDENTICAL ON EVERY CHANNEL THE CALLER CAN READ, exit code included. TWO DISTINCT STATES COLLAPSED INTO ONE VALUE. The remedy is named rather than left as a gap: not read the status, but ESTABLISH THAT THE SUBJECT EXISTS BEFORE CONSUMING AN OBSERVATION ABOUT IT -- a `git cat-file -e` existence probe separates the two arms where no channel of the instrument can. An empty observation set is readable only once the subject is known to be in the domain, which is 'a zero is only readable beside a nonzero' moved from the COUNT to the SUBJECT. The repair belongs to that neighbour and is pointed at rather than performed here. ",
+
+    "ONE RECOGNITION RULE BELONGING TO THAT SAME NEIGHBOUR, placed here only because this amendment was the edit in flight on this carrier and two lanes appending to one roster is how the duplicate-declaration defect of 2026-09-03 was created: `2>/dev/null` and `|| true` INSIDE A MEASUREMENT are a mechanical, greppable tell. Both are legitimate in a probe whose failure is expected and uninteresting; in an instrument they delete exactly the evidence that the instrument did not run.",
   ],
 
   evidence: [],