docs(skills): the absence pin a deleting PR writes is tree-scoped

[claude]

Part of #14878 — this is the governed half of that card's ruling D, travelling separately from the code by the ruling's own permission.

⛔ Draft on purpose, and it stays draft. .claude/skills/** is a governed surface: the maintainer merges it by hand, it is never armed, and it is never flipped ready by a seat. The code half — the two tree-scoped pins, the two live stale mentions, the reworded history line — is PR #15085. Bundling one sentence with it would have dragged the whole change onto the human-merge path.

What the ruling asked for, verbatim

The retirement playbook's deleting-PR checklist gains one sentence: the absence pin a deleting PR writes is tree-scoped.

What is here

Four lines added to the Pin 测试 item of the deleting-PR checklist in .claude/skills/spec-property-retirement/SKILL.md, in the file's own language and voice. They say: the absence pin is tree-scoped and never file-scoped; a file-scoped one only sees the file its author thought of, and the references that rot are the ones the author did not know about (measured — five surviving references across three packages, two cards, two of them written after the deletion by a later PR); exclude **/CHANGELOG.md, .changeset/ and the pin itself with the reason written beside it, ⛔ never an allowlist file; and ⛔ an assertion of absence is not a stale mention — "repairing" it deletes the guard.

That last clause is the one this card exists for. The pin the playbook is teaching contains expect(plugin!.text).not.toContain(...), and a naive fixer clearing a stale-mention report would delete exactly that line.

Ratchet — paid, not raised

✓ check-skill-line-ratchet: .claude/skills/spec-property-retirement/SKILL.md
    is 337 lines (ceiling 337; headroom 0)
pnpm check:pm-skill-ratchet   EXIT=0

333 → 337, inside the headroom that already existed. ⛔ No ceiling raised (that needs a maintainer ruling), ⛔ nothing re-wrapped to buy room — the first draft was six lines and was rewritten shorter rather than paid for out of neighbouring text.

This file is .claude/skills/** (internal agent tooling), not the published skills/ surface, so the published-skill net-growth budget does not apply to it; the line ratchet above is what governs it and it is green.

Verification, at 025072000

Gate family from node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack — 18 commands, exit codes captured before any pipe. 16 green, including check:pm-skill-ratchet, check:pm-governed-merges, check:skill-frame-sync, check:doc-authoring, check:agent-test-spelling, check:nul-bytes, check:required-contexts and both cross-package-inputs limbs.

Two came back exit 3 = NOT MEASURED (never a pass, never a red): check-test-completeness (wants a saved turbo run test log) and check:doc-formula-expressions (PREREQUISITE NOT MET in an unbuilt worktree).

@objectstack/spec declares this exact file as a cross-package test input, so its reader was run rather than assumed:

pnpm --filter @objectstack/spec exec vitest run src/shared/retired-key-migrate-sentence.test.ts
  Test Files  1 passed (1)      Tests  14 passed (14)

🤖 Generated with Claude Code

Generated by Claude Code

---

Generated by Claude Code