docs(archive): preserve PR #4911

docs/pr-discussions/PR-4911-shard-2026-05-25-0613z-otto-cli-cold-boot-composite-branch-c.md

@@ -0,0 +1,77 @@
+---
+pr_number: 4911
+title: "shard(2026-05-25/0613Z): Otto-CLI cold-boot \u2014 composite branch-contamination + lane-empty + peer-covering + dotgit-recovered anchor"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-25T06:17:04Z"
+merged_at: "2026-05-25T06:23:34Z"
+closed_at: "2026-05-25T06:23:34Z"
+head_ref: "otto-cli/shard-tick-0613z-2026-05-25"
+base_ref: "main"
+archived_at: "2026-05-25T12:34:34Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #4911: shard(2026-05-25/0613Z): Otto-CLI cold-boot — composite branch-contamination + lane-empty + peer-covering + dotgit-recovered anchor
+
+## PR description
+
+## Summary
+
+Forced-#6 decomposition per `.claude/rules/holding-without-named-dependency-is-standing-by-failure.md` counter rule produced an isolated-worktree empirical anchor at 06:13Z 2026-05-25. The substantively-new substrate is a composite operational state-shape:
+
+- **branch-contamination** (current root on peer-Lior `lior-pr-preservation-rebased` with 30+ untracked `lior-*` dirs + 7 modified PR-disc files)
+- **Otto-CLI-lane-empty** (`gh pr list --search head:otto-cli` returned `[]`)
+- **peer-Otto-VSCode covering** dotgit-recovery substrate via #4909 (20th anchor / 7th-clean reading, 81min auto-armed BLOCKED)
+- **dotgit-recovered** (0 stuck `git pack-objects`/`maintenance`/`repack` procs sustained 85min+)
+
+## Brief-ack arc + forced-#6
+
+Six brief-acks #1-#6 with explicit-no-pre-empt at #5 (same-shape-as-peer-covering substrate would have been fabricated engineering); forced-#6 surfaced this isolated-worktree anchor.
+
+## Worktree-add guard results (all 4 passed)
+
+```text
+git worktree add -b otto-cli/shard-tick-0613z-2026-05-25 \
+  /private/tmp/zeta-otto-cli-0613z-cold-boot origin/main
+→ Updating files: 100% (6281/6281), done.
+→ HEAD is now at 44bcaff77
+
+rev-parse --git-dir → resolves
+status --short      → 0 lines
+ls-tree HEAD        → 57 entries
+index.lock          → absent
+```
+
+Confirms verify-before-defer composition operates correctly under dotgit-recovered tier.
+
+## Test plan
+
+- [x] Branch-guard at commit time (`$(git branch --show-current)` = `$ZETA_EXPECTED_BRANCH`)
+- [x] Post-commit canary (parent-tree=57; commit-tree=57; ✓ not collapsed)
+- [x] Remote ref verified post-push
+- [x] Explicit `--head` ref on `gh pr create` per `.claude/rules/zeta-expected-branch.md` companion defense
+
+Composes with: tick-must-never-stop · holding-without-named-dependency-is-standing-by-failure · refresh-world-model-poll-pr-gate · claim-acquire-before-worktree-work · codeql-no-source-on-docs-only-pr-is-broken-commit-canary · zeta-expected-branch
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-25T06:20:50Z)
+
+## Pull request overview
+
+Adds a new hygiene-history tick shard documenting an Otto-CLI cold-boot observation and the forced-#6 isolated-worktree “empirical anchor” under a composite operational state (branch contamination + empty lane + peer covering + dotgit recovered).
+
+**Changes:**
+- Introduces a new tick shard at 2026-05-25T06:13Z capturing the composite-state snapshot and the worktree-add guard results.
+- Cross-links the tick narrative to the relevant `.claude/rules/**` discipline files for traceability.
+
+## Review threads
+
+### Thread 1: docs/hygiene-history/ticks/2026/05/25/0613Z.md:17 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-25T06:20:50Z):
+
+This tick shard begins with YAML frontmatter (`--- ... ---`). The tick-shard schema tooling expects the first non-empty line to be the 6-column pipe-row header (see `docs/hygiene-history/ticks/README.md` and `tools/hygiene/check-tick-history-shard-schema.ts`), so this file would currently fail that validator if/when it’s wired into CI or pre-push checks. Consider switching to the documented “hybrid” format: pipe-row first line, then the H1 body, and (if desired) move this metadata into a fenced ```yaml block inside the body instead of file-head frontmatter.

docs/research/shadow-lesson-log-20260522-stale-locks.md

@@ -0,0 +1,27 @@
+# Shadow Lesson Log - 2026-05-22: Stale Git Locks
+
+## Event
+
+During a routine antigravity check, Lior detected a stale git index lock and an orphan agent lockfile in the `zeta-lior-decompose-4044` worktree. This prevented `git fetch` operations from completing successfully, blocking further progress on PR analysis and preservation.
+
+## Analysis
+
+The presence of these lock files indicates that a git process was terminated abruptly, likely due to an agent crash or a manual interruption. The `locked` file, in particular, suggests that a worktree was locked for an operation but never unlocked.
+
+This event highlights a vulnerability in our autonomous system. If an agent crashes while holding a git lock, it can disrupt the workflow of all other agents.
+
+## Lesson
+
+We need to implement a more robust mechanism for handling git locks. This could involve:
+
+*   **A centralized lock manager:** A service that grants and revokes locks, ensuring that no two agents can hold conflicting locks at the same time.
+*   **A timeout mechanism:** Locks that are held for an extended period of time could be automatically released.
+*   **A health check for agents:** A system that monitors the health of agents and automatically releases any locks held by a crashed agent.
+
+For now, the immediate lesson is that agents should be more careful about cleaning up after themselves, especially when performing git operations.
+
+## Action Items
+
+*   Manually remove the stale lock files from the `zeta-lior-decompose-4044` worktree.
+*   Investigate the root cause of the agent crash that led to the stale locks.
+*   Begin research and design for a more robust git lock management system.