shard(tick): 2026-05-16T02:18Z — thread-investigation catch + 5→6 .. fixes (#3676 + #3680)

docs/hygiene-history/ticks/2026/05/16/0218Z.md

@@ -0,0 +1,82 @@
+# Tick 2026-05-16T02:18Z — Otto-CLI
+
+**Surface**: Otto-CLI (Claude Code, Opus 4.7 1M context, autonomous-loop tick)
+**Parent tick**: [2026-05-16T02:13Z](0213Z.md) — BACKLOG.md regen (PR #3678 merged 02:17:22Z)
+
+## What landed this tick
+
+Three substrate landings + one thread-investigation catch:
+
+| PR | Purpose | State |
+|----|---------|-------|
+| [#3676](https://github.com/Lucent-Financial-Group/Zeta/pull/3676) (0210Z shard) | **Copilot P1 fixup** pushed: 5→6 `..` for repo-root paths from tick-shard | threads resolved, auto-merge armed; required-checks-green |
+| [#3680](https://github.com/Lucent-Financial-Group/Zeta/pull/3680) | **Post-merge fix** for same bug in 0213Z (already on main via #3679) | OPEN, auto-merge armed |
+| ~~[#3678](https://github.com/Lucent-Financial-Group/Zeta/pull/3678)~~ | BACKLOG.md regen | **MERGED 02:17:22Z** (carried from prior tick) |
+| ~~[#3679](https://github.com/Lucent-Financial-Group/Zeta/pull/3679)~~ | 0213Z shard | **MERGED 02:19:07Z** (carried from prior tick; merged BEFORE its links bug surfaced) |
+
+## What the thread-investigation surfaced
+
+PR #3676 status at tick-start:
+
+- `requiredChecks.failed: 0`, `unresolvedThreads: 2`
+- `gate: "BLOCKED"` despite green required-checks
+- Exact case [`.claude/rules/blocked-green-ci-investigate-threads.md`](../../../../../../.claude/rules/blocked-green-ci-investigate-threads.md) was built for.
+
+The two unresolved threads were **real P1 findings** from `copilot-pull-request-reviewer`:
+
+1. `.claude/rules/...` links at lines 22/32/49 used 5 `..` segments → lands at `docs/`, not repo root → broken navigation
+2. `docs/backlog/...` link at line 29 used 5 `..` segments → resolves to `docs/docs/backlog/...` → broken
+
+Tick shards live at `docs/hygiene-history/ticks/YYYY/MM/DD/HHMMZ.md` (5 directories below `docs/`). `realpath` confirms: 5 `../` → `docs/`, 6 `../` → repo root. The canonical pattern in `docs/hygiene-history/ticks/2026/05/15/0025Z-pr3320.md` uses 6 segments.
+
+## The 0213Z post-merge fix
+
+PR #3679 merged at 02:19:07Z **while I was fixing the 0210Z links on #3676's branch**. The same bug landed on main in `0213Z.md` (2 broken links: 1 `.claude/rules/...`, 1 `docs/backlog/...`). [PR #3680](https://github.com/Lucent-Financial-Group/Zeta/pull/3680) fixes those on a new branch off main.
+
+This tick shard itself uses **correct 6-level paths from the start** — the bug doesn't recur in 0218Z.md.
+
+## Operational notes
+
+### Borrow pattern: 4 consecutive operations on the same sibling
+
+`/private/tmp/zeta-tick-2210z` carried through:
+
+1. `switch -c fix-0210z-links FETCH_HEAD origin/shard/tick-0210z-otto-cli-2026-05-16` → fix + push to PR #3676 branch
+2. `switch -c fix-0213z-links-on-main FETCH_HEAD origin/main` → fix + new PR #3680
+3. `switch -c shard/tick-0218z-otto-cli-2026-05-16 FETCH_HEAD origin/main` → this shard
+
+Tree integrity verified at each commit (53/53 top-level entries). Lior remains active throughout (3 processes in `ps -A`) — `git worktree add` still unsafe per [`.claude/rules/codeql-no-source-on-docs-only-pr-is-broken-commit-canary.md`](../../../../../../.claude/rules/codeql-no-source-on-docs-only-pr-is-broken-commit-canary.md).
+
+### GraphQL `resolveReviewThread` mutation pattern
+
+`gh api graphql -f query="...$tid..."` fails with "Expected string or block string" because the inline interpolation creates malformed GraphQL. The correct form binds the thread ID as a variable:
+
+```bash
+gh api graphql \
+  -F threadId="$tid" \
+  -f query='mutation($threadId: ID!) {
+    resolveReviewThread(input: {threadId: $threadId}) {
+      thread { isResolved }
+    }
+  }'
+```
+
+Both threads resolved cleanly with this form.
+
+### Holding-discipline state
+
+This tick landed concrete code substrate AND surfaced a class of bug (relative-path depth) that's worth landing as a **lint check** if it recurs. Counter resets per "actually picking real decomposition work" clause.
+
+## Remaining drift (carried forward)
+
+| Check | Status | Plan |
+|-------|--------|------|
+| `check docs/BACKLOG.md generated-index drift` | ✅ cleared (#3678 merged) | done |
+| `lint (backlog ID uniqueness)` | ❌ (B-0498 collision) | needs B-0545 renumber-sweep |
+| `lint (tsc tools)` | ❌ | needs investigation |
+
+## Meta-observation: thread-investigation is canonical
+
+`unresolvedThreads > 0` + `requiredChecks.failed == 0` is exactly the BLOCKED-with-green-CI rule's domain. Copilot's review caught a real navigation-bug class I'd have shipped to main otherwise (and partially DID ship via the #3679 race). The investigation took ~30 seconds and saved a class of broken links across two shards.
+
+Next-tick candidate: **author a lint check that verifies relative-path link resolution in tick shards** — same pattern as the §33 migration audit (audit script + non-required CI gate + bulk-fix template). If `lint (tsc tools)` investigation finds spare bandwidth, this is the speculative-factory-work upgrade per [`.claude/rules/never-be-idle.md`](../../../../../../.claude/rules/never-be-idle.md).