hygiene(tick-history): 2026-05-01T10:28Z — PR #1030 DIRTY rebase + 4 thread-fixes

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

@@ -0,0 +1 @@
+| 2026-05-01T10:28:00Z | opus-4-7 / autonomous-loop tick | 98fc7424 | PR #1030 follow-up tick — DIRTY rebase + 4 thread-fixes. Rebased against latest main (BACKLOG.md autogen take-theirs + regen). Three real fixes: (1) **Wildcard ref in B-0129 line 42** — `feedback_carved_sentence_fixed_point_stability_*` replaced with specific filename `memory/feedback_carved_sentence_fixed_point_stability_soul_executor_bayesian_inference_aaron_2026_04_30.md`; (2) **Wildcard ref in feedback_manufactured_patience line 267** — same wildcard replaced with same specific filename; (3) **MEMORY.md inline `<!-- paired-edit: ... -->` comment trimmed** — the comment added 100+ chars to the index entry and Copilot flagged it as making the entry heavy. Removed. The 4th thread (BACKLOG.md auto-generated reminder) addressed by the rebase regen flow itself — `BACKLOG_WRITE_FORCE=1 ./tools/backlog/generate-index.sh` is exactly what Copilot was asking for. All 4 threads resolved via GraphQL. PR #1030 substrate; auto-merge unarmed. Cron 98fc7424 healthy. | [PR #1030: 1 commit (0395256) addressing 4 threads — 2 wildcard→specific + 1 trim + 1 process-already-followed; force-with-lease push; auto-merge intentionally unarmed] | The wildcard-not-navigable class fired again twice in this same PR — same wake-window pattern as PR #1042 + others. The corrective is the same (paste-from-actual-filename), and at this point the pattern is so well-established it deserves a write-time lint (B-0130 row #1 wildcard-ref auditor). The MEMORY.md trim is the 4th instance this drain wave of "MEMORY.md entry too heavy / over-cap" — entries added during 2026-05-01 wake-window consistently include too much context inline rather than letting the linked file carry the detail. Future-Otto: when adding a MEMORY.md entry, the bullet should be 1-3 sentences max; everything else belongs in the topic file. The over-cap pattern is now a candidate for v3 taxonomy extension as a real-fix sub-class: **MEMORY.md-index-bloat / Real-fix subclass** — when the index entry exceeds ~250 chars or carries non-essential framing, trim to <200. |