fix(hygiene): regen docs/BACKLOG.md index — clear generated-index drift#3678
Merged
AceHack merged 1 commit intoMay 16, 2026
Merged
Conversation
…ft non-required-check Mechanical regen via `BACKLOG_WRITE_FORCE=1 bun tools/backlog/generate-index.ts`. Source: per-row files in `docs/backlog/P*/B-*.md`. Diff is +16/-1; new backlog rows added since last index regen (recent decomposition + QG-isomorphism rows B-0543–B-0548 etc.) are now reflected. `bun tools/backlog/generate-index.ts --check` now exit 0 → the `check docs/BACKLOG.md generated-index drift` non-required CI check will flip fail → pass on subsequent PRs. Second of three drift cleanups deferred from tick 0111Z (after PR #3666 cleared the 22 §33 xrefs). Two more remain: `lint (backlog ID uniqueness)` (B-0498 collision per B-0545) and `lint (tsc tools)` (pending investigation). Co-Authored-By: Claude <noreply@anthropic.com>
AceHack
deleted the
fix/backlog-md-generated-index-regen-otto-cli-2026-05-16
branch
There was a problem hiding this comment.
Pull request overview
Mechanical regeneration of docs/BACKLOG.md from per-row backlog files to clear generated-index drift.
Changes:
- Adds recently filed P1/P2/P3 backlog rows to the generated index.
- Updates B-0500 from open to closed in the index.
- Leaves the known B-0498 duplicate-ID drift visible in the regenerated output.
| - [ ] **[B-0496](backlog/P1/B-0496-hamiltonian-viz-slice-2-live-github-api-2026-05-14.md)** Hamiltonian viz — slice-2: live GitHub API commit fetch → trajectory | ||
| - [ ] **[B-0497](backlog/P1/B-0497-b0440-slice-6-standing-by-detector-launchd-registration-2026-05-14.md)** B-0440 slice 6 — standing-by-detector launchd plist + AUTONOMOUS-LOOP.md wiring update | ||
| - [ ] **[B-0500](backlog/P1/B-0500-b0441-slice-3-queue-state-guard-poll-once-wiring-2026-05-14.md)** B-0441 slice 3 — wire isAgentQueueEmpty guard into pollOnce | ||
| - [ ] **[B-0498](backlog/P1/B-0498-riven-cursor-terminal-background-loop-ide-native-autonomous-gate-2026-05-15.md)** Riven Cursor Terminal background loop — IDE-native autonomous gate with manager contract |
AceHack
added a commit
that referenced
this pull request
May 16, 2026
…nd of 3 drift items (#3679) Drift queue from 0111Z: 22 §33 xrefs (#3666 merged), BACKLOG.md regen (#3678 this tick, armed), backlog ID uniqueness + tsc tools (open). Borrow-pattern used twice this tick on /private/tmp/zeta-tick-2210z while Lior remains active. Holding-discipline counter resets per "actually picking real decomposition work" clause — concrete code substrate landed this tick. Co-authored-by: Claude <noreply@anthropic.com>
This was referenced May 16, 2026
AceHack
added a commit
that referenced
this pull request
May 16, 2026
…nt (tsc tools) (#3684) `publishHeartbeat` accepted `"alive" | "shutdown"`, but the bus's `HeartbeatPayload.status` is `"alive" | "idle" | "working"` and consumers (`tools/bus/bus.ts` line 331) filter to that union. `"shutdown"` would silently drop at the bus consumer even if the type allowed it. Surgical fix: - Import `HeartbeatPayload` type from `tools/bus/types.ts` - Bind the local `status` param to `HeartbeatPayload["status"]` (single source of truth; future-proof if the bus union widens) - Change the SIGINT-graceful-shutdown call site to publish `("alive", "shutdown:terminal-closed")` — the shutdown semantic is preserved in the `note` field where it actually reaches consumers Local verify: `bun --bun tsc --noEmit -p tsconfig.json` → exit 0. Third of three drift cleanups from the 0111Z queue (after 22 §33 xrefs via PR #3666 and BACKLOG.md regen via PR #3678). One drift remains: `lint (backlog ID uniqueness)` — B-0498 collision per B-0545. Co-authored-by: Claude <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
May 16, 2026
…of 3 drift items) (#3685) Riven cursor-terminal heartbeat status type tightened to bus union. Single tsc error since PR #3603 cleared via surgical 3-line fix (preserve shutdown semantic in note field; no widening of HeartbeatPayload union). Drift queue from 0111Z: 22 §33 xrefs (#3666 merged), BACKLOG.md regen (#3678 merged), tsc tools (#3684 armed this tick). Remaining: backlog ID uniqueness (B-0498 collision, needs B-0545 renumber coordination). Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mechanical regen via `BACKLOG_WRITE_FORCE=1 bun tools/backlog/generate-index.ts`.
What
bun tools/backlog/generate-index.ts --checknow exit 0 (was exit 2)Why
Second of three drift cleanups deferred from tick 0111Z — the
check docs/BACKLOG.md generated-index driftnon-required CI check has been firing FAILURE on every PR this session.After this PR merges, the check will flip fail → pass on subsequent PRs.
Remaining drift (next-tick candidates)
lint (backlog ID uniqueness)— B-0498 collision per B-0545lint (tsc tools)— pending investigationProvenance
/private/tmp/zeta-tick-2210z(Lior still active inps -A— new worktree-add unsafe per broken-commit canary rule)Co-Authored-By: Claude noreply@anthropic.com