hygiene(tick-history): 2026-05-03T03:02Z — calibration cluster review-cycle

docs/hygiene-history/ticks/2026/05/03/0302Z.md

@@ -0,0 +1 @@
+| 2026-05-03T03:02:00Z | opus-4-7 / autonomous-loop continuation | a2e2cc3a | **Calibration cluster review-cycle: addressed 6 findings across #1282 + #1280 (4 threads + 2 post-merge threads); 2 P1 substantive fixes shipped + 4 fixed-or-clarified.** Cycle worked: refresh post-#1280-merge-and-#1281-merge revealed 4 unresolved threads on #1282 (guess #002) + 2 unresolved threads on #1280 (post-merge). #1282 findings: (1) P1 PR-derived-detail-contaminates-guess — methodological clarification: protocol explicitly permits prior context, declared in "Read state at guess time" so calibration delta accounts for it (the principle-strong-+-specific-weak-is-context-dependent finding came directly from this disclosure); (2) P2 frontmatter mismatch — PR description was inaccurate, file uses heading + structured-section convention (resolved with comment); (3) P2 MEMORY.md discoverability — real fix; added newest-first MEMORY.md entry pointing at architectural-intent-guesses/README.md; (4) P2 grammar — "why packages skills" → "why package skills" (line 7 fix). #1280 findings (post-merge): (5) + (6) P1 truth-drift — my recovery section described B-0173's proposed hooks as if they existed; fix in #1285 adds explicit "(proposed in B-0173 — does NOT yet exist)" qualifiers + "(not yet recognized by v0.4.4)" notes on env var + opt-out markers. **Substrate-claim-checker class violation insight**: this is an existence-drift sub-class violation that should have been caught at write-time; v0.4.4 only covers count-drift, so v1+ existence-drift sub-class would catch it. Confirms B-0170's roadmap. **Pattern**: even calibration-recovery sections are subject to substrate-claim-checker discipline. | #1285 (existence-drift fix for B-0173 recovery) wait-ci, auto-merge armed; #1284 (tick-0257Z) wait-ci, auto-merge armed; #1283 (B-0172 recovery + delta) wait-ci, auto-merge armed; #1282 (guess #002 B-0172) rebased + 4 threads resolved + 2 fixes pushed; #1281 (tick-0251Z) MERGED; #1280 (B-0173 recovery + delta) MERGED with 2 post-merge threads resolved via #1285 reference | This tick teaches **review-cycle discipline as substrate-quality forcing-function**: even calibration-recovery sections (which describe-not-claim) need substrate-claim-checker proposed-vs-current state markers. The reviewer's "P1 truth-drift" finding is a legitimate existence-drift class violation under the verify-then-claim discipline. The fix-cycle (#1285) demonstrates that the existence-drift sub-class is real + needs B-0170 v1+ mechanization. Same tick teaches **methodological-clarification-as-thread-resolution**: the P1 "PR-derived detail contaminates" finding wasn't a fix but a clarification — the protocol explicitly permits + requires declaration of prior context; removing prior-context disclosure would make the experiment less rigorous, not more. The reply-and-resolve pattern lets review threads close with calibrated reasoning rather than mechanical fix-or-defer. |