Operator direction before the bookend: "complete a session sweep for anything
missed that should be committed that would be lost on session end". Precedent:
queued-findings-20260726.txt and -20260727.txt. Capture:
docs/audit/queued-findings-20260727-stage5-audit.txt.

THE SWEEP FOUND THREE STALE SURFACES THIS AUDIT ITSELF CREATED, which is the
exact defect class it was convened to find:

1. docs/audit/stage5-readiness-20260727.md -- the "read this first" artifact --
   still carried THIRTEEN NEEDS-RULING markers after every one of R1-R15 had been
   ruled or withdrawn. At that moment it was the single most misleading surface in
   the repo. Fixed with a supersession banner that names the three authorities in
   order and states what in the document is STILL true and worth reading: the
   ordered precondition sequence, the evidence column, the what-breaks column. The
   row-level markers were deliberately NOT rewritten -- they are the record of what
   was owed at the time, and rewriting them would destroy that record.

2. queued-rulings-20260727.md still opened with "Nothing here is adopted" after
   fourteen adoptions. Fixed with a STATUS block naming design-decisions.md and
   CURRENT-STATE.md as the ruling authorities rather than that file; the original
   sentence is struck through, not deleted.

3. SIX sections of that file had BLANK OPERATOR UTTERANCE lines -- R8, R9, R10,
   R12, R13, R15 -- for rulings that WERE properly recorded in design-decisions
   and CURRENT-STATE. GA-R5 was satisfied; the question sheet was not, and a
   future session reading only that file would have believed six questions were
   still open. All six filled with the exact utterance and where the ruling lives.
   R14-ORIGINAL's blank line is CORRECT and left alone -- it is superseded text
   kept for the audit trail.

TRANSCRIPT-ONLY OPERATIONAL FACTS NOW CAPTURED: the repo-lint L5 heading trap (a
heading LEADING with a D-number counts as a second definition unless the line also
contains AMENDMENT or RESOLVED -- it bit this session twice and is on no
author-facing surface); the commit-gated-on-lint discipline adopted after a red
commit was pushed, which then caught the second occurrence before it landed; the
read-only live-apex poll procedure that keeps the token in env and prints nothing;
that the office1 VMs answer from vcloud but NOT via voffice1, so "unreachable" from
the wrong host must never be recorded as "absent"; and that creds-matrix.tsv is
SPACE-aligned despite the .tsv extension, so awk -F'\t' returns zero rows and looks
like a real result.

META-FINDING RECORDED FOR THE NEXT COMMITTEE: the lenses' OBSERVATIONS were
reliable, their CONCLUSIONS repeatedly were not. Three of this audit's own premises
needed correcting by measurement -- R2a (literals already assigned under D-111), R9
(one failure mode not two, two scripts not twenty), R14 (the register already
attributed and explained the findings, and already warned against the suppression
the question contemplated) -- and R8's entire evidence base collapsed on reading
the cited bugs. A lens finding is an OBSERVATION, not a conclusion; measure before
putting it to the operator as a question.

VERIFIED DURING THE SWEEP, after an API disconnect mid-turn: nothing was lost or
corrupted. The earlier lens-5 API casualty was fully recovered -- its 18 findings
and section header are in the committed record, and all seven lenses are present.
The disconnect this turn fell cleanly between edits and a commit; the two modified
files parsed intact and lint was red only for the L10 this commit satisfies.

NOT DONE AND NOT OWED YET: the skill sweep. This session closed no STAGE, so the
stage-close fold-in and snapshot regeneration are not due. B1/C1/C2 in the capture
are the candidates when Stage 5 closes.

Revert: git revert this commit; the capture is new and the two repairs are
additive (banner, status block, filled utterance lines).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf