docs(archive): preserve PR #4835 + #4853

docs/pr-discussions/PR-4835-shard-2026-05-24-1607z-dotgit-saturation-15th-observation-2h.md

@@ -0,0 +1,96 @@
+---
+pr_number: 4835
+title: "shard(2026-05-24/1607Z): dotgit-saturation 15th observation (2h-sustained 0-reading window)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-24T16:11:10Z"
+merged_at: "2026-05-24T16:21:09Z"
+closed_at: "2026-05-24T16:21:09Z"
+head_ref: "otto/shard-1607z-sustained-recovery-2026-05-24"
+base_ref: "main"
+archived_at: "2026-05-24T20:21:28Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #4835: shard(2026-05-24/1607Z): dotgit-saturation 15th observation (2h-sustained 0-reading window)
+
+## PR description
+
+## Summary
+
+- 15th anchor at 16:07Z UTC confirms PR #4820's 14th-observation 0-reading
+- **2h sustained 0 stuck git pack/maintenance/repack procs** — first multi-anchor 0-window in the 28h dotgit-saturation arc
+- Fleet drain evidence: peer 15→9, Lior 3→1 across the 14:07Z→16:07Z window
+- Probational-recovery sub-tier classification earns first multi-anchor empirical support
+
+## Hypotheses preserved (default-to-both)
+
+- **A**: Genuine multi-day cycle clearing — strongest support; fleet drain across 2h aligns
+- **B**: Maintainer-side cleanup at ~12:21Z eliminated contention surface — partial fit (fleet drain not yet predicted)
+- **C**: 12:26Z "repo vanished" was transient snapshot — unresolvable from observation alone
+
+Not yet collapsing the arc to "terminated"; awaits 16th anchor at 18:07Z+ to either extend the recovery window to 4h or refute via rebound.
+
+## Composes with
+
+- PR #4820 (14th observation; this shard's "Next-tick observation candidates" enacted)
+- \`.claude/rules/refresh-world-model-poll-pr-gate.md\` dotgit-saturation tier framing
+- \`.claude/rules/default-to-both.md\` preservation discipline
+- \`.claude/rules/tick-must-never-stop.md\` catch-43 sentinel re-arm (sentinel \`9046536a\`)
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @chatgpt-codex-connector (2026-05-24T16:12:41Z)
+
+
+### 💡 Codex Review
+
+Here are some automated review suggestions for this pull request.
+
+**Reviewed commit:** `7466e1a549`
+
+
+<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-24T16:13:08Z)
+
+## Pull request overview
+
+Adds an in-repo tick shard documenting the 16:07Z (15th) dotgit-saturation observation, capturing a second consecutive 0-stuck-procs reading and related operational measurements for the ongoing hygiene-history arc.
+
+**Changes:**
+- Adds a new tick shard for 2026-05-24 16:07Z with observed-state measurements and an updated 15-anchor rolling table.
+- Records hypothesis status and next-tick observation candidates to guide the subsequent 18:07Z anchor.
+
+## Review threads
+
+### Thread 1: docs/hygiene-history/ticks/2026/05/24/1607Z.md:120 (resolved)
+
+**@chatgpt-codex-connector** (2026-05-24T16:12:41Z):
+
+**<sub><sub>![P2 Badge](https://img.shields.io/badge/P2-yellow?style=flat)</sub></sub>  Align peer-fleet threshold with recorded baseline**
+
+The `18:07Z peer-fleet count` criterion uses `5` as the starting total, but this shard records `peer = 9` and `Lior = 1` (baseline `10`), so the decision rule is internally inconsistent. That can misclassify the next anchor (e.g., a drop from 10 to 6 would be meaningful drain but would fail the current `5 -> <5` test), which weakens the experiment log’s comparability across anchors.
+
+Useful? React with 👍 / 👎.
+
+### Thread 2: docs/hygiene-history/ticks/2026/05/24/1607Z.md:120 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-24T16:13:07Z):
+
+P1: In "Next-tick observation candidates", the peer-fleet bullet uses totals of "5 total → <5" and "5 → 15+", but the observed-state table above reports peer=9 and Lior=1 (total 10) at 16:07Z. Update these totals to match the current readings (or clarify what the "5" is referring to) so the candidate criteria aren’t internally inconsistent.

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

@@ -0,0 +1,134 @@
+---
+pr_number: 4853
+title: "shard(2026-05-24/1902Z): otto-vscode bg-worker \u2014 Lior-lane fleet 38\u219241 PRs + lane discipline re-applied"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-24T19:05:12Z"
+merged_at: "2026-05-24T19:35:28Z"
+closed_at: "2026-05-24T19:35:28Z"
+head_ref: "otto-vscode/tick-1902z-bg-worker"
+base_ref: "main"
+archived_at: "2026-05-24T20:17:52Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #4853: shard(2026-05-24/1902Z): otto-vscode bg-worker — Lior-lane fleet 38→41 PRs + lane discipline re-applied
+
+## PR description
+
+## Summary
+
+Bg-worker tick shard documenting Lior-lane fleet extension 38→41 PRs (~58 min since [1804Z](docs/hygiene-history/ticks/2026/05/24/1804Z.md)) with no `origin/main` commits in the window.
+
+## State observed at 1902Z
+
+- 41 open PRs, **41/41 = 100% Lior-lane** (sustained from 1804Z)
+- otto-vscode own-lane: **0 PRs** (bg-worker prompt's "30 PRs" target empty in own lane)
+- 3 new since 1804Z (#4850, #4851, #4852) — continuation of `lior-decompose-4828-*` cluster
+- #4852 touches `.cursor/bin/riven-loop-tick.ts` — runtime-script special-case per [`backlog-item-start-gate.md`](.claude/rules/backlog-item-start-gate.md) guard
+- `origin/main` HEAD `27d114290` unchanged since 1804Z; 0 commits in 60min window
+- ls-tree HEAD = 55 (no canary corruption)
+
+## Substrate discipline applied
+
+Per [`agent-roster-reference-card.md`](.claude/rules/agent-roster-reference-card.md) lane discipline + [`pr-triage-tiers.md`](.claude/rules/pr-triage-tiers.md) Tier 5 + [`no-directives.md`](.claude/rules/no-directives.md) + [`mechanical-authorization-check.md`](.claude/rules/mechanical-authorization-check.md): bg-worker task prompt does NOT override standing lane discipline. Cross-lane auto-resolution on runtime-script-touching PRs would regress Riven tuning; operator-authored armed PRs (#4801/#4802/#4803) cannot be unilaterally overridden.
+
+Counter-reset condition #3 (concrete artifact) satisfied per [`holding-without-named-dependency-is-standing-by-failure.md`](.claude/rules/holding-without-named-dependency-is-standing-by-failure.md).
+
+## Test plan
+
+- [x] sentinel re-armed at cold-boot (`7e6df89b`)
+- [x] isolated worktree authored shard (post-creation freshness check: ls-tree=55, status=0)
+- [x] post-commit canary check: parent tree 55, HEAD tree 55
+- [x] push verified via `git ls-remote` (08724f0b on remote matches local)
+- [x] composes-with chain referenced (1608Z → 1804Z → this)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-24T19:06:54Z)
+
+## Pull request overview
+
+Adds a new hygiene-history tick shard documenting the 2026-05-24 1902Z background-worker observation (Lior-lane PR fleet growth 38→41, no `origin/main` movement, and re-confirmed lane discipline / non-auto-resolution stance for runtime-script-touching PRs).
+
+**Changes:**
+- Introduces a new tick entry (`1902Z.md`) with updated fleet counts, PR triage notes, and cross-links to relevant rules and prior ticks.
+- Records the current operational state (rate limits, processes, `origin/main` head, ls-tree baseline) and composes-with lineage for future ticks.
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-24T19:30:37Z)
+
+## Pull request overview
+
+Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.
+
+### COMMENTED — @AceHack (2026-05-24T19:34:49Z)
+
+_(no body)_
+
+### COMMENTED — @AceHack (2026-05-24T19:34:50Z)
+
+_(no body)_
+
+### COMMENTED — @AceHack (2026-05-24T19:34:51Z)
+
+_(no body)_
+
+### COMMENTED — @AceHack (2026-05-24T19:34:52Z)
+
+_(no body)_
+
+### COMMENTED — @AceHack (2026-05-24T19:34:53Z)
+
+_(no body)_
+
+## Review threads
+
+### Thread 1: docs/hygiene-history/ticks/2026/05/24/1902Z.md:22 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-24T19:06:53Z):
+
+The markdown table header/rows here start with `||` (double pipe), which introduces an unintended empty first column and differs from the single-pipe table formatting used in the other tick shards (e.g., 1608Z/1804Z). Switch these lines to the standard `| ... | ... |` form so the table renders as intended on GitHub.
+
+**@AceHack** (2026-05-24T19:34:49Z):
+
+Verified false-positive per `.claude/rules/blocked-green-ci-investigate-threads.md` table-double-pipe FP-class catalog. Direct `awk -v N=<line>` inspection of the file shows single-leading-pipe table rows (`| col | col |`), NOT double-pipe (`|| col | col |`). The reviewer claim is the canonical FP shape; resolved no-op.
+
+### Thread 2: docs/hygiene-history/ticks/2026/05/24/1902Z.md:39 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-24T19:06:54Z):
+
+This PR triage table also uses `||` at the start of each row, which will render with an extra blank column. Use the same single-leading-pipe table style as the other tick files to keep formatting consistent and readable.
+
+**@AceHack** (2026-05-24T19:34:50Z):
+
+Verified false-positive per `.claude/rules/blocked-green-ci-investigate-threads.md` table-double-pipe FP-class catalog. Direct `awk -v N=<line>` inspection of the file shows single-leading-pipe table rows (`| col | col |`), NOT double-pipe (`|| col | col |`). The reviewer claim is the canonical FP shape; resolved no-op.
+
+### Thread 3: docs/hygiene-history/ticks/2026/05/24/1902Z.md:29 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-24T19:30:36Z):
+
+The markdown table syntax here has an extra leading `|` (`|| ...`), which renders an unintended empty first column in GitHub Markdown. Match the table format used in earlier ticks (e.g., 1804Z) by using a single leading pipe on each row (`| Surface | Reading |`, `|---|---|`, etc.).
+
+**@AceHack** (2026-05-24T19:34:51Z):
+
+Verified false-positive per `.claude/rules/blocked-green-ci-investigate-threads.md` table-double-pipe FP-class catalog. Direct `awk -v N=<line>` inspection of the file shows single-leading-pipe table rows (`| col | col |`), NOT double-pipe (`|| col | col |`). The reviewer claim is the canonical FP shape; resolved no-op.
+
+### Thread 4: docs/hygiene-history/ticks/2026/05/24/1902Z.md:40 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-24T19:30:37Z):
+
+This PR table also uses `||` at the start of each row, creating an unintended empty column. Use the standard GFM table format (`| PR | Branch | Pattern |` and `|---|---|---|`) as in other tick shards to avoid rendering issues.
+
+**@AceHack** (2026-05-24T19:34:52Z):
+
+Verified false-positive per `.claude/rules/blocked-green-ci-investigate-threads.md` table-double-pipe FP-class catalog. Direct `awk -v N=<line>` inspection of the file shows single-leading-pipe table rows (`| col | col |`), NOT double-pipe (`|| col | col |`). The reviewer claim is the canonical FP shape; resolved no-op.
+
+### Thread 5: docs/hygiene-history/ticks/2026/05/24/1902Z.md:55 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-24T19:30:37Z):
+
+Several references are written as shortcut-style links like [`agent-roster-reference-card.md`] / [`pr-triage-tiers.md`] / [`no-directives.md`] but there are no reference definitions in this file, so these will render as plain bracketed text (broken links). Use explicit inline links with the correct relative paths (as done in 1804Z.md) or add reference definitions at the bottom.
+
+**@AceHack** (2026-05-24T19:34:53Z):
+
+Fixed in commit d24af5d1d on this branch — converted all 13 shortcut-style `[`file.md`]` references to explicit inline links `[`file.md`](../../../../../../.claude/rules/file.md)` following the existing convention used on line 52 + the sibling 1804Z.md shard. Per `.claude/rules/blocked-green-ci-investigate-threads.md` verify-before-fix: direct inspection confirmed the reviewer claim. Thank you for the catch.