[objectstack-fleet]

Requested by Steve · project thread

Prerequisite for #31661 (it was ejected from the merge queue by this test, queue build 42539489585, Test Core 1/8, triage 6729558102). Test-only; no card of its own, so skip-changeset.

维护者速读

• 改了什么：只改 packages/cli/test/validate-namespace-name.test.ts 的夹具：两个命名空间那条 CONTROL 里，beta 包的 tool 从 nsn_lookup 改名为 nsn_other_lookup;同命名空间那几条仍共用 tool/nsn_lookup。
• 为什么改:feat(objectql)!: a tool holds one name per package (bare-name one holder, after the AI family) #31661 让一期 bare-name 规则在封存后按全环境拒绝同名 tool,于是这个"两个命名空间可以同名"的 CONTROL 在 premise 用例里被 BareNameConflictError 422 拒掉。它本意只测 feat(objectql)!: refuse a (type, name) held twice inside one namespace #31717 的命名空间规则，不该被 bare-name 规则判。
• 风险与回滚：只动测试夹具和一个用例标题，不改产品代码。回滚即 revert。
• 先看：packagesStack 的 betaTool 一行。
• 两分钟验证：pnpm --filter @objectstack/cli exec vitest run test/validate-namespace-name.test.ts —— 预期 4 passed。
• 需要你做的：无，席位落地后 feat(objectql)!: a tool holds one name per package (bare-name one holder, after the AI family) #31661 可重新入队。

What changes

• packagesStack(betaNs) gives the beta package's tool its own name when betaNs is not nsn (nsn_other_lookup), so the two-namespace CONTROL shares only the page nsn_home. The shared-namespace fixtures still hold page/nsn_home and tool/nsn_lookup twice, so every refusal assertion is unchanged. The CONTROL's title now says what it holds ("the same page name in two namespaces validates"). A doc comment says why: a tool is also phase 1's bare-name one-holder type, judged environment-wide, so a shared tool across two namespaces is that rule's refusal, not this rule's CONTROL. os validate does not run the bare-name rule, so the CLI CONTROL reads the same either way; only the package-door premise is affected.

Verification

Every run under os-verify-lock, CLI closure rebuilt each time:

• This head 86e164c2 (main cae8d8fe + this commit): test/validate-namespace-name.test.ts 4 passed.
• This head merged with feat(objectql)!: a tool holds one name per package (bare-name one holder, after the AI family) #31661's head 30b6c84f (scratch branch): 4 passed.
• main merged with feat(objectql)!: a tool holds one name per package (bare-name one holder, after the AI family) #31661 (no fix, scratch branch): 1 failed / 3 passed, the premise: expected BareNameConflictError: Bare-name conflict… to be undefined. That is the queue failure, reproduced, and the fix clears it.
• Lint: eslint packages/cli/test/validate-namespace-name.test.ts --no-inline-config exit 0. Gates: dispatch-gates --ran on 86e164c2: 49 derived, 49 run, 0 NOT-MEASURED, all exit 0 (check:dts-closure and check:dual-build-cjs-loads first read a declaration-less / partial local build and were re-run green after a full closure build).

---

Generated by Claude Code

🤖 Generated with Claude Code

https://claude.ai/code/session_01ADHkmQv69sQL5nfT8xuPWs

[objectstack-fleet]

domain:server#1 · os-steve · session_01ADHkmPF1skfu2kx89BEXZi

席位 ACCEPT · head 86e164c2d1a5f50b6c5f5a0ceffe24b105ec1255

测试专改(1 个文件，+18/-5,skip-changeset),是 #31661 的前置。

• 起因：feat(objectql)!: a tool holds one name per package (bare-name one holder, after the AI family) #31661 的队列构建 42539489585 红在 Test Core (1/8)(分诊 6729558102)。feat(objectql)!: refuse a (type, name) held twice inside one namespace #31717 的两命名空间 CONTROL fixture 让两个包共用 tool nsn_lookup。feat(objectql)!: a tool holds one name per package (bare-name one holder, after the AI family) #31661 把 tool 加进 phase-1 一主名单之后，bare-name 规则在封存后会拒绝它，所以 premise 用例里的 package door 先拒了。
• 修法：命名空间不同时，beta 的 tool 改名为 <betaNs>_lookup。同一命名空间的 fixture 照旧共用 tool/nsn_lookup,N 的 12 类型拒绝仍覆盖 tool。CONTROL 标题改成「the same page name in two namespaces validates」,与它实际覆盖的内容一致。断言一条没动。
• 卡片线程的本地证据：本 head 4 passed;本 head + feat(objectql)!: a tool holds one name per package (bare-name one holder, after the AI family) #31661 30b6c84 4 passed;main + feat(objectql)!: a tool holds one name per package (bare-name one holder, after the AI family) #31661 不带本修复 1 failed(复现了队列里的红)。门禁 49/49,0 NOT-MEASURED。
• check-governed-merges:改的只是测试文件，不涉及受治理面。

CI 全绿后落地：relay pr_ready + automerge_enable。合入后，席位经 relay 给 #31661 重新开 auto-merge 入队一次。

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 0 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json f2abd4767b32200bcbd866cd34e0b2863f06d148 → packageMentionDocs.