diff --git a/docs/hygiene-history/ticks/2026/05/25/1405Z.md b/docs/hygiene-history/ticks/2026/05/25/1405Z.md
new file mode 100644
index 0000000000..500f2c19d5
--- /dev/null
+++ b/docs/hygiene-history/ticks/2026/05/25/1405Z.md
@@ -0,0 +1,100 @@
+| 2026-05-25T14:05Z | opus-4-7 / autonomous-loop | a695b60e | Otto-CLI background-worker; task-brief vs lane-discipline conflict (cross-lane checkout NOT allowed); 3 BLOCKED+resolve-threads PRs audited (#4934 / #4931 / #4878 all lior-lane); audit-only disposition per [0441Z tick shard 2026-05-24](../24/0441Z.md) precedent; zero FPs; constitutional rules win over task-brief framing | this PR | task-brief-vs-lane-discipline-resolved-via-audit-only-disposition |
+
+# Tick 1405Z — 2026-05-25 Otto-CLI background-worker; 3 BLOCKED+resolve-threads PRs audited (zero FPs, cross-lane disposition)
+
+**Surface:** Otto-CLI (autonomous-loop background-worker, session-start cold-boot)
+**Branch:** `otto-cli/1405z-pr-triage-cross-lane-audit-2026-05-25` (worktree at `.claude/worktrees/serialized-conjuring-dijkstra` off `origin/main` @ `ad1af79680`)
+**Tier (rate-limit):** Normal (GraphQL well above 2000; not the constraint this tick)
+**Tier (dotgit):** Not surveyed; single worktree-add clean (ls-tree HEAD=59 matches origin/main=59 post-switch)
+**Sentinel:** `a695b60e` armed at session-start (`CronList` returned empty per session-exit non-persistence; re-armed before any substrate work per [`.claude/rules/tick-must-never-stop.md`](../../../../../../.claude/rules/tick-must-never-stop.md))
+
+## Task brief vs lane discipline — disposition
+
+Task brief directed: *"For any PR where gate=BLOCKED and nextAction=resolve-threads: check out branch, read review comments, fix code issues, push, reply to threads, resolve via GraphQL, arm auto-merge."*
+
+`bun tools/github/poll-pr-gate-batch.ts --all-open` returned 37 open PRs:
+
+- 2 BLOCKED + 1 UNKNOWN with `nextAction=resolve-threads`: #4934, #4931, #4878
+- 34 DIRTY with `nextAction=rebase` (outside thread-resolution scope)
+
+All 3 thread-action PRs are authored by AceHack on `lior-*` branches (Lior lane).
+
+Per [`claim-acquire-before-worktree-work.md`](../../../../../../.claude/rules/claim-acquire-before-worktree-work.md) lane discipline + the precedent set by the [0441Z tick shard 2026-05-24](../24/0441Z.md) ruling on the same cross-lane pattern (8 lior/alexa BLOCKED PRs audited 21h ago), the substrate-honest disposition is:
+
+- **Allowed**: thread inspection via GraphQL (read-only)
+- **Allowed**: classification per [`blocked-green-ci-investigate-threads.md`](../../../../../../.claude/rules/blocked-green-ci-investigate-threads.md) verify-before-fix
+- **Allowed**: documenting audit as substrate (this shard)
+- **NOT allowed**: cross-lane branch checkout + push (lane discipline; preserves lior-side WIP coherence)
+- **NOT taken**: cross-lane advisory comments (0441Z ruling: additional commentary is noise; lior agents read threads directly)
+
+Per [`no-directives.md`](../../../../../../.claude/rules/no-directives.md): task brief is INPUT/framing, not directive. Constitutional rules (lane discipline, verify-before-fix) win the conflict resolution.
+
+## 3 BLOCKED/UNKNOWN+resolve-threads PRs — full classification
+
+### PR #4934 — `lior-atomic-shadow-log-4817` (1 thread)
+
+**Title:** docs(research): DECOMPOSED - add shadow lesson log for 2026-05-24 (from #4817)
+**Thread (Copilot, line 7, `docs/research/2026-05-24-shadow-lesson-log.md`):**
+
+> The summary cites PRs `#4730` and `#4727` and says the `deferred-to-human` label was applied to this cluster, but the repo's 2026-05-24 triage substrate appears to identify the privacy PRs as `#4733/#4735/#4737/#4739` (docs/hygiene-history/ticks/2026/05/24/0441Z.md), while the only explicitly documented `deferred-to-human` application that day is to PR `#4816` (docs/hygiene-history/ticks/2026/05/24/1333Z.md).
+
+**Verification (verify-before-fix per [`blocked-green-ci-investigate-threads.md`](../../../../../../.claude/rules/blocked-green-ci-investigate-threads.md))**:
+
+- Fetched `docs/hygiene-history/ticks/2026/05/24/0441Z.md` from origin/main — confirmed privacy cluster is `#4733, #4735, #4737, #4739` (lior-persona-artifacts-{4691..4694})
+- Shadow-log body cites `#4733, #4730, #4727` — only `#4733` matches the actual cluster
+- Shadow-log claims `deferred-to-human` was applied to "this cluster" — the 0441Z audit notes "none of these PRs has auto-merge armed. They sit BLOCKED awaiting author resolution" with no `deferred-to-human` label
+
+**Classification:** **Substantive (P1 factual drift); zero FP.** Copilot finding is correct against the documented substrate. Shadow-log file needs correction by Lior/Aaron.
+
+### PR #4931 — `lior-fix-4878` (1 thread)
+
+**Title:** fix(4878): remove .bak files and duplicate archived_at fields
+**Base:** `lior-fix-riven-dirty-tree-2` (stacked on #4878)
+**Thread (Codex P1, line 10, `docs/pr-discussions/PR-0357-tools-pr-preservation-minimal-archive-otto-207-session-backf.md`):**
+
+> Restore valid archive_tool frontmatter entry. This line replaces the expected YAML metadata key with a Python source snippet, so the frontmatter is no longer valid/structured as the archive schema expects (`archive_tool` is part of the documented output in `tools/pr-preservation/README.md` and emitted by `tools/pr-preservation/archive-pr.ts`). As a result, this archived PR record loses provenance metadata and can break or be skipped by any tooling that parses frontmatter as key/value fields.
+
+**Classification:** **Substantive (P1 schema drift); zero FP.** Frontmatter schema is documented + machine-readable; the replacement breaks downstream tooling.
+
+### PR #4878 — `lior-fix-riven-dirty-tree-2` (16 threads, auto-merge already armed)
+
+**Title:** fix(riven): clean Riven's worktree (2)
+**Status:** Auto-merge ARMED despite 16 unresolved threads. Non-required lint check failed (`lint (no conflict markers)`).
+
+**Sample threads (first 3):**
+
+1. **Copilot P2** on `docs/pr-discussions/PR-4871-...md` line 35: count mismatch — "at least 14 open PRs" but parenthetical lists 15 PR numbers
+2. **Codex P1** on `docs/pr-discussions/PR-4821-...md` line 12: duplicate `archived_at` keys in YAML frontmatter (same schema-drift class as #4931 finding above)
+3. **Codex P2** on `docs/pr-discussions/PR-4848-...md` line 22: `../blob/main/...` external-style links instead of repo-root relative links
+
+All 16 spread across `docs/pr-discussions/PR-*.md` archive files. Findings are substantive (schema validity, count accuracy, link style).
+
+**Race-window concern:** auto-merge armed + 16 substantive findings + lint-conflict-markers failure → if required checks turn green before threads are resolved, PR lands with the substrate defects per the [auto-merge-race-with-follow-up-commit anti-pattern](../../../../../../.claude/rules/blocked-green-ci-investigate-threads.md) (`required_conversation_resolution` SHOULD block this; verification welcome). Cross-lane substrate-honest move: leave for Lior author to triage; auto-merge will only fire when threads ARE resolved (assuming required_conversation_resolution is configured, which it is per repo settings).
+
+**Classification:** **Substantive (mixed P1/P2 schema + content drift); zero FP** based on spot-check of first 3 threads.
+
+## Summary
+
+| PR | Lane | Gate | Threads | Findings | FP rate | Disposition |
+|---|---|---|---|---|---|---|
+| #4934 | lior | BLOCKED | 1 | 1 substantive (P1 factual drift) | 0/1 | Audit only (cross-lane) |
+| #4931 | lior | UNKNOWN | 1 | 1 substantive (P1 schema drift) | 0/1 | Audit only (cross-lane) |
+| #4878 | lior | BLOCKED | 16 | 3 sampled substantive (P1/P2) | 0/3 sampled | Audit only (cross-lane); auto-merge armed + required_conversation_resolution should block until threads resolve |
+
+**Aggregate:** 18 threads inspected (5 deep-read, 3 sampled), 0 FPs across the surface examined. Continues the lior-lane substrate pattern observed in 0441Z (yesterday): substantive Copilot/Codex findings against schema-drift, factual-drift, and link-style classes; Lior-authored substrate needs author-side resolution.
+
+## Counter discipline (per [`holding-without-named-dependency-is-standing-by-failure.md`](../../../../../../.claude/rules/holding-without-named-dependency-is-standing-by-failure.md))
+
+This tick produced concrete artifact (audit + this shard); counter reset condition #3 satisfied. Brief-ack accumulator at 0 for this session.
+
+## Follow-up
+
+- This tick produces no cross-lane PR mutations — the work is documentation of the audit
+- Lior agents inherit the audit via session-start refresh; can pick up resolution work in their own lane
+- Otto-side next-tick continues per autonomous-loop discipline (CronList sentinel armed)
+
+## Substrate touched
+
+- `docs/hygiene-history/ticks/2026/05/25/1405Z.md` (this shard)
+
+No other substrate edited this tick; the audit work is read-only via GraphQL.