fix(spec): send a top-level flow trigger to the START node config, not to a type rename

[os-sam]

Fixes #14337

FlowSchema's aliases table pointed trigger at type, and the rename it prescribed cannot be taken. type is the flow KIND, so an author who follows the advice lands on Invalid option one round later with the trigger binding still nowhere. Both keys move to the guidance table, beside the object / objectName / schedule prescriptions that already name the START node's config.

No accept/reject change. A top-level trigger / triggerType was refused before and is refused now; FlowSchema's accepted keys and its type enum are untouched. Only the prescription the refusal carries changes.

The sibling was unmeasured — it is measured now, and it reproduces

The card flagged triggertype: 'type' as probably the same mistake without measuring it. Measured on origin/main (its flow.zod.ts restored on disk, everything else at this branch), verbatim:

ROUND 1 — author writes top-level `triggerType`
Unrecognized key(s) on this flow: `triggerType`. Did you mean `triggerType` -> `type`? Until this
shape was closed, these were dropped silently ...

ROUND 2 — author takes the rename: `type: 'record-after-create'`
Invalid option: expected one of "autolaunched"|"record_change"|"schedule"|"screen"|"api"

That is the same dead end as trigger: the enum the rename points at contains no record-* token at all, so the second round cannot succeed either. The alias table is probed case- and separator-insensitively (aliases[aliasProbe(key)], packages/spec/src/shared/suggestions.zod.ts:463), which is why the source spelling triggertype was answering an authored triggerType. Fixed in this PR, as the card directed.

After this change, the same two inputs:

Unrecognized key(s) on this flow: `trigger`.
  - `trigger` is not a Flow field - a record-change flow binds its trigger on the START node's
    `config` (`{ objectName, triggerType, condition }`, where `triggerType` is a `record-*` token
    such as `record-after-create`), not at the flow top level; the flow-level `type` names the
    flow kind (`record_change`), not the binding. Until this shape was closed, ...

Unrecognized key(s) on this flow: `triggerType`.
  - `triggerType` is not a Flow field - it belongs on the START node's `config`
    (`{ objectName, triggerType, condition }`), where a `record-*` token such as
    `record-after-create` binds the lifecycle event; ...

Where the binding really lives (cited, not paraphrased)

Claim the prescription makes	Anchor
the trigger binds on the START node's config, as { objectName, triggerType, condition }	packages/spec/src/automation/flow-trigger-kind.ts:12
a record-* token is the lifecycle-event grammar	packages/spec/src/automation/flow-trigger-kind.ts:74 (triggerType.startsWith('record-') resolves record_change)
the flow-level type names the KIND, and contains no event token	packages/spec/src/automation/flow.zod.ts:669
guidance is exact-key and suppresses the rename; aliases renders "Did you mean X -> Y?"	packages/spec/src/shared/strict-object.ts:122, packages/spec/src/shared/suggestions.zod.ts:445 and :463

One measured consequence, stated rather than hidden

The alias row was probe-matched, so it also answered the folded spellings; guidance is exact-spelling by design (case folding is the rename channel's job). A non-canonical triggertype therefore now gets the bare rejection instead of the rename it could not take. That is a deliberate trade - no advice beats confidently wrong advice - and it is pinned in flow.test.ts so it cannot drift back into a rename unnoticed.

Verification (all on efe488c42, the final commit; heavy runs under scripts/pm/os-verify-lock.sh)

Run	Verdict
@objectstack/spec - flow.test.ts, flow-trigger-kind.test.ts, strict-object.test.ts, alias-integrity.test.ts, suggestions.test.ts, visible-when-alias-guidance.test.ts	6 files / 210 tests pass (VERDICT command-exit 0)
@objectstack/spec typecheck (tsc --noEmit + check:scripts-typecheck + check:test-typecheck)	pass; the test layer IS compiled - 54 files under tsconfig.test.json, so the new pins are type-checked
check:generated (after pnpm --filter @objectstack/spec build)	all 15 artifacts up to date, check:authorable-surface and check:api-surface among them - the guidance change projects into no generated page
check:system-context-census	OK - 145 anchors resolve, 109 census sites
check:doc-authoring	OK - 14524 customer-facing strings, no internal issue ids
consumer: @objectstack/lint (lint-flow-patterns, validate-flow-trigger-readiness, flow-variable-scope, authoring-rule-input-tier)	4 files / 236 tests pass
consumer: @objectstack/service-automation (engine, canonicalize-stored-flow, flow-cold-boot-bind)	3 files / 158 tests pass
24 further gates from node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack	pass (check:nul-bytes, check:skill-examples 256 blocks, check:doc-anchors, check:corpus-claim-drift, check:cross-package-test-inputs, check:test-source-alias, check:type-check-coverage, check:empty-changeset, check:changeset-no-major, check:adr-0087-registration, and the docs family)
check:test-completeness, check:type-check-debt	exit 3, NOT MEASURED by their own definition (one needs a turbo run test log, the other a fully built workspace) - left to CI, which has both

Reverse verification

Removing the guidance entries on disk (flow.zod.ts restored to origin/main, mutation confirmed by grep counts before the run) turns exactly the three new prescription pins red:

x sends a top-level `trigger` to the START node config, never to a `type` rename
x sends a top-level `triggerType` to the START node config, never to a `type` rename
x no spelling of the removed alias renames to `type` any more
Test Files  1 failed (1)     Tests  3 failed | 93 passed (96)

The two positive controls stay green under the same ablation, correctly - they pin the claim, not the change. The file was restored with git checkout HEAD -- FILE, spelled as an absolute path and the restore proved by blob hash (abc5dc708... on disk equals HEAD:packages/spec/src/automation/flow.zod.ts), with git diff HEAD empty afterwards.

The third commit on this branch re-anchors a file:line citation on content/docs/permissions/system-context.mdx from flow.zod.ts:685 to :702, because this change inserts 17 lines above it. That commit is load-bearing, not cosmetic: reverting only that file makes check:system-context-census fail with [anchor-is-not-a-read-site] on :685 plus [ledger-row-unused] on :702. The anchored line's content is byte-identical at both numbers.

Notes

• Existing pins of the old rename are flipped, never deleted - the assertion now reads .not.toContain on the trigger -> type string, in a dedicated test that also pins the prescription.
• Changeset: @objectstack/spec: patch, customer-facing text, no issue ids.
• This branch is a takeover: two earlier developer sessions died in container restarts. All three inherited commits were re-read hunk by hunk and re-verified from scratch; no inherited measurement was taken on trust.

Generated by Claude Code

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

This PR changes 1 package(s): @objectstack/spec, touching 2 documentable anchor(s).

10 hand-written doc(s) NAME something this change touched and may need an implementation-accuracy re-verification:

• content/docs/api/plugin-endpoints.mdx (via record_change (literal, a string literal in FlowSchema))
• content/docs/automation/approvals.mdx (via record_change (literal, a string literal in FlowSchema))
• content/docs/automation/flows.mdx (via FlowSchema (symbol, a top-level const), record_change (literal, a string literal in FlowSchema))
• content/docs/automation/hooks.mdx (via record_change (literal, a string literal in FlowSchema))
• content/docs/automation/workflows.mdx (via record_change (literal, a string literal in FlowSchema))
• content/docs/concepts/architecture.mdx (via record_change (literal, a string literal in FlowSchema))
• content/docs/getting-started/common-patterns.mdx (via record_change (literal, a string literal in FlowSchema))
• content/docs/kernel/services-checklist.mdx (via record_change (literal, a string literal in FlowSchema))
• content/docs/permissions/capabilities.mdx (via record_change (literal, a string literal in FlowSchema))
• content/docs/protocol/objectql/schema.mdx (via record_change (literal, a string literal in FlowSchema))

⛔ 2 release-owned page(s) also name something this change touched. These are read-only:

• content/docs/releases/v12.mdx (via record_change (literal, a string literal in FlowSchema))
• content/docs/releases/v17.mdx (via FlowSchema (symbol, a top-level const), record_change (literal, a string literal in FlowSchema))

content/docs/releases/ is RELEASE-OWNED (AGENTS.md "Documentation Guardrails"): release
notes are written centrally at release time, and a code PR that edits them is the exact PR
that guardrail exists to stop. They are still audited — read-only. If one of them is actually
wrong, file an issue or open a dedicated docs-only PR; do not edit it here.

What this run could not see

• the SDK route bridge reached 47 of 219 client-bound route-ledger rows — the other 172 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 172: 14 are remediable by widening that discovery convention (an in-repo file declares the path; the convention did not scan it); 56 are structural — on a ledger where NOT ONE row is declared in-repo, so no discovery change reaches them at any price; 102 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.

Coarse fallback — 128 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 dbf115284295b1989d4648dbfbd7e5f3f96357dc → packageMentionDocs.

Which tree this was computed on

This run read content/docs from ac50f706795e1e5df86a9fd1cf7c70112826c33c — the merge of head efe488c42ce309a010a3e9d6a490c4e74db3a8ae into base dbf115284295b1989d4648dbfbd7e5f3f96357dc, 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 ac50f706795e1e5df86a9fd1cf7c70112826c33c && git checkout ac50f706795e1e5df86a9fd1cf7c70112826c33c
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin dbf115284295b1989d4648dbfbd7e5f3f96357dc efe488c42ce309a010a3e9d6a490c4e74db3a8ae && git checkout -B drift-repro dbf115284295b1989d4648dbfbd7e5f3f96357dc && git merge --no-ff efe488c42ce309a010a3e9d6a490c4e74db3a8ae

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

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

Advisory only, and a precision-first one (#9192): a page is listed because it names a
symbol, wire route or SDK method this diff touched — not because it mentions a changed
package. Each row says which anchor put it there, so a wrong row is reportable rather than
merely annoying. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs dbf115284295b1989d4648dbfbd7e5f3f96357dc → pass the list as
args.docs, on the commit named under Which tree this was computed on.

[github-actions]

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

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

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

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

  @objectstack/cli:test:  FAIL   integration  test/run-dev-unbuilt-workspace.e2e.test.ts > the mirror direction: a reader that is never coming back > gives up and exits instead of waiting forever
    ↳ 失败原因: @objectstack/cli:test: AssertionError: the harness SIGKILLed the child — it was still alive at the ceiling. cap 180000 ms (RUN_TIMEOUT_MS, constant and load-independent by design); this child ran 1801
  

↳ 失败原因 是判读的关键：超时（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/run-dev-unbuilt-workspace.e2e.test.ts — 24h 内已弹出 15 个 PR（fix(objectql,runtime,rest): store a serializable manifest projection in the package registry #14499、fix(plugin-sharing): let system writes materialize sharing rules — drop the isSystem skips in bindRuleHooks (#13533) #14528、fix(devx): guard the last two run-on-import gate scripts — KNOWN_IMPORT_UNSAFE 2 to 0 #14593、lint(flows): warn on an uncontained loop body and on a try_catch with no catch, and document loop { try_catch } #14617、test(driver-sql): give the seven unconditionally-live hooks an explicit 60_000 budget #14629、fix(cli): let the dev artifact door own stack-declared security metadata on a host config #14631、fix(metadata): drop the leftover boot-time debug probe from MetadataPlugin.init #14649、fix(cli): walk bulkActions, validation messages and datasets in i18n extract, so the coverage ratchet can see them #14651、fix(objectql,metadata): derive a view container's object through the shared helper, so the row's own name is LAST at every SOURCE registrar (#14399) #14665、fix(cli): remove the ghost field types from generate.ts's three vocabularies #14675、test(runtime): measure which declaration copy the security/sharing seeders consume on an artifact boot with an engine #14687、Declare the scripts/ population two Silent gate families walk but never named #14692、test(cli): make the unread-reader ceiling a load-independent constant at RUN_TIMEOUT_MS #14715、fix(devx): partition os-regen-merge.sh's step-1 conflict message by class #14733、fix(spec): send a top-level flow trigger to the START node config, not to a type rename #14735），分属 11 条投机栈 ⇒ 11 次独立命中。汇总 issue：Queue-flake anchor: test/run-dev-unbuilt-workspace.e2e.test.ts #14752（已刷新）
• ⚠️ 24h 评论账本没读完（超过 5 页仍未读到窗口尽头），所以上面的「不同 PR 数」是下界，不是全量。

历史信号：

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

分诊清单：

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 构建失败 — 先分诊，再决定要不要重排

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

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

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

  @objectstack/cli:test:  FAIL   integration  test/run-dev-unbuilt-workspace.e2e.test.ts > the mirror direction: a reader that is never coming back > gives up and exits instead of waiting forever
    ↳ 失败原因: @objectstack/cli:test: AssertionError: expected 'SIGKILL' to be null
  

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

  @objectstack/plugin-auth:test:  FAIL  src/durability-swallow-repair.test.ts > #12981 batch 6 — the plugin-auth admin-audit swallows report instead of vanishing > admin-import-users :: the run-level au
    ↳ 失败原因: @objectstack/plugin-auth:test: Error: Test timed out in 10000ms.
  

↳ 失败原因 是判读的关键：超时（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/run-dev-unbuilt-workspace.e2e.test.ts — 24h 内已弹出 16 个 PR（fix(objectql,runtime,rest): store a serializable manifest projection in the package registry #14499、fix(plugin-sharing): let system writes materialize sharing rules — drop the isSystem skips in bindRuleHooks (#13533) #14528、fix(devx): guard the last two run-on-import gate scripts — KNOWN_IMPORT_UNSAFE 2 to 0 #14593、test(driver-sql): give the seven unconditionally-live hooks an explicit 60_000 budget #14629、fix(cli): let the dev artifact door own stack-declared security metadata on a host config #14631、fix(metadata): drop the leftover boot-time debug probe from MetadataPlugin.init #14649、fix(cli): walk bulkActions, validation messages and datasets in i18n extract, so the coverage ratchet can see them #14651、fix(objectql,metadata): derive a view container's object through the shared helper, so the row's own name is LAST at every SOURCE registrar (#14399) #14665、fix(cli): remove the ghost field types from generate.ts's three vocabularies #14675、test(runtime): measure which declaration copy the security/sharing seeders consume on an artifact boot with an engine #14687、Declare the scripts/ population two Silent gate families walk but never named #14692、test(cli): make the unread-reader ceiling a load-independent constant at RUN_TIMEOUT_MS #14715、fix(devx): partition os-regen-merge.sh's step-1 conflict message by class #14733、fix(spec): send a top-level flow trigger to the START node config, not to a type rename #14735、fix(deps): take the fix for the four OSV advisories blocking every manifest PR #14736、fix(tooling): a template-literal mode for the vocabulary gate's four shared textual scanners #14739），分属 10 条投机栈 ⇒ 10 次独立命中。汇总 issue：Queue-flake anchor: test/run-dev-unbuilt-workspace.e2e.test.ts #14752（已刷新）
• src/durability-swallow-repair.test.ts — 24h 窗口内只有本 PR 撞到过，暂不汇总（再有一个不同 PR 撞到就会自动开汇总 issue）。
• ⚠️ 24h 评论账本没读完（超过 5 页仍未读到窗口尽头），所以上面的「不同 PR 数」是下界，不是全量。

历史信号：

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

分诊清单：

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

---

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

[claude]

Re-enqueue receipt (domain:spec seat, session_017RbbUMnxkUnWhE4j94v8FE, 2026-09-03T00:33Z) — first kick, signature checked, re-queued once.

• Kick: removed_from_merge_queue 00:29:08Z, reason CI_FAILURE, queue build 33697809557 (the earlier red build 33695118192 at 23:46Z did not eject the PR — the queue rebuilt). Kick count on this PR: 1.
• Signatures (both outside this PR's package — the diff is packages/spec/src/automation/flow.zod.ts + its test + one docs anchor + a changeset, head efe488c42 unchanged since 21:23Z):
  1. packages/cli test/run-dev-unbuilt-workspace.e2e.test.ts › "gives up and exits instead of waiting forever" — AssertionError: expected 'SIGKILL' to be null (23:46Z build: "the harness SIGKILLed the child — it was still alive at the ceiling, cap 180000 ms"). The assertion measures the harness's own time budget, i.e. the timing class; matches the standing queue-flake anchor Queue-flake anchor: test/run-dev-unbuilt-workspace.e2e.test.ts #14752 (16 PRs / 10 independent hits in 24 h).
  2. packages/plugin-auth src/durability-swallow-repair.test.ts › "The durability log-level gate cannot see the catch { return null; } seeder family — 15 files outside #12923's five, and neither widening path is cheap #12981 batch 6 … admin-import-users" — Test timed out in 10000ms. Timeout class; only this PR in the 24 h window so far, package untouched by this diff.
• Head vs main: trial merge git merge-tree --write-tree origin/main refs/pull/14735/head at origin/main 224f8ea4a — clean, zero conflicts; no commit on main since 23:15Z touches the PR's files; mergeable_state: clean.
• Decision (platform-readings rule: a kicked PR is re-queued once when the signature matches a known flaky, with this receipt on the PR; a second kick stops re-queueing and re-judges by signature): auto-merge (SQUASH) re-enabled once, now. A second kick on the same signatures ⇒ no further re-queue from this seat; the flake conversation stays on Queue-flake anchor: test/run-dev-unbuilt-workspace.e2e.test.ts #14752.

---

Generated by Claude Code

[github-actions]

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

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

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

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

  @objectstack/cli:test:  FAIL   integration  test/run-dev-unbuilt-workspace.e2e.test.ts > the mirror direction: a reader that is never coming back > gives up and exits instead of waiting forever
    ↳ 失败原因: @objectstack/cli:test: AssertionError: expected 'SIGKILL' to be null
  

↳ 失败原因 是判读的关键：超时（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/run-dev-unbuilt-workspace.e2e.test.ts — 24h 内已弹出 16 个 PR（fix(plugin-sharing): let system writes materialize sharing rules — drop the isSystem skips in bindRuleHooks (#13533) #14528、fix(cli): let the dev artifact door own stack-declared security metadata on a host config #14631、fix(metadata): drop the leftover boot-time debug probe from MetadataPlugin.init #14649、fix(cli): walk bulkActions, validation messages and datasets in i18n extract, so the coverage ratchet can see them #14651、fix(objectql,metadata): derive a view container's object through the shared helper, so the row's own name is LAST at every SOURCE registrar (#14399) #14665、fix(cli): remove the ghost field types from generate.ts's three vocabularies #14675、test(runtime): measure which declaration copy the security/sharing seeders consume on an artifact boot with an engine #14687、Declare the scripts/ population two Silent gate families walk but never named #14692、test(cli): make the unread-reader ceiling a load-independent constant at RUN_TIMEOUT_MS #14715、test(cli): derive the vitest tier population instead of freezing it in a list #14717、fix(devx): partition os-regen-merge.sh's step-1 conflict message by class #14733、fix(spec): send a top-level flow trigger to the START node config, not to a type rename #14735、fix(deps): take the fix for the four OSV advisories blocking every manifest PR #14736、fix(tooling): a template-literal mode for the vocabulary gate's four shared textual scanners #14739、test(runtime): pin the measured loadMany vs by-name divergence for #14423 (a) #14741、test(plugin-approvals): pin the lock release in the tenant-admin reverse check #14750），分属 10 条投机栈 ⇒ 10 次独立命中。汇总 issue：Queue-flake anchor: test/run-dev-unbuilt-workspace.e2e.test.ts #14648（已刷新）
• ⚠️ 24h 评论账本没读完（超过 5 页仍未读到窗口尽头），所以上面的「不同 PR 数」是下界，不是全量。

历史信号：

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

分诊清单：

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

---

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

[claude]

Second kick — re-queueing stops here (domain:spec seat, session_017RbbUMnxkUnWhE4j94v8FE, 2026-09-03T02:12Z).

• removed_from_merge_queue 02:08:03Z (CI_FAILURE, queue build 33704757465, job 100491457306 Test Core (1/6)): the same signature as the first kick — packages/cli test/run-dev-unbuilt-workspace.e2e.test.ts › "gives up and exits instead of waiting forever" — AssertionError: expected 'SIGKILL' to be null. Kick count on this PR: 2; head efe488c42 unchanged; the diff never touches packages/cli.
• Signature judgment (platform rule: a second kick on the same signature is not re-queued; re-judge by signature): not this PR's package; the surviving flake anchor is Queue-flake anchor: test/run-dev-unbuilt-workspace.e2e.test.ts #14648 (Queue-flake anchor: test/run-dev-unbuilt-workspace.e2e.test.ts #14752 was closed as its duplicate at 00:53Z — the anchor lookup only sees finding-labelled cards, merge-queue-triage filed a SECOND anchor for a test file it already had an open anchor for (#14679 duplicating #14648, 74 minutes apart) — the aggregation it promises in its own body did not happen #14682 records that defect); the fix is PR test(cli): make the unread-reader ceiling a load-independent constant at RUN_TIMEOUT_MS #14715 (test(cli): make the unread-reader ceiling a load-independent constant at RUN_TIMEOUT_MS), open and itself in this queue, ejected by the same flake in the same batches. No fix is on main yet, so the flake is not "fixed and recurring" — it is the standing flake with its fix stuck behind it.
• Disposition: auto-merge is left off (the kick cleared it and this seat does not re-enable it). The card FlowSchema's trigger alias prescribes a rename to type, and taking that advice cannot work — the binding moves to the START node's config #14337 goes pm:blocked with Blocked-by: #14648 and Unlock-action: re-check PR #14735 — when Queue-flake anchor: test/run-dev-unbuilt-workspace.e2e.test.ts #14648 closes (PR test(cli): make the unread-reader ceiling a load-independent constant at RUN_TIMEOUT_MS #14715 merged), the unlock scan returns the card and this seat re-checks the PR (trial merge, checks, re-queue) instead of re-dispatching. The ACCEPT (5517551364) stands; nothing on this PR needs work.

---

Generated by Claude Code

[claude]

Unlock re-check (domain:spec seat, session_017RbbUMnxkUnWhE4j94v8FE, 2026-09-03T04:03Z) — the blocker closed, re-queued once.

• Blocker: Queue-flake anchor: test/run-dev-unbuilt-workspace.e2e.test.ts #14648 (the run-dev-unbuilt-workspace.e2e.test.ts queue-flake anchor) CLOSED 03:52:25Z — its fix PR test(cli): make the unread-reader ceiling a load-independent constant at RUN_TIMEOUT_MS #14715 merged 03:52:24Z (accb9231c, RUN_TIMEOUT_MS now a load-independent constant at packages/cli/test/run-dev-unbuilt-workspace.e2e.test.ts:93 on origin/main). Card FlowSchema's trigger alias prescribes a rename to type, and taking that advice cannot work — the binding moves to the START node's config #14337's Unlock-action: re-check PR #14735 fires.
• Re-check: head efe488c42 unchanged since ACCEPT 5517551364; all 35 checks green (33 success / 2 skipped); trial merge git merge-tree --write-tree origin/main refs/pull/14735/head at origin/main 521eaf9e4 — clean (the system-context.mdx line is the os-regen merge driver regenerating, not a conflict); mergeable_state: clean; not governed.
• Decision: auto-merge (SQUASH) re-enabled once. Kick history: 2 (00:29Z, 02:08Z), both on the signature test(cli): make the unread-reader ceiling a load-independent constant at RUN_TIMEOUT_MS #14715 fixes. If the SAME signature recurs now that the fix is on main, it is a new problem to re-diagnose, not the flake — no reflex re-queue.

---

Generated by Claude Code