docs: CLAUDE.md Build Verification gate items (3) tree-clean + (4) verbatim trailer

SonicField · SonicField · commit ba00817065b1 · 2026-04-22T13:28:14.000-07:00
Per supervisor [chat L2257] adoption + librarian [chat L2255]
memory-decay-gap close. In-session adoptions (testkeeper L2186 +
L2233) now load-bearing in project-anchored CLAUDE.md instead of
agent memory only.

CHANGES (CLAUDE.md Build Verification section):
  Item (3) expanded:
    BEFORE: 'commit hash verified in the built binary'
    AFTER:  'commit hash verified in the built binary AND working tree
             clean during the build (no uncommitted edits influencing
             the binary)'
    Origin: testkeeper L2186 self-flag — L2174 lapse cited HEAD that
    didn't reflect actual binary content (uncommitted edits in tree).

  Item (4) added:
    'the verbatim build trailer block (from === Build complete ===
     through Binary timestamp: ...)'
    Origin: testkeeper L2233 paste-discipline + pythia L2188 +
    librarian L2255. Empirical evidence over PASS-on-claim convention.

  Reports missing any of items (1)-(4) are UNVERIFIED.

This is the close-the-memory-decay-gap fix librarian named at L2255.
3 lapses this session (count, session-log-only build check, paste-
build-output) all had existing discipline in memory but not in the
project-anchored doc — same class as L2174 lapse pattern.

Standalone commit (NOT bundled with W25 Step B-4) — discipline change
should be visible immediately + B-4 will need full attention with
130-extern full-paste discipline.

Authorization chain:
  - Librarian flagged memory-decay gap: chat L2255
  - Supervisor adopted amendment: chat L2257
  - Scribe surfaced existing CLAUDE.md text: chat L2256
  - In-session adoptions: testkeeper L2186 + L2233
diff --git a/CLAUDE.md b/CLAUDE.md
@@ -29,7 +29,9 @@ Retroactive approvals are NOT acceptable for Phase 3D commits (codegen conversio
 
 ## Build Verification (MANDATORY)
 
-Every BUILD PASS report must include: (1) the build command run, (2) binary timestamp, (3) commit hash verified in the built binary. Reports without these are UNVERIFIED. Two build-verification failures in the 2026-04-16 session (stale binary + phantom build) proved that "it builds" claims without evidence are unreliable.
+Every BUILD PASS report must include: (1) the build command run, (2) binary timestamp, (3) commit hash verified in the built binary AND working tree clean during the build (no uncommitted edits influencing the binary), (4) the verbatim build trailer block (from `=== Build complete ===` through `Binary timestamp: ...`). Reports without all four are UNVERIFIED.
+
+Two build-verification failures in the 2026-04-16 session (stale binary + phantom build) proved that "it builds" claims without evidence are unreliable. Item (3)'s tree-clean addition is per testkeeper 2026-04-22 L2186 self-flag (cited HEAD didn't reflect actual binary content during uncommitted-edit window). Item (4) verbatim-trailer paste is per testkeeper L2233 + librarian L2255 (closes memory-decay-gap on PASS-on-claim convention).
 
 ## Build Lock (MANDATORY — Phase 3D)
 
