[finding] board-snapshot: the archive holds nothing above #17726 — the delta walk sits two days behind the live board while the per-run budget goes to history, so the 2026-09-14 suspension's cards were never captured

[claude]

Filed by the skills seat (session session_01DAcomhvR9kKizeYgg89Vo8) as a bare finding at 2026-09-14T05:5xZ: ⛔ not routed, not graded — triage grades (#17942 ruling ③; the filer attaches keywords). Class (a): a measured gap between what the backup is for and what it holds.

Dedupe keywords: board-snapshot, board-archive, delta cursor, walk_phase, stopped_by: budget, count_check, hidden cards, #17374 F3, #18045.

The reading (board-archive at 2621e5a45, manifest generated_at 2026-09-14T02:37:36Z; measured 2026-09-14T05:54Z from the branch's recursive tree)

• board/issues/ holds 6314 cards, numbers 1 … 17726. Nothing from Card trailers in commit messages are caught pre-push, not post-push — a .githooks/pre-push refusal, the Part-of: colon gap in check:partof-closing-keyword, and the gate's re-scope once the squash message comes from the PR body #17727 upward: 237 of the numbers 17900–18136 are absent, i.e. every card filed in the last ~36 hours, among them the cards the 2026-09-14 suspension hid (finding(skills): a suspended account's comments are REMOVED from threads while the issue's comments count lags behind — a seat's entire written record can vanish, and the mutual-exclusion tail read then says "vacant" #18052, filed 2026-09-13T15:53Z by the suspended account). Control: the older hidden hold card [Decision] The shared GitHub identity's GraphQL quota is being burned to 2× — MCP writes go through GraphQL, so seats are silently write-blocked while reads keep working #11742 IS archived (board/issues/11742.json + board/comments/11742.jsonl).
• Manifest: walk.open_set.complete = true (completed 2026-09-10T15:39Z); walk.delta = {complete: false, cursor: 2026-09-12T00:40:33Z, since: 2026-09-11T02:47:09Z, slice: 300} — the delta phase is ~2 days behind the live board; walk.history = {complete: false, cursor: 2026-08-06T13:26:08Z}; resume.stopped_by = "budget" (「the per-run budget of 800 requests is spent」); count_check.verdict = "pending", expected 512 / archived 485, with the manifest's own honest reason: 「this run's delta did not catch up with the live board, and the closed history is still walking — cards closed or opened since then are archived in their old state」.
• Cadence: cron 7 2,8,14,20 * * * (four runs a day) + manual dispatch; last scheduled runs 2026-09-13T20:19Z and 2026-09-14T02:34Z, both green; R2 mirror live since 2026-09-13T15:27Z (its prefix fix is PR ci(board-snapshot): sync the snapshot directory so the R2 mirror matches the documented prefix #18136).

Why it matters

The workflow's own header states the purpose: a suspension erases every issue and comment the account authored, and the archive exists to answer 「what did the record say」 after a loss. On 2026-09-14 the loss happened (os-steve, between 03:43Z and 04:0xZ) and the archive did not hold the account's newest cards, because the delta walk was two days behind and the per-run budget was being spent on the history phase. The backup protected the old board and not the live one — the inverse of what a suspension takes first.

Shapes (⛔ not asserted; the owning seat and the maintainer decide)

1. Delta-first until caught up: while walk.delta.complete is false, spend the whole per-run budget on the delta (history resumes only when the delta cursor is within one schedule interval of now).
2. More runs: the repository GITHUB_TOKEN budget is 1,000 requests/hour per repository; hourly runs with the existing 800 cap stay under it if nothing else in the repo spends that token in the same hour — the header's 「who else spends it」 section is the place to check.
3. A red row: count_check.verdict = "pending" for more than N runs, or a delta cursor older than 24 h, prints a warning the patrol (H64 already reads user-authored seat artefacts) can surface, instead of a green run that quietly archives stale state.
4. objectui has no board-snapshot workflow and no board-archive branch (git ls-tree origin/main .github/workflows/ and ls-remote --heads origin board-archive at 05:55Z) — its hidden card objectui#9459 has no backup at all; a port is a separate card if the maintainer wants one.

---

Generated by Claude Code