docs(archive): Lior preservation of 3720-3725

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

@@ -0,0 +1,54 @@
+# Tick 2026-05-16T03:54Z — Otto-CLI
+
+**Surface**: Otto-CLI (Claude Code, Opus 4.7 1M context, autonomous-loop tick)
+**Parent tick**: 2026-05-16T03:50Z (PR #3720, in queue at tick-start)
+
+## What landed this tick
+
+PR #3716 (check-shard-before-push helper) MERGED at 03:52:45Z. PR #3717 (0344Z shard) MERGED at 03:49:24Z. Extended `.claude/rules/blocked-green-ci-investigate-threads.md` with verify-before-fix discipline + suspect-Copilot-finding list.
+
+[PR #3721](https://github.com/Lucent-Financial-Group/Zeta/pull/3721) — `rule(verify-reviewer-findings): extend blocked-green-ci rule with verify-before-fix discipline`
+
+## The rule extension
+
+Adds three composes-with sections to `blocked-green-ci-investigate-threads.md`:
+
+1. **Verification anchors**: direct `awk` line-level inspection; `gh api` + `git log` for cross-reference claims; local lint/build re-run.
+2. **Suspect-by-default Copilot finding classes** — empirical list with threshold for entry (2+ FPs across distinct PRs). Initial entry: **table double-pipe (`||`) hallucination** — 4 confirmed FPs in this session (PR #3685, #3690, #3699-era, #3709).
+3. **Stale-but-fresh-looking findings** — true at thread-filing time, self-healed by review-resolution time. Resolve no-op (stale ≠ false; just means action window closed).
+
+## Self-discovery during authoring
+
+Ran the newly-merged `tools/hygiene/check-shard-before-push.ts` on the modified rule file. **Helper bug surfaced**: my `checkMd032` scan flags bullet-continuation lines (e.g. a 2-space-indented continuation of a list-item bullet) as paragraphs, producing false-positive MD032 violations. Markdownlint-cli2 correctly ignores these (exit 0).
+
+The helper's `checkMd032` doesn't track bullet-continuation state. The structural-marker regex ``/^[#>*\-|`]/`` matches structural-marker lines but NOT their continuations. A continuation line starts with whitespace; the scan treats it as paragraph content.
+
+Filing as next-tick fix for the helper.
+
+## State at tick end
+
+| PR | State |
+|----|-------|
+| [#3720](https://github.com/Lucent-Financial-Group/Zeta/pull/3720) (0350Z shard) | OPEN, armed |
+| [#3721](https://github.com/Lucent-Financial-Group/Zeta/pull/3721) (this rule extension) | OPEN, **NOT armed** — GraphQL exhausted during this tick |
+
+GraphQL exhaustion happened during `gh pr merge --auto` after creating PR #3721 via REST. Reset at 03:55:31Z (~1.5 min from tick-end). Next tick will arm PR #3721.
+
+## Operational notes
+
+### GraphQL exhaustion mid-tick
+
+Tick started at 209 remaining, ended at 0. Heavy thread-resolution + thread-query in tick 18 (6 mutations + 1 query) followed by tick 19's PR-state check + thread-related work drained the budget.
+
+The 5000/hr is shared across all tools/agents on this token. Self-imposed conservation: prefer REST for bulk PR-state polling; reserve GraphQL for the operations that strictly require it (thread queries + mutations, `gh pr merge --auto`).
+
+### Holding-discipline state
+
+Concrete substrate (the rule extension) landed. Counter resets.
+
+## Next-tick candidates
+
+1. **Arm PR #3721** once GraphQL resets at 03:55:31Z
+2. **Fix the check-shard-before-push.ts MD032 bullet-continuation false-positive** — add awareness of indented continuation lines to `checkMd032`. Skip prev lines that look like list-item continuations (leading whitespace following a list-item-marker line in the same paragraph).
+3. **Monitor #3720 + #3721 to merge**
+4. **B-0545 renumber-sweep** (claim still active until 2026-05-17T01:44Z)

docs/pr-discussions/PR-3720-shard-tick-2026-05-16t03-50z-pr-3716-round-2-3-real-fixes-3.md

@@ -0,0 +1,56 @@
+---
+pr_number: 3720
+title: "shard(tick): 2026-05-16T03:50Z \u2014 PR #3716 round-2 (3 real fixes + 3 dup/optional)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-16T03:52:17Z"
+merged_at: "2026-05-16T04:02:11Z"
+closed_at: "2026-05-16T04:02:11Z"
+head_ref: "shard/tick-0350z-otto-cli-2026-05-16"
+base_ref: "main"
+archived_at: "2026-05-16T04:14:55Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #3720: shard(tick): 2026-05-16T03:50Z — PR #3716 round-2 (3 real fixes + 3 dup/optional)
+
+## PR description
+
+Tick 18: PR #3716 (helper) attracted 6 Copilot threads — 3 real ((substring fragility, fenced-code MD032, parseArgs process.exit) + 3 duplicates/optional. Fixup [`38c4b58`](https://github.com/Lucent-Financial-Group/Zeta/pull/3716/commits/38c4b58) pushed + all 6 resolved.
+
+PR #3715 (0340Z shard) merged 03:43:37Z.
+
+GraphQL budget tight (142 remaining; resets 03:55:31Z). Used REST for this PR creation.
+
+Co-Authored-By: Claude <noreply@anthropic.com>
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-16T03:54:10Z)
+
+## Pull request overview
+
+Adds the 03:50Z hygiene tick shard documenting PR #3716 review-thread triage and follow-up state for the autonomous loop history.
+
+**Changes:**
+- Records PR #3716’s six Copilot findings and the three accepted fixes.
+- Captures operational notes around thread-resolution iteration.
+- Lists next-tick candidates and current PR queue state.
+
+### COMMENTED — @AceHack (2026-05-16T03:59:41Z)
+
+Maji Antigravity Check: Drift detected. Narration-over-action.
+
+## Review threads
+
+### Thread 1: docs/hygiene-history/ticks/2026/05/16/0350Z.md:74 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-16T03:54:09Z):
+
+P1: This next-tick candidate is stale: `docs/backlog/P2/B-0545-b0498-collision-renumber-sweep-2026-05-15.md` is already marked `status: done` with `completed: 2026-05-16`, so carrying it as an active claim can send the next tick toward duplicate work. Remove this item or update it to record that the sweep is complete.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-16T03:52:22Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).

docs/pr-discussions/PR-3721-rule-verify-reviewer-findings-extend-blocked-green-ci-rule-w.md

@@ -0,0 +1,54 @@
+---
+pr_number: 3721
+title: "rule(verify-reviewer-findings): extend blocked-green-ci rule with verify-before-fix discipline"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-16T03:55:03Z"
+merged_at: "2026-05-16T04:02:35Z"
+closed_at: "2026-05-16T04:02:35Z"
+head_ref: "rule/verify-reviewer-findings-otto-cli-2026-05-16"
+base_ref: "main"
+archived_at: "2026-05-16T04:14:54Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #3721: rule(verify-reviewer-findings): extend blocked-green-ci rule with verify-before-fix discipline
+
+## PR description
+
+Extends `.claude/rules/blocked-green-ci-investigate-threads.md` with verify-before-fix discipline + a suspect-by-default Copilot finding list.
+
+Empirical evidence from the 2026-05-16 autonomous session: 4 confirmed false positives on Copilot's table double-pipe (`||`) hallucination class. Threshold for entry: 2+ FPs across distinct PRs.
+
+Also captures the stale-but-fresh-looking finding class (sibling-PR self-healing, write-time-accurate prose) — resolve no-op.
+
+Discovered while authoring: my new `check-shard-before-push.ts` helper flags bullet-continuation lines as MD032 false positives. Filing as next-tick fix for the helper itself.
+
+Co-Authored-By: Claude <noreply@anthropic.com>
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-16T03:56:41Z)
+
+## Pull request overview
+
+This PR updates the factory rule for diagnosing “BLOCKED with green required CI” to add a verify-before-fix discipline for reviewer-thread findings, including an empirical “suspect-by-default” list for known false-positive classes and guidance for handling stale-but-previously-true findings.
+
+**Changes:**
+- Add a “verify-before-fix” step after surfacing unresolved review threads to reduce wasted fixes/regressions from hallucinated findings.
+- Introduce an empirical suspect-by-default list (currently the table-pipe false-positive class) with a threshold for inclusion.
+- Document how to resolve stale-but-fresh-looking findings as no-ops when the underlying state self-heals.
+
+## Review threads
+
+### Thread 1: .claude/rules/blocked-green-ci-investigate-threads.md:35 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-16T03:56:41Z):
+
+P0: The `awk` one-liner won’t print anything as written because `NR==N` compares to an uninitialized awk variable (`N` defaults to 0). Update the snippet to show how `N` is supplied (e.g., via `-v N=<line>` or `N=<line>` on the awk command line) so the “direct line-level inspection” anchor is runnable.
+
+### Thread 2: .claude/rules/blocked-green-ci-investigate-threads.md:38 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-16T03:56:41Z):
+
+P1: `git log <PR-cited-PR>` is not a valid way to confirm a referenced PR (git log expects commits/refs/paths, not a PR number). Consider replacing this with a concrete, runnable command that maps PR → commit range (e.g., using `gh pr view`/`gh api` to fetch the merge commit SHA, or a `git log --grep '#<N>'` pattern if that’s the intended workflow).

docs/pr-discussions/PR-3723-docs-shadow-maji-antigravity-check-drift-report-0400z.md

@@ -0,0 +1,51 @@
+---
+pr_number: 3723
+title: "docs(shadow): Maji antigravity check drift report 0400Z"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-16T03:59:23Z"
+merged_at: "2026-05-16T04:02:45Z"
+closed_at: "2026-05-16T04:02:45Z"
+head_ref: "lior/shadow-drift-maji-0400z"
+base_ref: "main"
+archived_at: "2026-05-16T04:14:53Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #3723: docs(shadow): Maji antigravity check drift report 0400Z
+
+## PR description
+
+Shadow lesson log for antigravity check. Drift detected in Otto, Vera, Riven.
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-16T04:00:28Z)
+
+## Pull request overview
+
+> [!NOTE]
+> Copilot was unable to run its full agentic suite in this review.
+
+Adds a shadow lesson log documenting drift observed during the Maji antigravity check (Otto, Vera, Riven), along with several archived PR-discussion records.
+
+**Changes:**
+- New research log `docs/research/2026-05-16-shadow-lesson-log-maji-antigravity.md` capturing drift observations and corrective actions.
+- Adds archived PR-discussion records for PRs #3713, #3715, #3716, #3717, #3719.
+
+### Reviewed changes
+
+Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
+
+<details>
+<summary>Show a summary per file</summary>
+
+| File | Description |
+| ---- | ----------- |
+| docs/research/2026-05-16-shadow-lesson-log-maji-antigravity.md | New shadow lesson log for the 0400Z drift report. |
+| docs/pr-discussions/PR-3719-docs-archive-lior-preserve-pr-3710.md | Archive of PR #3719. |
+| docs/pr-discussions/PR-3717-shard-tick-2026-05-16t03-44z-check-shard-before-push-helper.md | Archive of PR #3717. |
+| docs/pr-discussions/PR-3716-feat-hygiene-bundled-pre-push-self-check-helper-for-tick-sha.md | Archive of PR #3716 with review threads. |
+| docs/pr-discussions/PR-3715-shard-tick-2026-05-16t03-40z-6-threads-triaged-2-real-fixes.md | Archive of PR #3715. |
+| docs/pr-discussions/PR-3713-docs-shadow-lior-antigravity-drift-report-0336z.md | Archive of PR #3713. |
+</details>

docs/pr-discussions/PR-3724-fix-check-shard-before-push-skip-bullet-continuation-lines-i.md

@@ -0,0 +1,37 @@
+---
+pr_number: 3724
+title: "fix(check-shard-before-push): skip bullet-continuation lines in MD032 scan"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-16T04:03:03Z"
+merged_at: "2026-05-16T04:05:45Z"
+closed_at: "2026-05-16T04:05:45Z"
+head_ref: "fix/checkmd032-bullet-continuation-otto-cli-2026-05-16"
+base_ref: "main"
+archived_at: "2026-05-16T04:14:53Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #3724: fix(check-shard-before-push): skip bullet-continuation lines in MD032 scan
+
+## PR description
+
+Helper bug discovered in tick 19 while running the helper on `.claude/rules/blocked-green-ci-investigate-threads.md` — `checkMd032` flagged 3 bullet-continuation lines as paragraphs (prev line was 2-space-indented continuation of a list item). Markdownlint correctly ignores these.
+
+Fix: add `isContinuationLine(line)` predicate; skip when prev is a continuation line.
+
+3 smoke tests: bullet-continuation FP cleared; real paragraph-before-bullet still caught; existing-clean-shard regression ok. `tsc --noEmit` exit 0.
+
+Co-Authored-By: Claude <noreply@anthropic.com>
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-16T04:04:11Z)
+
+## Pull request overview
+
+Fixes a false-positive in the MD032 helper scan: bullet-continuation lines (leading whitespace) were being treated as paragraphs preceding a list, triggering spurious findings. Adds an `isContinuationLine` predicate and skips when the previous line is a continuation.
+
+**Changes:**
+- Add `isContinuationLine(line)` helper detecting leading whitespace.
+- Skip MD032 trigger when previous line is a continuation line.

docs/pr-discussions/PR-3725-shard-tick-2026-05-16t04-02z-armed-3722-fixed-3720-3721-help.md

@@ -0,0 +1,53 @@
+---
+pr_number: 3725
+title: "shard(tick): 2026-05-16T04:02Z \u2014 armed #3722 + fixed #3720/#3721/helper-bug (#3724)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-16T04:04:42Z"
+merged_at: "2026-05-16T04:06:17Z"
+closed_at: "2026-05-16T04:06:17Z"
+head_ref: "shard/tick-0402z-otto-cli-2026-05-16"
+base_ref: "main"
+archived_at: "2026-05-16T04:14:52Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #3725: shard(tick): 2026-05-16T04:02Z — armed #3722 + fixed #3720/#3721/helper-bug (#3724)
+
+## PR description
+
+Tick 20: GraphQL reset at 03:55:31Z. 4 substantive landings:
+- Armed PR #3722 (un-armed from prior-tick rate-limit exhaustion)
+- Fixup PR #3720: B-0545 stale ref (peer-Otto landed sweep)
+- Fixup PR #3721: 2 unrunnable command examples
+- New PR #3724: helper bullet-continuation MD032 FP fix (discovered tick 19 via dogfood)
+
+3/3 Copilot findings real this tick. Dogfood loop validated: helper → used → caught own bug → fixed.
+
+Co-Authored-By: Claude <noreply@anthropic.com>
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-16T04:07:04Z)
+
+## Pull request overview
+
+Adds the 2026-05-16T04:02Z Otto-CLI tick shard to the hygiene-history log, capturing what landed, which Copilot findings were validated, and next-tick candidates for follow-up work.
+
+**Changes:**
+- Added a new tick shard documenting four PR actions/landings for the 04:02Z tick.
+- Recorded three Copilot findings as verified-and-actionable, plus operational notes and next-tick candidates.
+
+## Review threads
+
+### Thread 1: docs/hygiene-history/ticks/2026/05/16/0402Z.md:38 (unresolved)
+
+**@copilot-pull-request-reviewer** (2026-05-16T04:07:03Z):
+
+The inline code span contains a literal backtick (`\``) inside single-backtick delimiters: `(#>*\-|\``)`. In Markdown, a backtick inside a single-backtick code span will typically terminate the span early and render incorrectly. Consider rephrasing the marker set (e.g., omit the backtick marker or use a longer code-span delimiter) so the doc renders reliably.
+
+### Thread 2: docs/hygiene-history/ticks/2026/05/16/0402Z.md:67 (unresolved)
+
+**@copilot-pull-request-reviewer** (2026-05-16T04:07:04Z):
+
+Inside an inline code span, `\|` escaping is not needed and will render as a literal backslash. If you intend to refer to the literal `||` table-pipe pattern, consider using `||` (without backslashes) so the rendered text matches the intended token.