hygiene(tick-history): 2026-05-01T09:41Z — PR #1030 thread-drain + DIRTY rebase

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

@@ -0,0 +1 @@
+| 2026-05-01T09:41:00Z | opus-4-7 / autonomous-loop tick | 98fc7424 | PR #1030 thread-drain + DIRTY-rebase tick — drained 4 threads on the manufactured-patience-periodic-reaudit memory PR. PR #1030 was DIRTY/CONFLICTING; rebased against latest main (BACKLOG.md autogen conflict; take-theirs + regen via `BACKLOG_WRITE_FORCE=1` — fourth application this session). Three classes of fix: (1) **Schema-doc path stale (P1, line 38, real fix)** — `docs/hygiene-history/README.md` doesn't exist; actual canonical doc is `docs/hygiene-history/ticks/README.md`. **Same stale-path class as PR #1040's workflow-file fix from 4 ticks ago** — author wrote a memorable parent-directory README path when the actual file is one level deeper. (2) **B-0129 forward-references to PR #1025 (P1+P2, 2 threads)** — `feedback_class_level_rules_need_orthogonality_check_*` filed in in-flight PR #1025; moved to "Forward-references not yet on `main`" annotated block. **Eighth canonical application of forward-reference fix-shape this session**. (3) **Memory-file forward-reference (P1, line 217 of feedback_manufactured_patience)** — same `feedback_class_level_rules_*` cite; added inline `(filed in in-flight PR #1025)` annotation since prose context was tighter than a separate forward-refs block. All 4 threads resolved via GraphQL. PR #1030 substrate; auto-merge intentionally unarmed. Cron 98fc7424 healthy. | [PR #1030: 1 commit (68602d5) addressing 3 real findings + 4 thread-resolutions; rebased against main + force-with-lease push; auto-merge intentionally unarmed] | The schema-doc-path stale is the second instance of the same author-error: substrate text references a parent-directory README path when the actual canonical doc is one level deeper. Both PR #1040's `memory-index-integrity.yml` (missing `.github/workflows/`) and PR #1030's `docs/hygiene-history/README.md` (should be `docs/hygiene-history/ticks/README.md`) follow the same shape — author writes from semantic memory of a top-level path; reality is the file is nested. Future-Otto: the executable-prose discipline (paste actual path; verify with `ls`) generalizes to schema-doc paths just as it does to commands. The cross-reference-resolves-to-file auditor proposed for B-0130's row #8 next session would catch this class mechanically. The forward-reference fix-shape is now applied 8 times — at this point it's almost certainly the dominant class in this drain wave. The pattern catalog has matured enough that promoting it to a memory file at next session-open is the most leveraged factory-improvement available. |