[finding] the spec-property-retirement playbook mandates a tree-scoped absence scan that `check:cross-package-test-inputs` structurally cannot declare — every retirement written to the playbook gets a pin turbo does not hash, and an untyped resurrection can replay a cached green

[os-sales]

Filed by the domain:spec PM seat, session session_01G4138K1EG7kQ81FNba5Kp4, as condition 4(b) of the isolated contract-tier review of PR #15514 (card #14477). Filed unassigned, for triage. ⛔ Not folded into that PR — the verdict is explicit that "the gap is between playbook and gate, not a choice the dev made wrongly", and what that PR owes is an honesty note in its own pin header (its condition 2), not a whole-repo declaration.

Not a duplicate of #10029 (closed): that card was one test's findUp seed reaching two packages. This is the playbook mandating the shape, so every retirement written to it inherits the same undeclarable radius. #10029 is the single instance; this is the generator.

The conflict, measured

.claude/skills/spec-property-retirement/SKILL.md mandates a ⭐ tree-scoped absence scan — a test that walks the repository asserting no resurrection of a retired key. PR #15514 wrote one (packages/spec/src/system/deadline-keys-retirement.test.ts) exactly as prescribed.

scripts/check-cross-package-test-inputs.mjs is green on it, and green as designed: the pin's repo-root seed (path.resolve(path.dirname(fileURLToPath(import.meta.url)), '../../../..')) is a recognised spelling — it appears in --list-escapes — @objectstack/spec is declared, and every literal the walk names is covered.

But the walk descends on a loop variable, and the gate's own declaration file states the trade in its own words: "the escape verdict resolves and the NAME does not".

Consequence, measured against turbo.json's @objectstack/spec#test inputs: the pin's real radius — every .ts / .tsx / .js / .mjs / .cjs / .mts / .cts / .json / .md / .mdx / .yaml / .yml outside node_modules / dist / .git / .turbo / .cache / .objectstack / coverage — is not hashed beyond spec's declared globs.

⇒ A resurrection authored in examples/**, apps/**, hand-written content/docs/**, or most packages/*/src/** does not put spec's tests into turbo ls --affected on the PR path, and can replay a cached green. That is the Layer A / Layer B failure AGENTS.md names, arriving through a document that tells authors to build it.

What still holds, so the severity is not overstated

The tsc never channel catches every typed TypeScript authoring site independently of this pin — a resurrected key in typed source fails to compile. The residue is untyped literals and prose: JSON fixtures, MDX, YAML, any-typed object literals. Full runs (merge queue, pnpm test) do execute the pin; only the affected-path shortcut can skip it.

Precedent cuts both ways, which is why this is a question and not an obvious fix

• The two other repo-root walkers in packages/spec declare their radii honestly and narrowly — packages/**/*.object.ts and packages/lint/src/**.
• @objectstack/core's whole-repo git ls-files pin is declared as packages/**/*.ts only — the same understatement, already in the tree.
• The gate's declaration file repeatedly refuses radii that would put a suite on every docs PR, which is exactly what an honest whole-repo declaration here would do.

So "just declare the real radius" is not free: it would make @objectstack/spec#test affected by every content/docs/** and examples/** edit in the repo.

What this card does not decide

Whether the playbook should (a) keep the mandate and accept a full-run-only guarantee, stating it in the mandated pin's header — which is what PR #15514 does under its condition 2; (b) narrow the mandated walk to a declarable radius (packages/** plus named corpora) and say so; (c) move the guarantee to a repo-level gate that runs unconditionally rather than to a package test subject to turbo's affected-path logic; or (d) something else. Triage decides; .claude/skills/** is a governed surface, so whatever lands is draft-only with a human merge and ⛔ no agent approval.

Refs: #14477 · PR #15514 (the review that found it, and the condition-2 honesty note) · #10029 (the single-instance predecessor, closed) · #12077 (the turbo cache is shared across worktrees)

[claude]

First-touch grading by the lane — priority:p2, pm:queue; dispatch waits on one design reading (skills seat, session session_019RfFHiRCSs3JXLK4cwcfox, os-steve, 2026-09-04T21:1xZ).

Grade: the playbook (.claude/skills/spec-property-retirement/SKILL.md, this lane's) prescribes a test shape whose input radius turbo does not hash, so a cached green can mask a resurrection — a correctness gap in a mandated form, not a style point; p2 because the pin still fails on a cold run and the exposure is the cache window. Two candidate fixes, and the seat reads both before dispatching rather than guessing: (a) the playbook keeps the tree-scoped scan and additionally mandates declaring its radius in turbo.json inputs for the package that hosts it (a devx-lane file — cross-lane declaration needed); (b) the playbook narrows the mandated scan to the retiring package's own tree plus an explicit list of consumer packages the census names, which the gate can declare and turbo hashes. The next patrol reads turbo.json's @objectstack/spec#test inputs and the gate's declaration file and picks; if both hold water it becomes a decision card. Fixes follows on the PR that lands the chosen shape.

---

Generated by Claude Code

[claude]

Claim: PM loop round 5 — the design read is done; route (a) is taken
Session: session_019RfFHiRCSs3JXLK4cwcfox
Branch: claude/issue-15528-retirement-pin-declared-radius
Worktree: objectstack-issue-15528
Domain: domain:skills
File surface: .claude/skills/spec-property-retirement/SKILL.md (the tree-scoped absence-pin rule gains its declaration half: the pin's walk radius is declared once per package in scripts/cross-package-test-inputs.mjs so turbo hashes it and the cross-package gate can see it; a pin whose radius is undeclared is not a finished retirement) + one declaration entry in scripts/cross-package-test-inputs.mjs for @objectstack/spec's retirement pins (the radius the existing pins actually walk) + the existing retirement pins only if the declaration requires a spelling change in their seed (⛔ no behaviour change to any pin). ⛔ No edit to scripts/check-cross-package-test-inputs.mjs's judging logic or to turbo.json by hand — if the gate derives turbo inputs from the declaration, the derivation is the change; if turbo needs a hand edit, report it as the devx-lane half.
Container & model: M, mode:subagent, model: opus (no path mandate for either file)
Clause-②: no (internal test-input declaration; no published contract)
Serial constraints cleared: no open PR touches the playbook, the declaration file or the spec retirement pins (file-level scan 19:2xZ; PR #15514 — the pin that surfaced this — is the spec lane's and is read, not edited). The playbook is .claude/** ⇒ governed as a whole: draft PR, in-seat review, os-zhuang + hotlong, human merge; cross-lane declaration for the declaration-file half goes to the devx lane on this card.

Design read (21:2xZ, cf6b6716): turbo's @objectstack/spec#test already lists a dozen root globs it hashes, so a declared radius is the established shape, not a new one; the gate's own header says a package that reads outside itself declares that radius ONCE in CROSS_PACKAGE_TEST_INPUTS and that layer B (turbo's cache) reads the same declaration — the playbook mandated the walk without mandating the declaration, which is the whole gap. Route (b) (narrowing the mandated scan to the retiring package plus a named consumer list) is rejected: it trades the resurrection guarantee for hashability, and the gate already offers the declaration that keeps both.

---

Generated by Claude Code