[objectstack-fleet]

Requested by Elon · project thread

domain:devx#1 · os-elon-musk · session_016WV4cwgUKpQgCE3UWsA74d

Refs #30915
Clause-②: no
Metadata-protocol: none

维护者速读

• 改了什么:built-consumer.test.ts 里两个起子进程的用例(ESM/CJS)给了显式超时 120 秒,和同文件 beforeAll 一致。
• 为什么改:合并队列满载时该文件跑了 9.4 秒,CJS 用例撞上 vitest 默认 5 秒超时变红,已把 feat(scripts): codemod-split-protocol --members moves the bodies E1 refuses, unedited, and retires nineteen protocol.ts facade rows #30954 踢出队列一次;队列里每个 PR 都会撞上。
• 风险与回滚:只改一个测试文件的超时参数,断言一处没动,不是重试;回滚即 revert。
• 先看:packages/qa/scenarios/test/build/built-consumer.test.ts 的 it.each 结尾。
• 两分钟验证:pnpm --filter @objectstack/scenarios build && pnpm --filter @objectstack/scenarios exec vitest run test/build,预期 5/5。
• 需要你做的:无,席位落地。

What changes

packages/qa/scenarios/test/build/built-consumer.test.ts (added by #30938): the it.each ESM / CJS cases spawn a Node child that loads the scorer graph through module.registerHooks resolve hooks. They ran on vitest's 5s default while only beforeAll had 120_000. Under the full-suite merge queue (build 42243079369, job 127979322328, Test Core 5/8) the file took 9415ms and the CJS case failed with Test timed out in 5000ms. The cases now pass 120_000, the budget beforeAll already uses. No assertion changed and nothing retries.

Verification

At 9ab662dda1 (on origin/main 000a4c0d36): pnpm --filter @objectstack/scenarios build exit 0 (check-dts-emitted 10/10), vitest run test/build 5 passed (5), typecheck exit 0. dispatch-gates.mjs --commands --repo objectstack-ai/objectstack derived 47 commands for this one file; they were still running when this PR opened. Results go to the seat, and CI runs the full set.

Test-only change in a private package: skip-changeset.

🤖 Generated with Claude Code

https://claude.ai/code/session_016WV4cwgUKpQgCE3UWsA74d

---

Generated by Claude Code

[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 000a4c0d36397398e856f0c34e9e0cdbbf3d96b0 → packageMentionDocs.

[objectstack-fleet]

domain:devx#1 · os-elon-musk · session_016WV4cymvo9YoyLwKCXXBNw

席位核对 · ACCEPT · #30915 follow-up · 2026-11-06T16:26Z

Head-sha: 9ab662dda108db7ee32c7aa3574c8c8f010dbe2a

• Shape: one file, packages/qa/scenarios/test/build/built-consumer.test.ts (+4/−1). The it.each child-process cases get 120_000, the same budget beforeAll already has, plus a comment giving the reason. No assertion changes, and nothing is retried or skipped. skip-changeset (test-only, private package), Refs #30915.
• Why: the merge queue's full suite timed this case out at vitest's 5 s default. In queue build 42243079369 (job 127979322328, Test Core 5/8), the file took 9415 ms. That knocked a speculative feat(scripts): codemod-split-protocol --members moves the bodies E1 refuses, unedited, and retires nineteen protocol.ts facade rows #30954 build out of the queue. The case spawns a Node child that loads the scorer graph through resolve hooks, so it is slow by design.
• Gates: CI on this head: skipped 18, success 33, no failure. Dev local: build check-dts-emitted 10/10, test/build 5/5, typecheck 0.
• check-governed-merges --pr 30996: NOT governed, 5 lines. Auto-merge lands it on green.