Uh oh!
There was an error while loading. Please reload this page.
Anchor recorded replays to surviving commits, and content over positions - #14045
Merged
Conversation
…content over positions The record-discipline block asks for reproductions on cards and rulings but says nothing about what those records are pinned TO, and both pins expire silently. A repro block stated at its own PR head goes unreplayable the moment the branch is squash-merged and deleted: measured, one card's own block had two of its three shas unresolvable, both PR-branch commits, while the surviving one was the main-side diff base. The same shape reaches positions — one triage round hit three dead line-number citations, every one relocated only via a symptom string. The block reads replayable in both cases, and there is no signal at write time. One bullet, two legs: state a replay against a commit that survives (the main merge commit, or base plus PR number) and never a PR head, saying so and recording the inputs themselves — the diff, or the changed hunks — where the PR head genuinely is the subject; and anchor content rather than positions, since line numbers drift as files grow. No gate: scanning card bodies for sha liveness would false-positive on every unmerged PR, which is the card's own restraint and triage's concurrence. Claude-Session: https://claude.ai/code/session_01Msg17tAHJ3jVTYFgHydCm2 Co-authored-by: Claude <noreply@anthropic.com>
This was referenced Sep 1, 2026
os-zhuang
approved these changes
Sep 1, 2026
os-zhuang
marked this pull request as ready for review
September 1, 2026 06:32
Uh oh!
There was an error while loading. Please reload this page.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes#13739
One bullet added to the record-discipline block of
.claude/skills/pm-dispatch/references/dispatch-runbook.md— the section thatgoverns how cards and rulings are written down. That section asks for
reproductions, but says nothing about what a record is pinned TO, and both of
the usual pins expire silently.
The two failure shapes, both measured
A replay stated at its own PR head. The branch is squash-merged and
deleted, the objects go unreachable, and the command block still reads
replayable. On the card behind this PR, two of the three shas in its subject's
repro block were unresolvable — both PR-branch commits — while the one that
survived was the main-side diff base.
A citation stated as a line number. Files grow and the number drifts. One
triage round hit three dead line-number citations, and every one of them was
relocated only by searching for a symptom string.
Same defect in both: a record that reads checkable and is not. A number nobody
can re-derive is a number nobody can check.
The rule
State a replay against a commit that survives — the
mainmerge commit, orbase plus the PR number — never a PR head. Where the PR head genuinely is the
subject, say so and record the inputs beside it (the diff, or the changed
hunks) so the run can be rebuilt without the object. And anchor content, not
positions: symptom strings or distinctive identifiers rather than line numbers.
No gate, deliberately
Scanning card bodies for sha liveness would false-positive on every unmerged
PR, where a PR-head sha is alive and correct. That restraint is the card's own
and triage concurred with it, so this PR adds no script and no check.
Budget and verification
Line budget on the runbook: 271 → 276 lines, ceiling 278 (headroom 7 → 2).
The five added lines were wrapped by the ratchet's own
wrapLine, so each is acanonical break: widths 118 / 116 / 119 / 119 / 97 bytes against the 120-byte
cap, and no table row is introduced (that file's widest-table-row pin is 0).
No issue numbers appear in the operative text, per the id lint.
Gate union re-derived in the worktree with
node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commandsand run after the final commit, at HEAD
f952cf8fd. Every exit code wascaptured by redirect-then-capture, never after a pipe:
Ratchet verdict for the edited file, verbatim:
check-skill-line-ratchet: .claude/skills/pm-dispatch/references/dispatch-runbook.md is 276 lines (ceiling 278; headroom 2).check:doc-formula-expressionsfirst refused with exit 3 — PREREQUISITE NOTMET,
@objectstack/formulathen@objectstack/lintunbuilt in a freshworktree. Both were built and the gate re-run to the exit 0 above; the refusals
measured nothing and are recorded here only so the sequence is reconstructible.
Changeset: none. The diff is
.claude/**-only and publishes from nopackage, so it takes
skip-changesetper the workflow's own prescription.Draft only — governed surface, human merge.
Generated by Claude Code
Generated by Claude Code