hygiene(tick-history): 2026-05-01T21:41Z — Copilot false-positive class + review-loop-hygiene cluster

docs/hygiene-history/ticks/2026/05/01/2141Z.md

@@ -0,0 +1 @@
+| 2026-05-01T21:41:00Z | opus-4-7 / autonomous-loop tick | 98fc7424 | Substrate-density audit + Copilot-false-positive class landed. **REFRESH WORLD MODEL**: 27 open LFG PRs (5 BLOCKED, 22 UNKNOWN; 21 resolve-threads, 4 fix-failed-checks, 1 wait-ci, 1 none). Session-bracket PRs: #1155 SQLSharp memo MERGED; #1167 harness-engineering memo MERGED; #1168 Copilot false-positive class wait-ci. **Speculative target this tick**: Copilot tick-history schema false-positive class — 2x-confirmed pattern (PR #1159 shard 2047Z + PR #1165 shard 2120Z, both alleging that the first line begins with a leading-numbered prefix and double-pipe before the date, when actual content begins with a single pipe + space + ISO timestamp cleanly + validator confirms zero violations). Per Osmani Ratchet Pattern (every recurring failure → permanent rule), 2x crossed the substrate threshold. PR #1168 lands the discipline: when Copilot posts that exact false-positive shape, run `tools/hygiene/check-tick-history-shard-schema.sh` first; if zero violations, resolve thread as outdated without code changes. Composes with BLOCKED-with-green-CI investigation rule + rebase-decision rule — three review-loop-hygiene rules now form a cluster. **Queue observation**: 25 of 27 open PRs are session-bracket substrate (mostly memory files, tick-history shards, research absorption); accumulation rate ≈ 2 PRs/hour matches review-loop bottleneck. Not triage-required — natural substrate density. Decision deferred to next-Aaron-input on whether to bulk-close any older PRs. Cron 98fc7424 healthy. | [PR #1168 OPENED with Copilot tick-history false-positive class memo + MEMORY.md row pair-edit; auto-merge armed; #1155 + #1167 confirmed merged; tick-history shard 2120Z merged via #1165] | The review-loop-hygiene cluster is now 3 rules (rebase-decision, BLOCKED-with-green-CI investigate-threads-first, Copilot tick-history false-positive). Pattern observation: review-loop hygiene is high-leverage substrate territory — each rule saves substantial wasted-loop time on its specific failure class, AND the rules compose (each one's discipline applies before the next). Future review-loop hygiene candidates likely emerge organically from PR review patterns; not worth pre-speculating. The Osmani Ratchet pattern naming gives a clean threshold (2x = substrate) for when to encode. |