[objectstack-fleet]

domain:spec#1 · os-steve · session_01ADHkmPi25XXKx92Xmg4viS

Requested by Steve · project thread
Fixes #29446
Fixes #28820

Clause-②: no
Metadata-protocol: none

维护者速读

• 改了什么:disabledActions 字段说明里"在 Setup › Packaged automation 关掉"改为 Setup › Packaged Actions,并重新生成两页 API 参考文档。
• 为什么改:Packaged automation 页面已退役,管理员照着已发布的 API 参考去找会找不到;packaged action 的开关现在在 Setup 的 Packaged Actions。
• 风险与回滚:只改文字,字段形状、何时出现、ACTION_DISABLED 错误码都不变;回滚即 revert 本 PR。
• 先看:packages/spec/src/api/protocol.zod.ts(disabledActions 的 describe 一行)、content/docs/references/api/app-bundle.mdx。
• 两分钟验证:git grep -n -i 'packaged automation' -- packages/spec content/docs/references 应无命中。
• 需要你做的:无,席位落地。

What changes

• packages/spec/src/api/protocol.zod.ts: the disabledActions .describe() now says an administrator turned the actions off under Setup › Packaged Actions (the nav_packaged_actions entry's label in packages/platform-objects/src/apps/setup-nav.contributions.ts), not the retired Setup › Packaged automation page. The same spelling the sibling N-31: docs and the turned-off sentence stop sending people to the Setup pages N-28 retired #29374 PR (fix(types,docs): the turned-off sentence and the docs stop pointing at retired Setup pages #29476) gives the ACTION_DISABLED refusal sentence.
• Regenerated content/docs/references/api/protocol.mdx (1 row) and content/docs/references/api/app-bundle.mdx (5 rows) through check:generated --fix, which proved only check:docs stale.
• .changeset/29446-disabled-actions-packaged-actions.md: @objectstack/spec patch.

That was the only spec occurrence: git grep -n -i 'packaged automation' -- packages/spec returns nothing on this head. Not packages/types (#29374's half, PR #29476).

Tests

Words only, so no test is added or edited, and no forced test edit. No spec test pins this sentence.

Spec suite at d734db7/daa54ce6 (describe + regen; the later merge brought in ui/ only)

• os-verify-lock -c 'pnpm --filter @objectstack/spec test && pnpm --filter @objectstack/spec typecheck': VERDICT command-exit 0, Test Files 792 passed (792), Tests 23519 passed, 1 todo; typecheck and check:test-typecheck OK.
• pnpm --filter @objectstack/spec check:generated: before the fix 1 of 14 artifact(s) stale: check:docs; --fix regenerated only those two pages (VERDICT command-exit 0).

Acceptance notes

• Not a contract-face change: the accept/reject result of every input is the same, so no consumer package tests are owed.
• Other open PRs on protocol.zod.ts (feat(spec): push channel protocol face — device registration widening, stored device shape, device contract members, push route, APNs/FCM config by credentialRef #29218, feat(spec): a save of a connector's served form drops a leftover undeclared auth key and names it #29456) edit other regions.

Verification

Derived gates at 6558d23: 97 derived, 97 run, 0 NOT-MEASURED, 0 UNRUN

• node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack listed 97 commands; every one exited 0.
• Six first exited 3 (PREREQUISITE NOT MET, not a red) and exited 0 once their prerequisite was met: check-plugin-teardown-shape --self-test (shallow clone, fetched the commit its fixture needs), check:doc-formula-expressions and check:doc-security-posture (built @objectstack/formula and @objectstack/lint), check:skill-examples, check:dual-build-cjs-loads and check:lean-entry-closure (built ./packages/**, 78/78 tasks).
• --ran reconciliation: ✓ 97 derived famil(ies) accounted for — 97 run, 0 NOT-MEASURED.
• check-changeset-no-major.mjs --base origin/main --event on this body: exit 0, Clause-②: no, Metadata-protocol: none, level patch.

---

Generated by Claude Code

🤖 Generated with Claude Code

https://claude.ai/code/session_01ADHkmSE1wCSKEv15rWZ5G2

[github-actions]

📓 Docs Drift Check

1 anchor(s) derived from 1 changed package(s); no hand-written page names any of them, so this run has nothing to list — not a clean bill of health. This check sees only pages that NAME a derived anchor: one that documents this change in prose, or enumerates it in an authoring dialect, names none and stays invisible to it on every run.

What this run could not see

• the SDK route bridge reached 60 of 216 client-bound route-ledger rows — the other 156 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 156: 0 are remediable by widening that discovery convention (an in-repo file declares the path; the convention did not scan it); 55 are structural — on a ledger where NOT ONE row is declared in-repo, so no discovery change reaches them at any price; 101 are undecided (no in-repo declaration, on a ledger that has other in-repo registrars — absence and an unreadable spelling are not distinguishable here). The rows themselves: node scripts/docs-audit/affected-docs.mjs --bridge-coverage
• 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 — 168 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 c88467d4adc417e668474e1b6198a5a7c503ac3f → packageMentionDocs.

Which tree this was computed on

This run read content/docs from e00ed71bc87f393dbc7536d740422524c0667886 — the merge of head 6558d23bfe7930c26757b6542f9fdfcd1b219d36 into base c88467d4adc417e668474e1b6198a5a7c503ac3f, which is what actions/checkout gives a pull_request run. Not the PR head.

A worktree cut from an older main holds a different content/docs, so re-deriving there can legitimately return a different list — that is a different tree, not a wrong row. To answer on the same tree:

# while this PR is open — GitHub drops the merge commit once it closes
git fetch origin e00ed71bc87f393dbc7536d740422524c0667886 && git checkout e00ed71bc87f393dbc7536d740422524c0667886
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin c88467d4adc417e668474e1b6198a5a7c503ac3f 6558d23bfe7930c26757b6542f9fdfcd1b219d36 && git checkout -B drift-repro c88467d4adc417e668474e1b6198a5a7c503ac3f && git merge --no-ff 6558d23bfe7930c26757b6542f9fdfcd1b219d36

node scripts/docs-audit/affected-docs.mjs --json c88467d4adc417e668474e1b6198a5a7c503ac3f

⚠️ That checkout carried uncommitted changes, so the commit above does not fully identify what was read.

[objectstack-fleet]

domain:spec#1 · os-steve · session_01ADHkmPi25XXKx92Xmg4viS

Head-sha: 6558d23b · read 2026-11-02T17:16Z

维护者速读

• 改了什么:disabledActions 的说明文字不再指向已退役的「Setup › Packaged automation」页面，改成「Setup › Packaged Actions」;生成的 API 参考页(protocol、app-bundle)同步更新。
• 为什么改:spec(protocol): the disabledActions describe text still sends admins to the retired Setup › Packaged automation page (item 4 of #29374) #29446(p1)和更早的重复卡 spec: the disabledActions describe still names "Setup › Packaged automation", which is now Setup › Packaged Actions #28820:Setup: retire Setup → Metadata behind redirects into Studio (datasource kept) and retire Packaged automation's flows half; Studio stops linking into Setup #28578 退役了那个页面，公开文档还在把管理员引到不存在的地方。
• 风险与回滚：只改文字，键、值、错误码都不变,spec patch。回滚即撤销本 PR。
• 先看:packages/spec/src/api/protocol.zod.ts 的 disabledActions 说明。
• 两分钟验证：在 content/docs/references/api/protocol.mdx 里搜 Packaged Actions。
• 需要你做的：无，席位落地。

席位意见：可落地，等契约复审。

席位核对 — ACCEPT · domain:spec#1 · head 6558d23b

1. Shape: draft, base main, Fixes #29446 and Fixes #28820, Clause-②: no / Metadata-protocol: none in the body and the changeset (spec patch). 4 files, +19/-7. Not governed. No packages/metadata-protocol/src/protocol.ts change, so the [maintainer] refactor(metadata-protocol): split src/protocol.ts (33,065 lines, +10,169 in 30 days) along its ObjectStackProtocolImplementation seams, one move-only slice per PR #25467 E2 freeze does not apply.
2. Surface: inside claim 6582241787: the disabledActions describe (the only spec hit) and the two regenerated reference pages. The wording matches fix(types,docs): the turned-off sentence and the docs stop pointing at retired Setup pages #29476's ACTION_DISABLED sentence.
3. Readings (dev, on 6558d23b): spec 792/792 files, typecheck green; 97/97 derived gates, DERIVED zero. No forced test edits. Main moved after the dev's merge (c88467d4, view.zod.ts and generated pages). GitHub reads no conflict, and CI runs on the merge ref.
4. Landing: a describe on the published-schema face, so one CONTRACT_REVIEW_TIER review by the seat (claim line follows). After a PASS and green CI, the seat readies and queues.

[objectstack-fleet]

domain:spec#1 · os-steve · session_01ADHkmPi25XXKx92Xmg4viS

Contract-review-claim: session_01ADHkmPi25XXKx92Xmg4viS · head 6558d23 · 2026-11-02T17:18Z

[objectstack-fleet]

domain:spec#1 · os-steve · session_01ADHkmPi25XXKx92Xmg4viS

PR-body guards red on 6558d23b · 2026-11-02T17:21Z

check:closing-target-claim failed because #28820 carried no Claim: naming claude/project-thread-448cbj. The claim lived only on #29446. The seat has now posted the same claim on #28820. This is the gate's remedy 1, so the failed job is re-run once, with no push. The CONTRACT_REVIEW_TIER review passed on this head (record follows).

[github-actions]

⛔ merge queue 构建失败 — 先分诊，再决定要不要重排

队列构建 41493209726 红了。队列跑的是全量套件（PR 侧 CI 只跑 affected 子集），
所以失败的测试可能在本 PR 没碰过的包里 —— 那不是重排能修的。每次盲目重排都会让排在后面的所有 PR 重建一轮。

分类：failure —— 按下面的日志分诊。

失败的 job（日志抽取，best effort）：

• Test Core (2/8) — 失败步骤: Run this shard's tests

  @objectstack/spec:test:  FAIL   local  scripts/dropped-refinements.test.ts > the committed ledger > names at least one site per entry, and its header totals match its body
    ↳ 失败原因: @objectstack/spec:test: AssertionError: expected 993 to be 998 // Object.is equality
  @objectstack/spec:test:repo:  FAIL   repo  scripts/strictness-ledger-doc.test.ts > the ledger and the generated counts agree > is checked in current — every shard on disk equals a fresh render, and no
    ↳ 失败原因: @objectstack/spec:test:repo: AssertionError: expected Map{ …(14) } to deeply equal Map{ …(14) }
  @objectstack/spec:test:repo:  FAIL   repo  scripts/strictness-ledger-doc.test.ts > the ledger and the generated counts agree > the read-time totals equal the sums of the shards' own rows
    ↳ 失败原因: @objectstack/spec:test:repo: AssertionError: expected 'untriaged: 1297 object site(s) across…' to be 'untriaged: 1296 object site(s) across…' // Object.is equality
  

↳ 失败原因 是判读的关键：超时（Test timed out in … / Hook timed out in …）多半是负载/时序，不是本 PR 的回归；
断言（AssertionError: …）才指向真实的行为改变。两者的 FAIL 行长得一模一样，只有这一行能区分。

⚠️ 断言这一侧有一类例外，判据是断言在测什么，不是它是不是 AssertionError。 断言的对象是产品行为（一个值、一个形状、一次拒收）⇒ 照上面读：真实的行为改变，去查，⛔ 不要重排掉；
断言的对象是这次实验自身的有效性前提（跑完的耗时、负载下的先后、任何只在时间预算内才成立的条件）⇒ 它跟超时是同一类，同样对负载敏感，重排一次是合法的判别手段。
识别是机械的：断言的消息或它比较的值本身点名了一段时长、一个时间戳、一个耗时计数。实测过的一对 —— AssertionError: SecurityPlugin.init() ran: expected false to be true 测的是产品行为（真回归）；
AssertionError: this run took over a second, so second-precision stamps could have differed too: expected 1006 to be less than 1000 测的是实验前提：它守护的那条不变式当时是绿的，同一个 head 原样重排一次即成功。
穿着 AssertionError 外衣的时间测量，仍然是时间测量。（⛔ 这只改「怎么读一次红」，不改「哪些测试可以重排」——后者由别处管。）

跨 PR 相同签名（24h，按失败测试文件聚合）：

• scripts/strictness-ledger-doc.test.ts — 24h 内已弹出 10 个 PR（feat(spec): declare the whole-deployment export, every installed package as installable packages in one read (PackageExportBundleSchema) #29100、feat(spec): push channel protocol face — device registration widening, stored device shape, device contract members, push route, APNs/FCM config by credentialRef #29218、fix(spec)!: refuse a dashboard globalFilters entry keyed dateRange beside a declared dateRange #29370、fix(spec)!: a datasource named drivers is refused at every door that parses a datasource #29423、feat(spec): a record page can name the apps whose routes open it (PageSchema.apps) #29437、feat(spec): declare features.sso on the auth config response #29455、build(turbo): hash the Service Worker generator into the Console's build and type-check only #29504、fix(pm): the relay reads no runner 403 as the egress proxy's, and a refused advisory row names its cause #29505、fix(cli): os migrate organization-ownership --apply carries a public-form withdrawal onto a read-only package view into its .custom pair, declared #29508、docs(spec): the disabledActions description names Setup › Packaged Actions, not the retired Packaged automation page #29511），但它们同属 1 条投机栈 ⇒ 1 次独立命中。汇总 issue：Queue-flake anchor: scripts/strictness-ledger-doc.test.ts #29524（已刷新）
• scripts/dropped-refinements.test.ts — 24h 内已弹出 3 个 PR（feat(spec): a record page can name the apps whose routes open it (PageSchema.apps) #29437、fix(pm): the relay reads no runner 403 as the egress proxy's, and a refused advisory row names its cause #29505、docs(spec): the disabledActions description names Setup › Packaged Actions, not the retired Packaged automation page #29511），但它们同属 1 条投机栈 ⇒ 1 次独立命中。汇总 issue：Queue-flake anchor: scripts/dropped-refinements.test.ts #29530（已刷新）
• ⚠️ 24h 评论账本没读完（超过 5 页仍未读到窗口尽头），所以上面的「不同 PR 数」是下界，不是全量。

历史信号：

• 本 PR 过去 24h 无队列失败记录（首次）。
• 过去 24h 队列共有 17 个失败构建（不含本次）。

分诊清单：

1. 失败测试在本 PR 改动的包里 → 真回归，修 PR。
2. 失败测试与本 PR 无关 → 看上面的「跨 PR 相同签名」；已有汇总 issue ⇒ flaky/环境问题实锤，去那张 issue 上谈，修好前重排只会再烧一轮全队列。
3. 两者都不是 → 可能与同组 PR 语义冲突；等前面的 PR 落地或失败出队后再重排一次即可，不要连续重排。

---

Generated by Claude Code · merge-queue-triage workflow (#4859)

[github-actions]

⛔ merge queue 构建失败 — 先分诊，再决定要不要重排

队列构建 41495591770 红了。队列跑的是全量套件（PR 侧 CI 只跑 affected 子集），
所以失败的测试可能在本 PR 没碰过的包里 —— 那不是重排能修的。每次盲目重排都会让排在后面的所有 PR 重建一轮。

分类：failure —— 按下面的日志分诊。

失败的 job（日志抽取，best effort）：

• Test Core (2/8) — 失败步骤: Run this shard's tests

  @objectstack/spec:test:      ✓ inverts the card's measured control: the three bogus keys now FAIL parse instead of adding zero warnings  347ms
    ↳ 失败原因: (这条 FAIL 之后 12 行内没有可识别的原因行 —— 点进 job 看)
  @objectstack/spec:test:  FAIL   local  scripts/dropped-refinements.test.ts > the committed ledger > names at least one site per entry, and its header totals match its body
    ↳ 失败原因: @objectstack/spec:test: AssertionError: expected 993 to be 998 // Object.is equality
  

↳ 失败原因 是判读的关键：超时（Test timed out in … / Hook timed out in …）多半是负载/时序，不是本 PR 的回归；
断言（AssertionError: …）才指向真实的行为改变。两者的 FAIL 行长得一模一样，只有这一行能区分。

⚠️ 断言这一侧有一类例外，判据是断言在测什么，不是它是不是 AssertionError。 断言的对象是产品行为（一个值、一个形状、一次拒收）⇒ 照上面读：真实的行为改变，去查，⛔ 不要重排掉；
断言的对象是这次实验自身的有效性前提（跑完的耗时、负载下的先后、任何只在时间预算内才成立的条件）⇒ 它跟超时是同一类，同样对负载敏感，重排一次是合法的判别手段。
识别是机械的：断言的消息或它比较的值本身点名了一段时长、一个时间戳、一个耗时计数。实测过的一对 —— AssertionError: SecurityPlugin.init() ran: expected false to be true 测的是产品行为（真回归）；
AssertionError: this run took over a second, so second-precision stamps could have differed too: expected 1006 to be less than 1000 测的是实验前提：它守护的那条不变式当时是绿的，同一个 head 原样重排一次即成功。
穿着 AssertionError 外衣的时间测量，仍然是时间测量。（⛔ 这只改「怎么读一次红」，不改「哪些测试可以重排」——后者由别处管。）

跨 PR 相同签名（24h，按失败测试文件聚合）：

• scripts/dropped-refinements.test.ts — 24h 内已弹出 7 个 PR（feat(spec): a record page can name the apps whose routes open it (PageSchema.apps) #29437、docs(spec): tenancy-posture prose says which side of the open/commercial split gates activation #29454、feat(lint)!: os lint refuses a flow region the engine refuses to register (flow-region-shape-invalid) #29495、fix(pm): the relay reads no runner 403 as the egress proxy's, and a refused advisory row names its cause #29505、docs(spec): the disabledActions description names Setup › Packaged Actions, not the retired Packaged automation page #29511、docs(spec): TOP_LEVEL_COLLECTIONS_NEVER_RESIDUAL names the readers of top-level datasets the tree has #29514、feat(pm): a ruled decision card still in the box is a patrol row, and the director's ruling lands with its knock #29515），但它们同属 1 条投机栈 ⇒ 1 次独立命中。汇总 issue：Queue-flake anchor: scripts/dropped-refinements.test.ts #29530（已刷新）
• ⚠️ 24h 评论账本没读完（超过 5 页仍未读到窗口尽头），所以上面的「不同 PR 数」是下界，不是全量。

历史信号：

• ⚠️ 本 PR 过去 24h 已在队列失败 1 次（不含本次）。 内容未变而反复失败 ⇒ 高度怀疑 flaky 测试或与同组 PR 的语义冲突，重排不解决。
• 过去 24h 队列共有 26 个失败构建（不含本次）。

分诊清单：

1. 失败测试在本 PR 改动的包里 → 真回归，修 PR。
2. 失败测试与本 PR 无关 → 看上面的「跨 PR 相同签名」；已有汇总 issue ⇒ flaky/环境问题实锤，去那张 issue 上谈，修好前重排只会再烧一轮全队列。
3. 两者都不是 → 可能与同组 PR 语义冲突；等前面的 PR 落地或失败出队后再重排一次即可，不要连续重排。

---

Generated by Claude Code · merge-queue-triage workflow (#4859)