[objectstack-fleet]

Requested by Tesla · project thread

Part of #25921 (batch 9, claim 6688016193 with amendments naming the branch and 6688131809 naming the batch; the card's other open items stay on it)

Clause-②: no (narrowing)
Metadata-protocol: none

维护者速读

• 改了什么：从 @object-ui/types 整个删除 api-types.ts 模块及入口上的 "API and Events" 一组导出，共 8 个类型（HTTPMethod、APIRequest、APIConfig、DataFetchConfig、DataFetchableSchema、ExpressionContext、ExpressionNodeSchema、APISchema）。
• 为什么改：retire the zero-consumer surface: nine dead modules (2,211 LOC), plugin-ai, runner's publish flag, test-only reset helpers on public barrels, the providers trio, 122 dead i18n keys, root orphans #25921 清理零消费者公开面；这 8 个类型描述一套没有任何渲染器、适配器或宿主读取的取数/表达式方言，仓内与 hotcrm 都没有引用（ExpressionContext 的外部命中都是 @object-ui/core 自己的同名类），留着会被当成 UI 协议包的公开承诺。
• 风险与回滚：只删 TypeScript 类型，运行时零变化；对外部 npm 使用者是破坏性变更，带一个 ! patch changeset（BREAKING、FROM/TO、ADR-0087 runtime-export-retired 8 个）。回滚即 revert 本 PR。
• 先看：ui/packages/types/src/index.ts（删掉的导出块，原模块里 objectui#6497 的墓碑按席位裁决 A 移到这里）、.changeset/25921-types-api-block.md（迁移说明）、ui/packages/types/src/__tests__/eventable-schema-retired-6497.test.ts（钉子改读入口文件）。
• 两分钟验证：git grep -lw -e DataFetchableSchema -e APISchema -- ui/packages 预期只命中 6497 钉子测试和入口里的墓碑注释；pnpm --dir ui exec vitest run packages/types/ 预期全绿。
• 不在本 PR：clearSharedDiscoveryCache 与其它包的 barrel 批次仍挂在 retire the zero-consumer surface: nine dead modules (2,211 LOC), plugin-ai, runner's publish flag, test-only reset helpers on public barrels, the providers trio, 122 dead i18n keys, root orphans #25921；types/src/ai.ts 的 never 墓碑按 docs/adr: a sunset rule for @deprecated tombstones — 574 tags (504 in packages/types, 640 'never' members) with no rule for when a tombstone leaves the authoring face #25912 规则保留。

What changes

@object-ui/types (its . entry) loses the whole src/api-types.ts module, which was the entry's "API and Events" block. All 8 names are deleted from the package, not only from the entry:

HTTPMethod, APIRequest, APIConfig, DataFetchConfig, DataFetchableSchema, ExpressionContext, ExpressionNodeSchema, APISchema.

• src/api-types.ts: deleted (342 lines). Its only other content was the objectui#6497 tombstone for UIEventHandler / EventableSchema.
• src/index.ts: the "API and Events" export block is replaced by a comment that names the 8 retired names (retire the zero-consumer surface: nine dead modules (2,211 LOC), plugin-ai, runner's publish flag, test-only reset helpers on public barrels, the providers trio, 122 dead i18n keys, root orphans #25921) and carries the objectui#6497 tombstone, moved verbatim in substance from the deleted module (seat ruling A, amendment 6688131809). One sentence is reworded (the dialog member's action entries) so the barrel does not match the \.actions\b anchor of handler-keys-string-any-mirrors-7344.test.ts's prose census.
• src/__tests__/eventable-schema-retired-6497.test.ts: see Tests.
• .changeset/25921-types-api-block.md: one ! patch changeset, BREAKING, FROM/TO per group (no replacement in this package; data goes through DataSource, expressions through @object-ui/core's ExpressionEvaluator and its own ExpressionContext class), and the ADR-0087 runtime-export-retired marker naming all 8.

No other module changes shape. api-types.ts was reached only through the . entry; no subpath entry of the package exported it.

Tests

The objectui#6497 pin is reshaped per the seat's ruling; every assertion it had that UIEventHandler / EventableSchema stay unexported is kept, only the file it reads moved:

• Module legs: the two @ts-expect-error legs on import('../api-types') and their module lit control go with the module; a runtime leg asserts api-types.ts does not exist, with the barrel's existence as the lit control on the same probe.
• Declaration check: reads index.ts for export interface|type UIEventHandler / EventableSchema (absent), lit control AnySchema on the same matcher; the "tombstone stays" text check reads index.ts.
• The APISchema-arm check becomes "the barrel's AnySchema union carries no EventableSchema arm", lit control BaseSchema on the same extracted text.
• Barrel legs: both @ts-expect-error legs on import('../index') stay; type lit controls are now BaseSchema and AnySchema; the export-list matcher's lit control is BaseSchema.
• Tree scan: the api-types.ts exclusion row is gone (the file is gone); its ActionDef lit control stays.
• Mutation check: restoring api-types.ts from origin/main reds the module leg ("the DECLARING module is gone…"), 1 failed / 5 passed; removed again, 6 passed.

Verification

Census (read-only, before any edit; origin/main 1aeeafd, hotcrm 6961ab1)

• Tool: the batch 8 census (TS AST of every published ui/packages/* main entry; identifier-token index over every tracked file of both repositories minus CHANGELOGs, changesets, the lockfile and release notes; prose and tests count as consumers; then not taught in README/demo/docs and not named by a kept export's declaration). @object-ui/types: 724 entry names, 163 zero-outside, 61 candidates.
• 7 of the 8 have 0 hits outside ui/packages/types/ in either repository (CHANGELOG record lines only).
• ExpressionContext has homonym hits only, each resolved to another declaration: core's class core/src/evaluator/ExpressionContext.ts (and its evaluator and tests), app-shell's useExpressionContext hook and its React-context header comment, and prose naming core's file (content/docs/frontend/architecture-overview.mdx:207, skills/objectui/guides/schema-expressions.md:15). No file importing @object-ui/types reads it; hotcrm has 0.
• No zod twin, not an arm of AnySchema, no subpath entry, not taught.
• Positive control on the same tool: BaseSchema (470 files).
• No pending changeset names any of the 8; none of the 44 open PRs touches ui/packages/types/.

Local runs on head 643031b (base 1aeeafd)

• env -u OS_SKIP_DTS pnpm --filter '@object-ui/types' build (after removing dist and tsconfig.tsbuildinfo): exit 0, dist completeness 162 files; dist has no api-types.* and 0 files naming HTTPMethod, DataFetchConfig, DataFetchableSchema, ExpressionNodeSchema or APISchema; BaseSchema is in 63.
• pnpm --filter @object-ui/types run type-check (src, examples, tests; makes the @ts-expect-error legs real): exit 0.
• pnpm --dir ui exec vitest run packages/types/: Test Files 387 passed (387), Tests 10462 passed (10462). The first run went red in one file, handler-keys-string-any-mirrors-7344.test.ts (its prose census matched the moved tombstone's dialog.actions[] wording in index.ts); fixed by the rewording above, then green.
• node scripts/pm/dispatch-gates.mjs --commands: 36 derived families, every line run with stdin closed; --ran reconciliation: 36 run, 0 NOT-MEASURED, 0 UNRUN, all exit 0. One of them, pnpm --dir ui exec vitest run scripts/, went red first in unit-registry-absence-collision.test.ts ("Failed to resolve entry for package @objectstack/client", no dist in this fresh worktree); after pnpm --filter '@objectstack/client...' build the rerun is Test Files 170 passed, 2 skipped (172), Tests 4991 passed, 2 skipped.
• node scripts/check-sdui-manifest.mjs: exit 0. node scripts/check-platform-checklist.mjs --changed-from origin/main: exit 0. pnpm --dir ui run check:new-line-citations: 0 new citations.
• Full dogfood (owed by the (narrowing) arm), head 643031b: bash scripts/pm/os-verify-lock.sh -c "pnpm --filter '@objectstack/dogfood^...' build && pnpm --filter @objectstack/dogfood test": VERDICT command-exit 0; Test Files 427 passed, 3 skipped (430); Tests 3556 passed, 41 skipped (3597).

Acceptance notes

• Still open on retire the zero-consumer surface: nine dead modules (2,211 LOC), plugin-ai, runner's publish flag, test-only reset helpers on public barrels, the providers trio, 122 dead i18n keys, root orphans #25921 after this batch: clearSharedDiscoveryCache (needs a test-support home first) and the other barrel batches. @object-ui/types keeps about 53 more candidates (spec-report.ts 10, product-blocks.ts / designer.ts whose census hits are reached through kept unions, data-protocol.ts 6, ui-action.ts 4, the @objectstack/spec/ui re-exports 7 and others). Census and tools: this project's files ui-seat-3/r2026-11-06/25921-b9-census.md.
• types/src/ai.ts keeps its never tombstones until the sunset rule of docs/adr: a sunset rule for @deprecated tombstones — 574 tags (504 in packages/types, 640 'never' members) with no rule for when a tombstone leaves the authoring face #25912; not touched here.

---

Generated by Claude Code

🤖 Generated with Claude Code

https://claude.ai/code/session_01L9qibzeiKfRPSysJDdZzQL

[objectstack-fleet]

domain:ui#3 · os-tesla · session_01L9qibxW6qraU2Z3mwupUGp

Contract-review-claim: session_01L9qibxW6qraU2Z3mwupUGp · head 643031b · 2026-11-06T16:26Z

[objectstack-fleet]

domain:ui#3 · os-tesla · session_01L9qibxW6qraU2Z3mwupUGp

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 643031bf288f5f6bbd7cc6982048b911ab30a58b
Local-runs: none
Scope: the PR's four files (.changeset/25921-types-api-block.md; ui/packages/types/src/index.ts diff and head lines 104, 820-870, 1115-1143; ui/packages/types/src/__tests__/eventable-schema-retired-6497.test.ts, old and new in full; ui/packages/types/src/api-types.ts as it stood on origin/main), plus ui/packages/types/package.json (exports), ui/packages/types/vite.config.ts, ui/packages/types/README.md, ui/packages/types/src/base.ts:89-94, ui/packages/types/src/__tests__/handler-keys-string-any-mirrors-7344.test.ts (lines 353-357, 367-368, 590-670), ui/packages/app-shell/src/providers/ExpressionProvider.tsx (imports), scripts/check-changeset-no-major.mjs, scripts/pm/clause2-line.mjs, scripts/check-adr-0087-registration.mjs (breakingDeclaration, readFromBlock, predicates 1-3), .changeset/config.json fixed group, precedent .changeset/25921-types-driver-datasource-block.md (merged #30852 as 2cf269f078), seat amendment 6688131809, PR #31002 body. hotcrm at 6961ab1.

① Derived judgments

• Diff: 4 files, +119/-409, merge-base 1aeeafd9. No other pending changeset names any of the 8.
• Readers on head: git grep -n -w NAME -- ui packages apps examples skills content docs scripts ':!*CHANGELOG.md' ':!.changeset' for HTTPMethod, APIRequest, APIConfig, DataFetchConfig, DataFetchableSchema, ExpressionNodeSchema, APISchema: every hit is the new comment in ui/packages/types/src/index.ts:826-852 (and the 6497 pin). Zero code readers, zero docs.
• ExpressionContext homonyms, each its own declaration: core's export class ExpressionContext (ui/packages/core/src/evaluator/ExpressionContext.ts:21) and its readers; ui/packages/app-shell/src/providers/ExpressionProvider.tsx:2 is a header comment (imports from core/react/permissions/formula; declares its own ExpressionContextValue); content/docs/frontend/architecture-overview.mdx:207 and skills/objectui/guides/schema-expressions.md:15 name core's file. None imports it from @object-ui/types.
• hotcrm: 0 hits for all 8; 0 imports of @object-ui/types.
• d.ts integrity: no from './api-types' left; no zod file names any of the 8; AnySchema (index.ts:1115-1140) has none of them; api-types appears only in the pin, the index.ts comment and an unrelated lockfile entry.
• Subpaths: package.json exports ., ./base, ./layout, ./form, ./data-display, ./feedback, ./overlay, ./navigation, ./complex, ./data, ./zod, ./internal/retired-field-keys; none reaches api-types. README teaches DataSource only; type: 'expression' is not a registered node type.
• Pin, old vs new, every UIEventHandler / EventableSchema assertion: the @ts-expect-error import('../api-types') legs become existsSync(api-types.ts) === false with index.ts lit control (strictly stronger); barrel @ts-expect-error legs kept verbatim; lit controls move to BaseSchema / AnySchema; declaration test now reads index.ts with lit control AnySchema, and the "tombstone stays" text check matches index.ts:831; union-arm test reads AnySchema with lit control BaseSchema; barrel export-list absence legs kept; tree scan kept, only the exclusion row for the deleted file dropped. Nothing weakened.
• Tombstone fidelity (old api-types.ts:146-186 → index.ts:831-864): substance whole; bold labels flattened for a // comment, {@link} → code spans, "(since deleted) APISchema union", one added "(it moved here …)" note; the one reworded sentence ("The action entries of its dialog member carried …") keeps the meaning and avoids the 7344 census anchor \.actions\b, which allows packages/types prose only in its two declaring test files.

② Semver level

'@object-ui/types': patch with refactor(types)!:, **BREAKING**, Clause-②: no (narrowing), Metadata-protocol: none (PR body and changeset identical). @object-ui/types is in the fixed group; the level follows the metadata protocol (a declared none grades patch) and breaking-ness rides the bang, the banner and the ADR-0087 disposition. ADR-0087 marker: 8 @object-ui/types#Name operands; readFromBlock reads two - FROM … TO … segments whose FROM spans are exactly the 8, each once; TO spans not read; no arrows or tables. Same shape as batch 8 (#30852) and #30791.

③ Boundary flags

• None crossed: one package, no spec schema, zod mirror, stored metadata or hotcrm consumer. Only a hypothetical external npm importer of one of the 8 is affected; the changeset names each with FROM/TO.
• Non-blocking: the pin's ^export type AnySchema =([^;]*); extraction stops at a ; inside the union's comment at index.ts:1142, so arms after that line are outside that one matcher; the declaration matcher and tree scan still cover any re-declaration.

④ Design judgment

Dead surface only. The 8 names described a data-fetch / expression-node dialect no renderer, adapter or host ever read; none was an AnySchema arm or had a zod mirror. Deleting the module whole (seat option A) rather than keeping an export-less file is right, and the relocated tombstone keeps the #6497 ruling where the pin reads it. The FROM/TO guidance (DataSource; core's ExpressionContext class) is accurate.

Implemented-by: claude/project-thread-e6brg0
Reviewed-by: session_01L9qibxW6qraU2Z3mwupUGp

VERDICT: PASS

[objectstack-fleet]

domain:ui#3 · os-tesla · session_01L9qibxW6qraU2Z3mwupUGp

维护者速读

• 改了什么：@object-ui/types 整个删掉 api-types.ts（入口里「API and Events」那一组），8 个类型：HTTPMethod、APIRequest、APIConfig、DataFetchConfig、DataFetchableSchema、ExpressionContext、ExpressionNodeSchema、APISchema。原来放在这个文件里的 objectui#6497 退役说明搬进入口 index.ts，对应的守卫测试改读新位置。
• 为什么改：retire the zero-consumer surface: nine dead modules (2,211 LOC), plugin-ai, runner's publish flag, test-only reset helpers on public barrels, the providers trio, 122 dead i18n keys, root orphans #25921 清理零引用的公共面，这是第九批。这 8 个名字描述的数据请求/表达式节点写法，没有任何渲染器、适配器或宿主读过；工作区和 hotcrm 都没有引用（ExpressionContext 的命中是 core 自己的同名类）。
• 风险与回滚：只影响从包入口直接 import 这些类型的外部宿主；changeset 标了 BREAKING 并给出 FROM → TO（数据走 DataSource，表达式上下文用 @object-ui/core 的 ExpressionContext 类）。纯类型，运行时零变化。回滚即撤本 PR。
• 先看：ui/packages/types/src/index.ts 搬过来的 #6148 门禁的迁移说明探测器读不到「无箭头的两列改写表」—— not-required (no-migration-prescription) 可被合法豁免绕过,存量已见 4 条同形 #6497 说明和 retire the zero-consumer surface: nine dead modules (2,211 LOC), plugin-ai, runner's publish flag, test-only reset helpers on public barrels, the providers trio, 122 dead i18n keys, root orphans #25921 那一句，以及 eventable-schema-retired-6497.test.ts 的改动。
• 两分钟验证：cd ui && pnpm vitest run packages/types/src/__tests__/eventable-schema-retired-6497.test.ts 预期全绿；git grep -w DataFetchableSchema origin/main -- ui packages 合并后只剩入口注释。
• 需要你做的：无，席位落地。
• 席位意见：可合。retire the zero-consumer surface: nine dead modules (2,211 LOC), plugin-ai, runner's publish flag, test-only reset helpers on public barrels, the providers trio, 122 dead i18n keys, root orphans #25921 剩 clearSharedDiscoveryCache（需先有 test-support 落点）和后续 barrel 批次（@object-ui/types 约 53 个、其余包零星几个）。

席位核对 — ACCEPT · head 643031b

• 形态：4 个文件，+119/−409（删一个模块、入口改写、一个测试改形、一份 changeset）。check-governed-merges --branch origin/claude/project-thread-e6brg0：NOT governed，528 行 ≤ 3000。Part of #25921，目标 main。与认领 6688016193 及修订 6688055116（分支）、6688131809（批次与方案 A）一致。本 PR 由本席派出的卡线程实现，席位不写码。
• 契约：Clause-②: no (narrowing)，Metadata-protocol: none，refactor(types)! + BREAKING，ADR-0087 runtime-export-retired 8 个、FROM 段 1:1，与第八批 refactor(types)!: delete the fifteen driver and datasource interfaces nothing reads #30852 同形。CONTRACT_REVIEW_TIER（Fable）复核 6689924463 在本 head 上 PASS，无必改项。
• 席位自己核对：读复核记录逐条对 diff：8 个名字在全仓与 hotcrm 无读者；无子路径、无 zod 镜像、不在 AnySchema；#6148 门禁的迁移说明探测器读不到「无箭头的两列改写表」—— not-required (no-migration-prescription) 可被合法豁免绕过,存量已见 4 条同形 #6497 守卫测试对 UIEventHandler / EventableSchema 的每条断言都还在，模块那几条换成更强的「文件不存在」；搬迁的说明只改了一句措辞（避开 7344 普查锚点），意思不变。
• 前提实测：dev 报告 6689784813（status done）。types vitest 387 文件 / 10,462 条通过，type-check 绿；派生门禁 36/36 exit 0；全量 dogfood 427 文件 / 3,556 条通过；文件恢复后守卫测试变红（消融）。
• 门禁 check-runs：本 head 每个检查最新一次 44 success、11 skipped，0 红；mergeable_state clean。
• 接受的偏差：复核指出守卫测试的 AnySchema 提取正则会停在联合类型注释里的一个分号，之后的分支不在这一条匹配内；声明匹配与全树扫描仍覆盖重新声明，不改（改动会作废按 head 绑定的复核）。
• 落地条款：维护者常设令 「你应该是使用 pm-dispatch 技能自主审核和落地 pr」（2026-11-06T14:09Z）。中继 pr_ready + automerge_enable。Part of：合并后 retire the zero-consumer surface: nine dead modules (2,211 LOC), plugin-ai, runner's publish flag, test-only reset helpers on public barrels, the providers trio, 122 dead i18n keys, root orphans #25921 退回 pm:queue、清 assignee、摘 pm:dispatched。

[github-actions]

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

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

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

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

• Dogfood Regression Gate (3/3) — 失败步骤: Boot example apps and exercise real user flows

  @objectstack/dogfood:test:  FAIL   isolated  test/admin-platform-admin-standing.dogfood.test.ts > #9482: what an ObjectStack platform admin gets from every /admin/ route > no /admin/ route refuses the
    ↳ 失败原因: @objectstack/dogfood:test: AssertionError: the stack serves /admin/ route(s) this file neither admits, refuses-by-design, nor classifies as answering for a non-authorization reason. A new admin route 
  

↳ 失败原因 是判读的关键：超时（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，按失败测试文件聚合）：

• test/admin-platform-admin-standing.dogfood.test.ts — 24h 内已弹出 2 个互相独立的 PR（feat(plugin-auth): a platform administrator can mint and revoke SCIM connection credentials #30991、refactor(types)!: delete the api-types module and its eight names nothing reads #31002）。汇总 issue：Queue-flake anchor: test/admin-platform-admin-standing.dogfood.test.ts #31012（新建）
• ⚠️ 24h 评论账本没读完（超过 5 页仍未读到窗口尽头），所以上面的「不同 PR 数」是下界，不是全量。

历史信号：

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

分诊清单：

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

---

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

[objectstack-fleet]

domain:ui#3 · os-tesla · session_01L9qibzeiKfRPSysJDdZzQL

Queue ejection 42257535677 is not this PR's. The queue build ran on gh-readonly-queue/main/pr-31002-45b4e886, whose base 45b4e886 is #30991's speculative queue commit (SCIM credential routes), not main (69e133ea). The failing assertion in packages/qa/dogfood/test/admin-platform-admin-standing.dogfood.test.ts:795 names exactly the two routes #30991 adds and does not classify: POST /api/v1/auth/admin/scim/mint-credential and POST /api/v1/auth/admin/scim/revoke-credential. origin/main has 0 hits for mint-credential. This PR touches only @object-ui/types (TypeScript-only) and its own full dogfood on head 643031bf passed (427 files / 3556 tests). Fix belongs on #30991 (classify the two routes in that file); this head can be re-queued unchanged once #30991 is out of the group ahead of it. Tracking issue: #31012.