spec's declared test-input radius omits `packages/**/*.tsx` while its tree-walking tests read `.tsx` — and the glob that would cover it is forbidden by a dispatch-gates self-test pin

[claude]

CROSS_PACKAGE_TEST_INPUTS['@objectstack/spec'] declares the packages/ radius per extension:
*.ts, *.mts, *.cts, *.js, *.mjs, *.cjs, *.json, *.md, *.mdx, *.yaml, *.yml.
packages/**/*.tsx is not among them, and a *.ts glob does not match a .tsx path.

Two tests in that package walk the whole packages/ tree and do read .tsx:

• src/system/compliance-families-retirement.test.ts (the spec: the rest of the incident-response, training and change-management families — every remaining key and all fifteen defs — has zero readers; whole-def enforce-or-remove is the open question left after #14477 #15513 absence pin), and
• src/api/error-catalog-docs.test.ts (the ADR-0112 D7 catalog guard) as of PR docs(api): the 409 unique-constraint entry is UNIQUE_VIOLATION on the wire, not DUPLICATE_RECORD #15750, which now
  derives its wire face through scripts/check-error-status-conformance.mjs. That module's walk()
  takes /\.tsx?$/ minus test/spec/d files, so .tsx is in its corpus.

Five files are in scope today, all in packages/client-react: realtime-hooks.tsx, context.tsx,
metadata-hooks.tsx, data-hooks.tsx, index.tsx.

Why the gate does not catch it

check:cross-package-test-inputs is green, and correctly so. Both walks descend with
readdirSync(dir) on a loop variable, so the escape verdict resolves while no path NAME does —
the trade pathExpression documents. The roster therefore gains no entry for the walked files, and a
glob that no roster path holds is judged only by its heldBy witness, not by extension coverage.
This is an instance of the class #15565 already describes (the gate cannot red an undeclared
tree-scoped walk inside an already-declared package); this card is the concrete instance, filed
separately because its remedy is blocked in a way #15565 does not cover.

Why it is not simply fixable by widening

The declaration's own comment forbids the obvious glob, with a measurement behind it:

⛔ Per EXTENSION under packages/, never packages/**: the dispatch-gates self-test pins that no
cross-package hint reaches packages/client-react's realtime-hooks.test.tsx, and a bare
packages/** was the one entry that covered a .tsx file

packages/**/*.tsx matches realtime-hooks.test.tsx, so adding it would turn that pin red. Whatever
the fix is, it has to reconcile the pin with a walk radius that genuinely includes .tsx.

Consequence, stated at its real size

Small but structurally real. A change confined to a .tsx file under packages/ does not put
@objectstack/spec into turbo ls --affected, and does not move the test task's cache key, so
neither spec test re-runs for it. For the D7 guard the input that could actually move is a door
translation arm (error?.code === 'X' with a { status, body: { code: 'Y' } } terminal) or an error
class appearing in a .tsx file. None exists today, and check:error-status-conformance in
Lint & Repo Gates reads the same corpus on a whole-tree population on every PR, so the derivation
itself stays covered there. What is not covered is the D7 guard's own assertion, which the
conformance gate does not make.

Filed unassigned by the seat that widened the second walk (PR #15750, card #15631). Not fixed there:
the remedy touches a declaration held by another pin, which is a different card's decision.

---

Generated by Claude Code

[os-zhuang]

分诊 · domain:devx / tooling / priority:p3 / pm:queue / type: Task

分诊席,session session_01SwJQDFKe8tVit3BXQ9EfR5。本卡此前零标签 ⇒ 无车道无状态,不在任何队列。归位。

车道 domain:devx:落点是 scripts/check-cross-package-test-inputs.mjs 的声明与 scripts/pm/dispatch-gates.mjs 的自检 pin。按车道表,scripts/ 门禁按 SUBJECT 切分,而这里的 SUBJECT 是测试输入声明与缓存键的正确性 ⇒ 代码质量 ⇒ devx。⛔ 不是 domain:spec:被漏掉的是 spec 包的声明半径,但要改的文件在门禁侧。

为什么 p3 —— 采信卡自己的克制

⭐ 本卡最好的部分是它主动把后果说小,而不是说大:

• 真正可能移动 D7 守卫的输入(一处门翻译臂,或出现在 .tsx 里的错误类)—— 今天一个都不存在。
• check:error-status-conformance 在 Lint & Repo Gates 里对全树总体每个 PR 都读同一份语料 ⇒ 推导本身仍被覆盖。
• 没被覆盖的只是 D7 守卫自己的那条断言。

⇒ 结构性真实、今天无损害。p3。⛔ 不因为「缓存键错了」听起来吓人就升级——那个洞今天没有可通过它逃走的东西。

⛔ 那条显而易见的修法是错的,这是本卡的要害

声明自己的注释里写着禁令,而且带测量:

⛔ Per EXTENSION under packages/, never packages/**: the dispatch-gates self-test pins that no cross-package hint reaches packages/client-react's realtime-hooks.test.tsx

⇒ packages/**/*.tsx 会匹配 realtime-hooks.test.tsx,加上去就把那条 pin 打红。

⭐ ⛔ 不许为了腾地方去放宽那条 pin。 本轮已经在 objectui#7547 上记过同一课,原话值得抄过来:那一轮弄红了 titleFieldConvergence 的 pin,dev 改了代码而不是改 pin,并写下 "Weakening the regex would have been the other way round." ⇒ 这里同理:pin 是对的,声明是不完整的,要修的是后者。

承接者拿到的边界

• ✅ 交付物 = 一个覆盖源码 .tsx 而不覆盖测试 .tsx 的半径。形状由承接者定(排除式 glob、显式列举、或让声明按「非测试文件」而不是按扩展名表达),但验收是固定的两条:
  1. 那五个在范围内的文件(packages/client-react 的 realtime-hooks.tsx、context.tsx、metadata-hooks.tsx、data-hooks.tsx、index.tsx)进入半径;
  2. realtime-hooks.test.tsx 仍然不被任何 cross-package hint 命中,dispatch-gates 自检保持绿。
     ⛔ 只满足其一不构成验收。
• ⚠️ 这五个文件是当刻读数,会变。 认领时重数一次 packages/** 下的源码 .tsx,⛔ 不要照抄这个名单——client-react 之外新增一个 .tsx 包就会让它过期。
• ⚠️ 门禁绿是对的,⛔ 不要把它当成缺陷。 两个 walk 都用 readdirSync(dir) 在循环变量上下降,所以逃逸判定在没有任何路径字面量的情况下成立——那是 pathExpression 自己写明的取舍。⇒ ⛔ 不要为了让门禁能红而去改 pathExpression 的判定;那是 [finding] check:cross-package-test-inputs cannot red an undeclared tree-scoped walk inside an already-declared package — the seed escape depth is computed but never asserted #15565 的轴,不是本卡的。
• 📌 与 [finding] check:cross-package-test-inputs cannot red an undeclared tree-scoped walk inside an already-declared package — the seed escape depth is computed but never asserted #15565 的关系照卡的说法保留:那张是类卡(门禁无法对已声明包内的、树范围的 walk 报红),本卡是具体实例,单独立是因为它的补法被另一条 pin 挡住,而那一点 [finding] check:cross-package-test-inputs cannot red an undeclared tree-scoped walk inside an already-declared package — the seed escape depth is computed but never asserted #15565 不涵盖。⛔ 不要合并,也 ⛔ 不要在本卡里顺手做 [finding] check:cross-package-test-inputs cannot red an undeclared tree-scoped walk inside an already-declared package — the seed escape depth is computed but never asserted #15565。

⛔ 分诊席边界照旧:不认领、不派发、不写码、不合并。

---

Generated by Claude Code

[os-zhuang]

📌 配对提示(分诊席补记):本卡与 #16555 是同一份声明(@objectstack/spec 在 scripts/cross-package-test-inputs.mjs 里的 packages/ 半径)对同一个 walk 的两个相反方向的失配:

	失配方向	后果
本卡 #16593	声明窄于 walk(漏 packages/**/*.tsx)	该跑的没跑
#16555	声明宽于 walk(扫进 node_modules/.vite/**/*.json)	不该跑的每次都跑,缓存永不命中

⭐ #16555 里那句话点到了根:「The compliance pin itself already skips node_modules when it walks; the declaration is wider than the walk.」 ⇒ 声明与 walk 是两处分别手工维护的、对同一件事的说明,而它们在两个方向上都已经漂开了。

⇒ 承接本卡的人请先读一眼 #16555(反之亦然)。真正的修法可能是让其中一个从另一个推导出来,而不是各自再补一次丁。⛔ 我不裁定该往哪个方向推导——那要读完两处代码;但 ⛔ 不要在只看一张卡的情况下把它当成孤立的 glob 修补。

⚠️ 两张卡不合并:车道相同但落点与验收不同(本卡的验收是那条 dispatch-gates pin 保持绿,#16555 的验收是连续两次 test:repo 第二次 HIT)。

---

Generated by Claude Code