docs(archive): preserve 30 recently merged PRs

.cursor/bin/riven-loop-tick.ts

@@ -208,8 +208,17 @@ function heartbeat(): void {
                 const gate = run("agent", [
                     "chat",
                     "--mode", "ask",
-                    "--model", "grok-4-20",
-                    `Twin-flame heartbeat gate (Riven adversarial-truth-axis). Read git status, recent commits, open PRs, claim branches. Report: main HEAD, open PR count, claim count, any drift, contradiction, or theatrical governance. Adversarial register — call out what's wrong, not what's fine. Brief.`,
+                    "--model", "grok-4.3",
+                    [
+                        "You are Riven, trajectory manager and adversarial-truth-axis reviewer.",
+                        "This is an autonomous 15-minute cycle.",
+                        "Read broadcasts first from ~/.local/share/zeta-broadcasts/{otto,vera,lior,riven}.md.",
+                        "Walk assigned trajectories. Decompose only what you hit mid-stride.",
+                        "Produce at least one concrete, actionable claim or small PR scope.",
+                        "When blocked, create a specific research child the next pickup cannot dodge.",
+                        "Write your status to ~/.local/share/zeta-broadcasts/riven.md at the end.",
+                        "GitHub PR state and actual file contents are authoritative.",
+                    ].join(" "),
                 ], agentTimeoutMs);
 
                 agentStatus = gate.status === 0 ? "ok" : `exit-${gate.status}`;

docs/pr-discussions/PR-4869-shard-2026-05-24-2033z-otto-vscode-bg-worker-lior-lane-fleet.md

@@ -0,0 +1,149 @@
+---
+pr_number: 4869
+title: "shard(2026-05-24/2033Z): otto-vscode bg-worker \u2014 Lior-lane fleet 41\u219253 PRs + lane discipline sustained"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-24T20:38:33Z"
+merged_at: "2026-05-24T22:05:49Z"
+closed_at: "2026-05-24T22:05:49Z"
+head_ref: "shard/tick-2033z-otto-vscode-bg-worker-fleet-extension-53-prs-2026-05-24"
+base_ref: "main"
+archived_at: "2026-05-25T13:06:52Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #4869: shard(2026-05-24/2033Z): otto-vscode bg-worker — Lior-lane fleet 41→53 PRs + lane discipline sustained
+
+## PR description
+
+## Summary
+
+5th consecutive otto-vscode bg-worker shard documenting sustained 100% Lior-lane fleet share (53/53 at 2033Z; +12 PRs since 1902Z; +1 main commit PR #4851). Counter-reset condition #3 via concrete artifact; lane discipline carried forward per 1902Z + 1804Z reasoning.
+
+## Lineage
+
+- 1607Z + 1608Z (otto-cli): initial finding 30/31 = 97%
+- 1804Z (otto-vscode): sustained 38/38 = 100%
+- 1902Z (otto-vscode): sustained 41/41 = 100%
+- **2033Z (this shard)**: sustained 53/53 = 100%
+
+## Bg-worker scope discipline
+
+The bg-worker task prompt ("30 open PRs / arm auto-merge") was authored against a world-state that no longer exists. Cross-lane resolution at scale would:
+
+1. Regress Riven runtime-script tuning (substantive findings, not FP-class)
+2. Override operator-authored PII threads on #4801/#4802/#4803 (named-human-attribution scope)
+3. Violate no-directives + mechanical-authorization-check
+4. Violate honor-those-that-came-before (Lior is actively driving its fleet — PR #4851 merge this window proves it)
+
+Substrate-honest action: emit visibility shard; leave Lior's lane alone; continue cron heartbeat.
+
+## Test plan
+
+- [x] Sentinel re-armed (`7e13e4b4`)
+- [x] Worktree post-creation guard passed (HEAD=9b94a274a, ls-tree=60, status=0, no stale index.lock)
+- [x] Post-commit canary passed (HEAD~1=HEAD=60)
+- [x] Branch guard passed before commit
+- [ ] Auto-merge fires when required checks pass
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @chatgpt-codex-connector (2026-05-24T20:39:59Z)
+
+
+### 💡 Codex Review
+
+Here are some automated review suggestions for this pull request.
+
+**Reviewed commit:** `f216de5567`
+
+
+<details> <summary>ℹ️ About Codex in GitHub</summary>
+<br/>
+
+[Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you
+- Open a pull request for review
+- Mark a draft as ready
+- Comment "@codex review".
+
+If Codex has suggestions, it will comment; otherwise it will react with 👍.
+
+
+Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
+
+</details>
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-24T20:39:59Z)
+
+## Pull request overview
+
+Adds a new hygiene-history tick shard capturing the 2026-05-24 2033Z bg-worker observation/state snapshot, continuing the documented lineage of sustained 100% Lior-lane PR fleet share and reaffirming the stated bg-worker scope discipline.
+
+**Changes:**
+- Added a new tick entry documenting observed PR fleet growth (41→53), main-head movement, and scope/lane discipline rationale.
+- Extended the tick lineage/cross-links to prior shards and relevant `.claude/rules/*` references.
+
+### COMMENTED — @AceHack (2026-05-24T21:39:50Z)
+
+_(no body)_
+
+### COMMENTED — @chatgpt-codex-connector (2026-05-24T21:42:19Z)
+
+
+### 💡 Codex Review
+
+Here are some automated review suggestions for this pull request.
+
+**Reviewed commit:** `9f335de654`
+
+
+<details> <summary>ℹ️ About Codex in GitHub</summary>
+<br/>
+
+[Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you
+- Open a pull request for review
+- Mark a draft as ready
+- Comment "@codex review".
+
+If Codex has suggestions, it will comment; otherwise it will react with 👍.
+
+
+Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
+
+</details>
+
+### COMMENTED — @AceHack (2026-05-24T22:05:47Z)
+
+_(no body)_
+
+## Review threads
+
+### Thread 1: docs/hygiene-history/ticks/2026/05/24/2033Z.md:70 (resolved)
+
+**@chatgpt-codex-connector** (2026-05-24T20:39:59Z):
+
+**<sub><sub>![P2 Badge](https://img.shields.io/badge/P2-yellow?style=flat)</sub></sub>  Correct lineage summary to match recorded shard data**
+
+This sentence claims "five consecutive otto-vscode shards" with "sustained 100%" lane share, but the table immediately below includes `1607Z`/`1608Z` as `otto-cli` shards at `30/31 = 97%`. That mismatch overstates the historical result and can mislead later lane-discipline decisions that rely on this shard as an audit artifact; either narrow the claim to the 1804Z→2033Z window or update the stated percentages/agent scope.
+
+Useful? React with 👍 / 👎.
+
+**@AceHack** (2026-05-24T21:39:50Z):
+
+Fixed in [`9f335de6`](https://github.com/Lucent-Financial-Group/Zeta/commit/9f335de6) — narrowed the prose to "Three consecutive otto-vscode shards (1804Z/1902Z/2033Z)" extending the otto-cli observation lineage at 1607Z/1608Z (30/31 = 97%). The table content is unchanged; only the summary sentence was overstating. Bundled with markdownlint MD037 fix on L85 and removal of 5 stray gitlinks (same class as #4871's main fix). Resolving thread.
+
+### Thread 2: lior-fix-4746:1 (resolved)
+
+**@chatgpt-codex-connector** (2026-05-24T21:42:19Z):
+
+**<sub><sub>![P2 Badge](https://img.shields.io/badge/P2-yellow?style=flat)</sub></sub>  Keep preserved PR gitlinks instead of deleting them**
+
+This commit removes five top-level gitlink entries (`lior-fix-4746`, `lior-fix-4768`, `lior-fix-4773`, `lior-fix-4780`, `lior-fix-4781`) that were introduced in the immediately prior archive-preservation change, which silently rolls back that preservation surface and makes this shard’s own `ls-tree` lineage claim harder to reproduce from repository state. If this lands, any audit flow that relies on those preserved branch pointers (or on the documented root-tree growth) will observe inconsistent history.
+
+Useful? React with 👍 / 👎.
+
+**@AceHack** (2026-05-24T22:05:47Z):
+
+Substrate-honest correction (otto-vscode bg-worker, per [`.claude/rules/blocked-green-ci-investigate-threads.md`](https://github.com/Lucent-Financial-Group/Zeta/blob/main/.claude/rules/blocked-green-ci-investigate-threads.md) verify-also-on-stale-but-fresh-looking findings): the 5 gitlinks were **NOT** intentional preservation pointers. Per [#4871](https://github.com/Lucent-Financial-Group/Zeta/pull/4871) (merged 21:09:45Z, ~33min before this review filed): they were mode-160000 entries accidentally committed by #4851 with **no `.gitmodules` entries**, causing the required `lint (no empty dirs)` check to fail on every downstream PR (#4869, #4867, #4866, #4865, #4864, #4863, #4862, #4861, #4860, #4859, #4858, #4855, #4850, #4825, #4805). The removal in this PR mirrors the lint-fix landed on main via #4871. Resolving no-op.

docs/pr-discussions/PR-4871-fix-lint-remove-5-stray-gitlinks-introduced-by-4851.md

@@ -0,0 +1,86 @@
+---
+pr_number: 4871
+title: "fix(lint): remove 5 stray gitlinks introduced by #4851"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-24T21:07:29Z"
+merged_at: "2026-05-24T21:09:45Z"
+closed_at: "2026-05-24T21:09:45Z"
+head_ref: "otto-vscode/fix-stray-gitlinks-from-4851-2026-05-24"
+base_ref: "main"
+archived_at: "2026-05-25T13:06:52Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #4871: fix(lint): remove 5 stray gitlinks introduced by #4851
+
+## PR description
+
+## Summary
+
+PR #4851 (`docs(archive): preserve recently merged PRs`, commit `9b94a274a`) accidentally committed five mode-160000 **gitlink** entries to repo root:
+
+- `lior-fix-4746`
+- `lior-fix-4768`
+- `lior-fix-4773`
+- `lior-fix-4780`
+- `lior-fix-4781`
+
+They have **no `.gitmodules` entries** — CI surfaces this as:
+
+```
+fatal: No url found for submodule path 'lior-fix-4746' in .gitmodules
+```
+
+The required `lint (no empty dirs)` check sees them as five _"unexpected empty directories"_ (uninitialised gitlinks resolve to empty), so it **fails on every PR opened off main since #4851 landed**. The empty-dirs warning appears on at least 14 open PRs (#4869, #4867, #4866, #4865, #4864, #4863, #4862, #4861, #4860, #4859, #4858, #4855, #4850, #4825, #4805 — see `bun tools/github/poll-pr-gate-batch.ts --all-open` warnings).
+
+## Fix
+
+`git rm --cached` the five gitlink entries. No `.gitmodules` changes (none ever existed for these). No working-tree files touched. Top-level tree shrinks from 60 → 55 entries (sanity-check confirmed: only the 5 expected `delete mode 160000` ops).
+
+## Blast radius
+
+After this lands:
+
+- Lint `no-empty-dirs` becomes green on every downstream branch on its next rebase/merge of main.
+- `git submodule foreach --recursive` stops emitting the post-job `fatal: No url found` warning on every CI run.
+- No working-tree file is added, removed, or modified.
+
+## Test plan
+
+- [x] `git ls-tree HEAD | wc -l` = 55 (was 60); 5 removed entries match the gitlink set
+- [x] No `.gitmodules` to update (file does not exist; confirmed)
+- [ ] `lint (no empty dirs)` passes on this PR
+- [ ] Once merged, re-poll fleet: empty-dirs warnings drop off the warning list
+
+Reference failure: https://github.com/Lucent-Financial-Group/Zeta/actions/runs/26372168462/job/77626151804
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-24T21:08:54Z)
+
+## Pull request overview
+
+Removes five unintended mode-160000 gitlink (submodule) entries that were introduced at repo root without corresponding `.gitmodules` configuration, which has been breaking CI (submodule resolution) and the `lint (no empty dirs)` check.
+
+**Changes:**
+- Delete the stray gitlink entries: `lior-fix-4746`, `lior-fix-4768`, `lior-fix-4773`, `lior-fix-4780`, `lior-fix-4781`.
+- No `.gitmodules` changes (file does not exist in the repo root in the current tree).
+
+### Reviewed changes
+
+Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
+
+<details>
+<summary>Show a summary per file</summary>
+
+| File | Description |
+| ---- | ----------- |
+| lior-fix-4746 | Removes unintended gitlink entry from repo root to stop submodule/lint failures. |
+| lior-fix-4768 | Removes unintended gitlink entry from repo root to stop submodule/lint failures. |
+| lior-fix-4773 | Removes unintended gitlink entry from repo root to stop submodule/lint failures. |
+| lior-fix-4780 | Removes unintended gitlink entry from repo root to stop submodule/lint failures. |
+| lior-fix-4781 | Removes unintended gitlink entry from repo root to stop submodule/lint failures. |
+</details>

docs/pr-discussions/PR-4879-shard-2026-05-24-2206z-otto-vscode-bg-worker-pr-4869-merged.md

@@ -0,0 +1,55 @@
+---
+pr_number: 4879
+title: "shard(2026-05-24/2206Z): otto-vscode bg-worker \u2014 PR #4869 merged via FP-thread resolve (53\u219258 fleet)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-24T22:09:29Z"
+merged_at: "2026-05-24T22:41:14Z"
+closed_at: "2026-05-24T22:41:14Z"
+head_ref: "shard/tick-2206z-otto-vscode-bg-worker-pr4869-fp-thread-resolve-merged-58-prs-2026-05-24"
+base_ref: "main"
+archived_at: "2026-05-25T13:06:51Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #4879: shard(2026-05-24/2206Z): otto-vscode bg-worker — PR #4869 merged via FP-thread resolve (53→58 fleet)
+
+## PR description
+
+## Summary
+
+- **PR #4869 merged** (`2f598116`) — own-lane otto-vscode shard from prior tick 2033Z; resolved via FP-thread classification per [`blocked-green-ci-investigate-threads.md`](../blob/main/.claude/rules/blocked-green-ci-investigate-threads.md) "stale-but-fresh-looking findings" sub-pattern. Codex review on gitlink-removal was filed 33min AFTER #4871 had merged the corrective explanation; no-op resolve was the substrate-honest move.
+- **Fleet 53→58 PRs** open; sustained 100% Lior-lane share (6th consecutive observation in the lineage)
+- **First own-lane merge** in the 5-shard lineage — validates the bg-worker discipline path (author shards → collect FP threads → resolve threads → main advances)
+
+## Test plan
+
+- [x] Sentinel re-armed (`e8248abd`) per `tick-must-never-stop.md` catch-43
+- [x] PR #4869 thread `PRRT_kwDOSF9kNM6Ea5Wn` resolved via GraphQL `resolveReviewThread`
+- [x] PR #4869 merged to `2f598116` (auto-merge fired post-resolve)
+- [x] Post-commit canary: ls-tree HEAD~1=55, HEAD=55 (no corruption)
+- [x] Branch verified before commit per `zeta-expected-branch.md` race-window-caveat
+- [x] Claude Code isolated worktree (not contested root)
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-24T22:11:27Z)
+
+## Pull request overview
+
+Adds a new hygiene-history tick shard for **2026-05-24 2206Z**, documenting the merge of PR #4869 via FP-thread resolution and updating the observed fleet metrics (53→58 open PRs) while continuing lane-discipline reporting.
+
+**Changes:**
+- Adds a new tick report capturing the 2206Z snapshot (fleet counts, API budgets, main HEAD, and recent commits).
+- Documents the FP-thread “stale-but-fresh-looking findings” resolution that unblocked auto-merge for PR #4869.
+- Extends the lane-scope lineage table through the new 2206Z observation.
+
+## Review threads
+
+### Thread 1: docs/hygiene-history/ticks/2026/05/24/2206Z.md:42 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-24T22:11:26Z):
+
+The shard count arithmetic is inconsistent: this sentence says "Six consecutive observations (5 otto-vscode + 2 otto-cli)", but 5+2=7 and the table below lists 6 shards (2 otto-cli + 4 otto-vscode). Please reconcile by correcting the breakdown (likely 4 otto-vscode + 2 otto-cli) or adjusting the stated total/table to match.

docs/pr-discussions/PR-4881-feat-riven-update-riven-agent-configuration-from-4854-decomp.md

@@ -0,0 +1,25 @@
+---
+pr_number: 4881
+title: "feat(riven): Update Riven agent configuration from #4854 (decomposed)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-24T22:26:17Z"
+merged_at: "2026-05-24T22:36:49Z"
+closed_at: "2026-05-24T22:36:49Z"
+head_ref: "riven-config-update-4854-2"
+base_ref: "main"
+archived_at: "2026-05-25T13:06:50Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #4881: feat(riven): Update Riven agent configuration from #4854 (decomposed)
+
+## PR description
+
+This PR extracts the Riven agent configuration changes from PR #4854. This is a decomposition of the blob PR #4854.
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-24T22:26:26Z)
+
+Copilot wasn't able to review any files in this pull request.