diff --git a/docs/hygiene-history/loop-tick-history.md b/docs/hygiene-history/loop-tick-history.md
index 58b20318..734c2fad 100644
--- a/docs/hygiene-history/loop-tick-history.md
+++ b/docs/hygiene-history/loop-tick-history.md
@@ -304,3 +304,4 @@ fire.
 | 2026-04-28T05:44Z (autonomous-loop tick — comprehensive CI fix landed (PR #80, MERGED) + retry bump 3→5 follow-up (PR #81) + Otto-357 2nd-recurrence substrate strengthening (PR #82) + 3 conflict resolutions on long-lived PRs) | opus-4-7 / session continuation | ff34da97 | **Multi-PR-cascade follow-up tick.** (1) **PR #80 MERGED** at 05:41:57Z — comprehensive install cache + workflow retry + ubuntu-22.04 → ubuntu-24.04 bump across 5 workflow files. Aaron's input chain absorbed: cache (added to all 3 lint jobs that previously had none), retry (CI-only wrapper around install.sh, 3 attempts), Ubuntu version bump (LTS-2 stale → current), comprehensive cache scope (everything install.sh writes — ~/.local/bin/mise, ~/.local/share/mise, ~/.cache/mise, ~/.dotnet/tools, ~/.elan, ~/.config/zeta, tools/tla, tools/alloy), cache key on `.mise.toml` + `tools/setup/**` + `global.json` so install-logic changes invalidate cache. (2) **PR #81 opened** — 3 → 5 attempt retry bump per Aaron's "go to 5 or 10" with backoff schedule extended to 10s/30s/60s/120s (≈3.7 min total). Conflict from #80 landing first resolved via `git checkout --ours` keeping the 5-attempt version; rerere recorded. (3) **Otto-357 2nd recurrence caught** — Aaron's "aaron does not have directives, only one there are no directives. Please fix your future self too." flagged my close-of-tick using "Aaron's directives in the chain". Filed PR #82 with: recurrence log section (now 2 entries), pre-write self-scan rule with explicit forbidden-token list (extends prior coverage from commit/PR/memo to ALSO conversational chat text — where this 2nd recurrence lived), backlog candidate for automated lint composing with prompt-protector pattern, Otto-340 application note about framing-language compounding. (4) **PR #19 rebased** onto new main (with PR #79's broader carve-out + PR #80's CI cache) — picks up `docs/research/2026-*-*.md` ignore that covers gemini-deep-think + action-mode verbatim ferries. (5) **PR #72 cascade conflict #4** resolved via additive-keep-both pattern on memory/MEMORY.md AND tick-history.md (now 2 spine files cascading); rerere now has resolutions for both. (6) **Cron `ff34da97`** verified live via CronList — fresh check, not stale claim, per the verify-don't-parrot meta-discipline (this tick is the 4th consecutive autonomous-loop tick where the discipline has fired; the observations column below enumerates the 4 distinct fresh-source verifications applied within this tick). | (multi-PR follow-up + Otto-357 substrate strengthening tick) | **Observation — Otto-357 recurrence-log pattern matches the bulk-resolve-not-answer recurring-pattern shape**: both memories track "violated again on date X" as empirical evidence that vigilance-only enforcement is structurally insufficient. The accumulating recurrences ARE the structural signal that automated lint is needed (composes with prompt-protector's invisible-Unicode lint shape). Future structural fix: write-time word-list scan as PreToolUse hook on Edit/Write tools. **Observation — sequential-merge spine-file cascade is now 2-file**: memory/MEMORY.md + tick-history.md both flip OPEN PRs to DIRTY when main lands a touch. With 12 PRs in queue, that's O(N×2) DIRTY-events per merge into either file. The B-0067 cadenced git-hotspot detector + B-0066 MEMORY.md auto-generated index are both upstream prevention; this tick reinforces both as P1. **Observation — Aaron's input-chain density 2026-04-28 ~05:30-05:44Z**: 4 corrective inputs in ~14 min (is-there-not-a-way / use-stock-and-not-old-ubuntu / cache-and-retry-and-dev-CI-parity / why-not-cache-whole-install + retry 3→5 + no-directives-fix-future-self). Aaron is actively shaping substrate at high tempo. The Otto-275-FOREVER discipline (apply-not-just-know) gets continuously stress-tested by these arrival rates. **Observation — verify-don't-parrot has now applied 4 ticks running**: cron-id verify (caught), AUTONOMOUS-LOOP.md grep (worked), CronList freshness (worked), retry-3-failed-on-#23 sourcing from actual run log (worked). The meta-discipline is sticky once the rule fires once. Pattern: sourcing claims from fresh data (run logs / git log / grep) instead of memory becomes habit after one Aaron-catch. |
 | 2026-04-28T05:50Z (autonomous-loop tick — PR #75 4 threads drained (1 form-2 with empirical bash-test on Copilot's wrong-P0 + 3 form-1 substantive fixes); 121 unresolved threads across 11 PRs surveyed; PR #19 rebased, PR #72 cascade #4 resolved, PR #81 --ours conflict resolved) | opus-4-7 / session continuation | ff34da97 | **Thread-drain batch tick.** (1) **Bulk thread-state audit** per Otto-355 corrected filter (`isResolved == false` only — outdated still blocks per `feedback_outdated_review_threads_block_merge_resolve_explicitly_after_force_push_2026_04_27.md`): #17(9), #19(14), #21(8), #22(8), #23(16), #24(9), #28(7+5out), #30(7), #31(6), #72(28), #75(4). Total 121 unresolved threads. (2) **PR #75 fully drained** — 4 threads, all from copilot-pull-request-reviewer. Thread 1 P0 (claimed `if ! var="$(cmd)"` doesn't catch cmd failure) verified empirically wrong on bash 3.2.57 + 5.x — `bash -c 'if ! x="$(false)"; then echo CAUGHT'` prints CAUGHT. Closed form-2 with bash version + test command + commit SHA in the thread reply; the macos.sh code is already double-safe (if-not gate + empty-string gate). Threads 2-4 form-1 substantive: stale curl-fetch.sh COMMAND-SUBSTITUTION + SET-E section now describes actual two-gate behavior; misleading "uniform retry behaviour during install" header now distinguishes file-output (retries) vs streamed (no-retries) variants explicitly + warns readers; B-0063 backlog `sha256sum` example replaced with cross-platform `sha256sum` / `shasum -a 256` / `openssl dgst -sha256` detect-and-dispatch (the OpenSSL form takes the digest algorithm as a `-sha256` flag with a space, not as a hyphenated subcommand). All 4 threads resolved via GraphQL; auto-merge still armed; awaiting CI on new commit. (3) **3 conflict resolutions earlier** in this tick: PR #19 rebased onto new main (picks up PR #79 carve-out + PR #80 cache); PR #72 cascade #4 resolved (memory/MEMORY.md + tick-history.md both spine files now flipping every PR DIRTY on each merge); PR #81 conflict from PR #80 landing resolved via `git checkout --ours` keeping the 5-attempt retry. (4) **Cron `ff34da97` verified live** via CronList. | (thread-drain batch + 3 conflict resolutions tick) | **Observation — Copilot P0 false-positive shape**: empirical test of the asserted bug took 30 seconds and falsified the claim. Pattern: when Copilot asserts shell-language semantics ("does not test exit status", "fall through"), test the assertion directly before applying a fix that might be unnecessary. Form-2 closure with empirical evidence is the right shape — preserves the agent's correctness without the maintainer-time-cost of a needless code change. **Observation — bulk thread state per Otto-355 corrected filter**: the rebased filter (`isResolved == false` only, including outdated) caught 5 outdated-but-unresolved threads on PR #28 that the prior wrong filter would have missed. Otto-355's filter-bug correction is paying compound dividends on every audit. **Observation — thread-drain throughput**: 4 threads on PR #75 took ~6 minutes including empirical verification, comment updates, B-0063 example fix, GraphQL replies + resolves. ~90sec/thread when most are addressable form-1/form-2. Multi-tick projection for remaining 117 threads: 25-30 minutes of focused drain time. **Observation — verify-don't-parrot meta-discipline 5 ticks running**: this tick I verified Copilot's P0 empirically before applying the suggested change; previous ticks verified cron-id, AUTONOMOUS-LOOP.md inclusion, retry-3-on-23-cause via run logs. Pattern: source-claims-from-fresh-data is now habit. **Observation — spine-file cascade now empirically twice-confirmed (#72)**: memory/MEMORY.md + tick-history.md both flip-DIRTY on every merge that touches them. With 12 PRs in queue + a typical PR touching either file, that's 11+ DIRTY-events per session. B-0066 (auto-generated MEMORY.md index) + B-0067 (cadenced git-hotspot detector) are the right structural fixes; rerere-recording is the bridge. |
 | 2026-04-28T07:15Z (autonomous-loop tick — 3 PRs MERGED in this tick chain (#82 Otto-357 strengthening at 06:57Z + #17 Amara ferries + #83 tick-history); 10 review threads drained across 5 AceHack PRs (#17 → 3 follow-up + #82 → 2 + #83 → 1 + #84 → 1 + #85 → 3) plus LFG #660 13 threads drained-but-still-BLOCKED-awaiting-reviewer (= 23 threads drained total this tick chain); B-0071 P2 backlog row filed for Otto-275-FOREVER rename out of live-lock taxonomy) | opus-4-7 / session continuation | ff34da97 | **Thread-drain throughput tick — 3 substantive PRs landed in this tick chain.** (1) **PR #82 MERGED** at 06:57:09Z — 2 threads addressed: Otto-275-FOREVER inline definition + expanded forbidden-token list with literal phrases from INSTEAD/USE table + bare-word patterns. (2) **PR #17 MERGED** at end of tick — **3 threads drained THIS TICK** (the `#17 → 3 follow-up` counted in bullet 0's per-tick subtotal); **9 threads drained on PR #17 lifetime cumulatively** across this session (3 this tick + 6 in earlier ticks already resolved at merge time): scope-note rewrite on docs/research/2026-04-26-amara-fail-open-with-receipts-* (factually accurate description of PR #17's 2-research-doc + 4-memory + MEMORY.md scope, dropped PR-relative phrasing); /tmp absolute-path replaced with durable-pointer rationale; Otto-278 xref relabeled as user-scope memory; per-named-agent-memory-architecture dead-pointer replaced with 4 real in-repo memory-architecture research docs; B-0071 P2 backlog row filed for the live-lock-9th-pattern rename (form-2 deferral with tracking — Otto-352 taxonomy split is correct but rename cascade needs dedicated PR); Otto-352 user-scope path relabeled. (3) **PR #83 MERGED** — 1 thread: verify-don't-parrot streak count reconciled (3 vs 4 → 4-within-PR-#83-scope, with explicit reference to the observations column enumeration; the observations footer of THIS row uses "6 ticks running" which counts back further across the entire session — see streak-scope clarification below). (4) **LFG #660 — 13 threads drained, still BLOCKED awaiting reviewer**: persona/name attribution stripped on 5 current-state surfaces (.github/workflows/budget-snapshot-cadence.yml + memory-index-duplicate-lint.yml + tools/hygiene/audit-memory-index-duplicates.sh + tools/setup/macos.sh + tools/setup/common/curl-fetch.sh) per Otto-279 history-vs-current-state distinction; corrected misleading "arms auto-merge" top-comment in budget-snapshot workflow (impl explicitly does NOT arm auto-merge; cited the auto-merge-limitation section); fixed shellcheck SC1091 rationale (was "CI runs without -x" — unrelated to SC1091; replaced with $SETUP_DIR-runtime-construction explanation); fixed shellcheck source path (common/curl-fetch.sh → tools/setup/common/curl-fetch.sh, repo-root-relative); replaced B-0063 specific-path xref with bare-id reference; PR title + body updated from "4 files" to "5 files" reflecting the audit-script dependency. (5) **PR #84/#85 thread fixes pushed**: openssl dgst-sha256 typo → openssl dgst -sha256 (with space); B-0069 frontmatter aligned to tools/backlog/README.md schema (status: backlog → status: open per enum, dropped non-schema slug/maintainer/ownership, added required last_updated, added optional ask/effort/tags); dead xref to PR-#17-only file replaced with in-tree authoritative tools/hygiene/validate-agencysignature-pr-body.sh pointer. (6) **Cron `ff34da97`** verified live via CronList. Drift: AceHack 123 ahead → 126 ahead, LFG 499 ahead unchanged (down 0 net but #17 + #82 + #83 landed so AceHack is +3 since last tick). **Streak-scope clarification:** the "6 ticks running" in the observations footer counts the autonomous-loop ticks across this entire session (back through the 05:23Z and 05:44Z tick rows where the verify-don't-parrot discipline first fired explicitly); the "4 ticks running" in PR #83's commit message counts only the 4 distinct verifications applied within the immediately-prior 05:44Z tick (cron-id / AUTONOMOUS-LOOP.md grep / CronList freshness / retry-3-failed-on-#23 sourcing). Both numbers are correct in their respective scopes; the apparent conflict is naming, not arithmetic. | (thread-drain throughput tick — 3 PRs landed) | **Observation — broken-in-repo-cross-reference is a recurring failure class**: this tick + prior ticks hit the same shape on Otto-278, Otto-352, per-named-agent-memory-architecture, B-0063 path, Amara-fail-open-with-receipts. Pattern: backlog rows / memory files / docs reference paths that exist only in user-scope or only on unmerged PR branches. Fix shape is consistent (relabel as user-scope with absolute path + scope-difference note, OR drop path-specific reference + use bare ID). Backlog-worthy: extend B-0070 orphan-role-ref-detector to ALSO catch broken in-repo path references — same lint, different pattern. **Observation — backlog frontmatter schema drift across 4 recent rows**: B-0068, B-0069, B-0070, B-0071 all authored with off-schema fields (slug, maintainer, ownership) and non-enum status:backlog. Schema source-of-truth is tools/backlog/README.md. Sister-row sweep PR worth opening once primary work clears. The drift happened because I authored from a stale mental template; copied across 4 rows in parallel = compounding. Otto-275-FOREVER applies: knowing-rule (read tools/backlog/README.md before authoring) != applying-rule (I didn't re-read the schema before each row). **Observation — Otto-355 BLOCKED-investigate-threads-first paying compound dividends**: this tick alone, 10 review threads drained across 5 AceHack PRs unblocked 3 PRs to merge. The structural fix from Otto-355 (always query unresolved threads before classifying a wait state) keeps converting "stuck" PRs into mergeable ones. The threads existed; the manufactured-patience pattern would have classified the PRs as "waiting for reviewer" and burned ticks waiting for the wait state to resolve. Active-investigation throughput: 3 PRs/tick, ~90sec/thread. **Observation — Otto-279 history-vs-current-state surface distinction is operationally cleanly applied**: stripped persona names from 5 current-state surfaces (.github/workflows/, tools/setup/, tools/hygiene/) without touching memory/, docs/research/, docs/backlog/ which keep persona attribution per the carve-out. The rule is sharp enough to apply mechanically; codex/copilot reviewers reliably flag violations. **Observation — verify-don't-parrot 6 ticks running**: this tick verified PR #82 was merged (gh pr view --jq mergedAt = real timestamp not "I think it merged"); verified Otto-352 file location (in-repo grep returned empty, user-scope ls confirmed); verified backlog schema in tools/backlog/README.md before fixing B-0069 frontmatter. The discipline is sticky. |
+| 2026-04-28T08:50Z (autonomous-loop tick — post-compaction recovery + drain; 2 PRs MERGED (#92 Zeta=heaven writeup + #87 tick-history with disambiguation fix); 11 threads drained (1 on #87 form-1 disambiguation + 10 on #72 [6 form-1 substantive + 1 form-2 deferral to B-0072 + 3 form-2 stale-snapshot empirical falsification of "0 elisabeth hits" claim]); PR #72 cascade #5 resolved (memory/MEMORY.md additive-keep-both, rerere recorded); B-0072 P2 filed for MEMORY.md index entry length normalization) | opus-4-7 / session continuation post-compaction | ff34da97 | **Drain-and-merge tick post-compaction.** Session resumed after context-compaction with state: PR #72 DIRTY (cascade from PR #93 merge) + PR #87 BLOCKED 1 thread + PR #92 CLEAN MERGEABLE no-auto-merge + LFG #659/#660 BLOCKED queue. (1) **PR #87 MERGED at 08:48Z** — 1 codex P2 thread on the prior 07:15Z tick row ("3 vs 9" thread-count ambiguity); fixed inline by labeling per-tick-vs-cumulative explicitly ("3 threads drained THIS TICK" + "9 threads drained on PR #17 lifetime cumulatively"). (2) **PR #92 MERGED at ~08:46Z** — was CLEAN with `autoMergeRequest:null`; armed auto-merge directly with `gh pr merge --auto`; merged immediately since on Zeta `requiredApprovingReviewCount=0` per the calibration memory (PR #91). (3) **PR #72 cascade #5 resolved** — memory/MEMORY.md conflict between HEAD (9 newer 2026-04-28 entries) and acehack/main (3 newer entries from #91+#93); applied additive-keep-both pattern with chronological main-first ordering; rerere recorded ("Recorded resolution for 'memory/MEMORY.md'"); pushed merge commit; auto-merge already-armed by Aaron at 04:02Z. (4) **PR #72 — 10 threads drained**: 6 form-1 substantive (docs/backlog/README.md auto-generated→read-only-stockpile framing reconciliation, docs/BACKLOG.md "Single source of truth"→legacy-stockpile alignment, docs/backlog/P1/B-0060 broken `B-0288` xref→task #288, memory/feedback_structural_fix wildcard xrefs→concrete filenames, memory/feedback_self_check user-scope-vs-in-repo path tagging, wallet-experiment §13.4 in-repo `tools/wallet-monitor/` removal aligning with §12.5 sibling-repo redundancy, wallet-experiment §15 Phase 0 sign-off reconciled with EAT §21.e real-money-phase deferral); 1 form-2 deferral (memory/MEMORY.md long-entry shortening filed as B-0072 P2 to avoid spine-file cascade churn on the open PR queue); 3 form-2 stale-snapshot closures (chatgpt-codex-connector + copilot reviewers cited filenames `memory/user_sister_elisabeth.md` + `memory/feedback_trust_guarded_with_elisabe...` that do NOT exist anywhere in the repo — empirical `grep -ri "elisabeth" memory/ docs/ tools/` returns ONLY the tick-history row's own prose; PR #73 commit 6cbe7e2 had renamed all 57 in-repo occurrences before the tick was written). (5) **B-0072 filed** for MEMORY.md index entry length normalization, on the PR #72 branch (not yet on `acehack/main` — pending PR #72 merge); composes with B-0066 auto-generated-index structural fix. (6) **Cron `ff34da97`** verified live via CronList. Drift this tick: AceHack +2 ahead from #92 + #87 landing; LFG unchanged. PR #72 awaiting CI rerun on 51f3690 then auto-merge fires. | (post-compaction drain-and-merge tick) | **Observation — post-compaction state-recovery via gh API queries works**: session resumed without conversation history; first queries (gh pr list + thread counts via GraphQL) reconstructed enough state to drive 2 PR merges + 11 thread drains in ~12 minutes. Class-1 BLOCKED-investigate-threads-first per Otto-355 immediately surfaced the actionable work; no manufactured patience or wait-state ambiguity. **Observation — `autoMergeRequest:null` is its own BLOCKED-class variant** (NOT in the 5-class taxonomy; this is a 6th class candidate): PR #92 was CLEAN MERGEABLE with no auto-merge armed — neither blocked NOR merging, just sitting unmerged. The fix was trivial (`gh pr merge --auto`) but the diagnostic is non-obvious. Add to calibration memory in next round: 6-class BLOCKED+stuck taxonomy = (1) threads, (2) failing/pending CI, (3) merge conflicts, (4) required-check missing, (5) ruleset gates, (6) auto-merge not armed on CLEAN PR. **Observation — stale-snapshot reviewer empirical-falsification form-2 closure is the right shape** for false-positives that cite specific filenames: `grep` is the discriminator. The reviewer hallucinated/cached the elisabeth filenames; verification took 30 seconds; closure with citation preserves both the agent's correctness and the reviewer's signal-validity. The bug is upstream of me (reviewer's snapshot/cache); my job is to verify and document, not to silently change correct content to match. **Observation — additive-keep-both + rerere is now stable across 5 cascade events**: cascade #5 followed cascades #1-#4 with the same shape (HEAD's new entries + main's new entries → ordered chronologically with most-recent-merged-from-main first). rerere has recorded resolutions; future cascades on this exact merge-base may auto-resolve. **Observation — context-compaction discipline held**: the conversation summary preserved enough operational substrate (5-class BLOCKED taxonomy, 7-class false-positive catalog, recent PR state) to immediately resume productive work without re-asking Aaron for context. The summary's tick-by-tick narration is what made the post-compaction recovery a 30-second state-rebuild instead of a 30-minute one. |