Repository navigation
Commit ee26ec6
docs(skills): the retirement playbook prescribes a
The `spec-property-retirement` Changeset checklist item told the agent to grade
`@objectstack/spec` a `major` bump. The per-PR `Check Changeset` job runs
`scripts/check-changeset-no-major.mjs`, which refuses exactly that while the
launch window stands — so an agent executing the checklist verbatim reddened its
own PR and then had to decide, mid-retirement, whether the playbook or the gate
was authoritative.
Measured in this worktree, both legs on a throwaway changeset:
"@objectstack/spec": major -> exit 1, "This PR introduces changeset(s) that
declare a `major` bump."
"@objectstack/spec": minor -> exit 0, "This diff introduces no `major` bump."
The item now says `minor`, names the gate and the job so the next reader sees
why, and states that the breaking semantics ride the BREAKING banner instead of
the bump level — the same split `.github/workflows/pr-automation.yml` already
states under "WHICH LEVEL". The `AGENTS.md:breaking` pointer, the FROM -> TO
mapping requirement, the `CHANGELOG.md` rationale, the template pointer and the
ADR-0087 disposition marker all survive; the item is repacked in place at 6
lines so the file stays at its ratchet ceiling of 337, every line under 120
bytes.
Claude-Session: https://claude.ai/code/session_017ETYWqMQD4qMtZzAGovWNi
Co-authored-by: Claude <noreply@anthropic.com>minor changeset, not the major a live gate refuses1 parent 23f1de0 commit ee26ec6
1 file changed
Lines changed: 6 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
288 | 288 | | |
289 | 289 | | |
290 | 290 | | |
291 | | - | |
292 | | - | |
293 | | - | |
294 | | - | |
295 | | - | |
296 | | - | |
| 291 | + | |
| 292 | + | |
| 293 | + | |
| 294 | + | |
| 295 | + | |
| 296 | + | |
297 | 297 | | |
298 | 298 | | |
299 | 299 | | |
| |||
0 commit comments