test(qa-scenarios): add the asset_lifecycle mid-tier scenario card by objectstack-fleet[bot] · Pull Request #30695 · objectstack-ai/objectstack

objectstack-fleet · 2026-11-05T22:35:10Z

Requested by Elon · project thread
Fixes #30481
Clause-②: no
Metadata-protocol: none

维护者速读

改了什么:新增「资产全生命周期」中档场景卡(8 个对象、报废审批、3 个角色其中 2 个按行限定、1 个按类别统计账面价值的报表、120 件资产跨 6–9 月采购、10 道问数、6 个写操作、6 个 agent 动作),并配一份只属于这张卡的真值测试。
为什么改:落实 cloud#3600 九个场景中的资产场景,让 AI 建应用、问数、代办写操作都有一张能用代码判分的资产管理卡(领用与归还、维修、按月折旧、报废审批)。
风险与回滚:只加测试数据和测试,所在包私有、不发布,运行时零改动,也没碰兄弟卡共用的文件;回滚即删两个新文件。
先看:① docs/qa/scenarios/asset_lifecycle.json 的 run.questions 与 run.operations;② packages/qa/scenarios/test/asset-lifecycle.test.ts 的 EXPECTED_TRUTHS 及旁边的手算注释;③ 同一文件里「seed internally consistent」用例(折旧、账面价值、资产状态与单据对得上)。
两分钟验证:pnpm --filter @objectstack/scenarios test,预期 5 个测试文件、70 个用例全绿。
需要你做的:无,席位落地。

What changes

docs/qa/scenarios/asset_lifecycle.json (new): the 资产全生命周期 asset-lifecycle mid-tier card.
- Eight objects: department, employee, asset_category (useful life, straight-line method), asset (the main object, with roll-up accumulated_depreciation and formula book_value), checkout (checkout and return, with the return condition), repair_order, disposal_request (the scrap approval, routed to the manager of the asset's department) and depreciation_entry (one per asset per month, posted by a scheduled flow).
- Three personas: employee (the assets they hold, their own checkouts, repairs and scrap requests; no cost, book value, depreciation, budget or home address) and dept_manager (their department; no home address) carry a row scope; asset_admin sees every asset but no asset budget.
- Seed: 120 assets bought June to September 2026, 92 checkouts (64 kits, re-issues after repair, 14 loaners), 19 repair orders, 7 scrap requests in all four states and 297 depreciation entries. The arithmetic rule that generated it is stated in the card's $comment, so every truth can be worked by hand.
- Run half: 10 questions, 6 operations and 6 agent actions (one confirm-gated); iterate adds transfers between departments.
packages/qa/scenarios/test/asset-lifecycle.test.ts (new): this card's own test file.
- It pins all 10 computed truths and the 10 per-persona truths against hand-worked values; each derivation is written next to its pin.
- It asserts the mid-tier floor, and the seed's own consistency: each depreciation entry is cost over useful life, posted after the purchase month and never from the disposal month on; accumulated depreciation sums the entries and book value is cost minus it; each asset's status and custodian follow its checkouts, repairs and scrap request; each scrap request's approver is its department's manager.
- It asserts each operation targets a row in the state its story needs (an overdue loaner, a submitted request the manager holds, an approved request, the employee's own request, an asset in repair, serials and a checkout key that do not exist yet).
- It shows that a wrong seed cell and a wrong truth spec in fixture copies go red against those pins.

Why

The card is one of the six mid-tier scenarios ruled on objectstack-ai/cloud#3600 (Q1 = v3, 「同意这9个场景」). It gives the asset domain a scenario whose answers, permission boundaries and write outcomes are graded by code only.

Tests

pnpm --filter @objectstack/scenarios test: 5 files, 70 tests passed (64 before this PR). pnpm --filter @objectstack/scenarios typecheck: exit 0, after building the closure with pnpm --filter '@objectstack/scenarios^...' build; tsc --listFiles lists the new test file. Both read at head 0ffa47e2a6.

Acceptance notes

File name. The card is asset_lifecycle.json, not asset-lifecycle.json as the issue spells it: a card's id must be a snake_case machine name equal to the file's basename. test(qa-scenarios): add the travel_expense mid-tier scenario card #30600 made the same call.
No shared file touched. Since test(qa-scenarios): add the travel_expense mid-tier scenario card #30600, test/library.test.ts names only the three control cards and the README's "Adding a card" step already sends a mid-tier card's pins to its own file. So this PR adds two files and edits none, and it cannot conflict with the sibling cards.
Seven operation kinds, six operations. receive_and_issue_from_text covers two of them: entry from free text with lines (three monitors on one delivery) and the multi-step chain (register them, then check one out). The workflow step is manager_approves_scrap; its progress query is the question dr_0005_waiting_on, asked about a different request so its truth stays a fact of the seed.
New rows in post-states. A where cannot name a created row's id, so the new checkout is matched by employee plus checked_out_on; the test proves no seeded checkout has that pair, and that the three delivered serials are new.
Overdue means due before asOf. overdue_loaners_by_department filters due_on lt "2026-10-31", the card's asOf; the window operators only name ranges that end on asOf.
No schema field for some floor items. An approval or automation flow, "declarative preferred" and a report as distinct from a dashboard have no field. The card states them in prompt.detailed (zh and en) and capabilities, seeds disposal_request as an expected object, and declares the report under expect.dashboards. Nothing in the loader grades them.
Capability names. The loader checks only the area half of a tag. approvals.dynamic-approver-routing is a checklist id; the rest follow the descriptive names travel_expense.json uses.
Changeset. packages/qa/scenarios is "private": true and the diff touches no published package, so this PR carries no changeset and asks for skip-changeset, as test(qa-scenarios): add the travel_expense mid-tier scenario card #30600 did.
Sources. The domain is designed from the card text and general business knowledge; the card's Reference line names no template. objectstack-ai/cloud#3567 was not read.

Verification

scenarios test + typecheck (head 0ffa47e)

 Test Files  5 passed (5)
      Tests  70 passed (70)
> tsc --noEmit
os-verify-lock: VERDICT command-exit 0

Run after merging main and a whole-tree pnpm build (118 of 118 turbo tasks).

dispatch-gates --commands (50 commands, local, head 0ffa47e)

All 50 derived commands exit 0 on head 0ffa47e2a6. The --ran reconciliation reads: 50 derived, 50 run, 0 NOT-MEASURED, 0 UNRUN, a derived zero because every line recorded its exit code.

The first run, on the pre-merge head 11193506f5, had 47 exit 0 and 3 exit 3 (PREREQUISITE NOT MET, nothing measured). Each cleared once its prerequisite was in place:

check-plugin-teardown-shape.mjs --self-test, after git fetch --unshallow origin main (its fixture is a pinned commit a shallow clone lacks);
check:lean-entry-closure and check:dual-build-cjs-loads, after the whole-tree build.

Changed lines: 1294 (+1294 / -0, 2 files), under the 3000 threshold (dispatch-gates.mjs reading).

Human Minimum

1. Schemas start as Zod; packages/spec holds no runtime logic. (No schema touched.)
2. Every name I added uses the casing for its kind.
3. No formatter ran; pnpm lint passes. (No formatter ran, and eslint on the new test file exits 0; the repo-wide pnpm lint is left to CI's Lint & Repo Gates.)
4. One issue, one branch off an up-to-date main, one pull request.
5. A change that publishes carries a changeset, and both declaration lines are filled in here and in the changeset. (Publishes nothing: private package.)
6. packages/spec touched: its generated artifacts are regenerated and committed. (Not touched.)
7. No hand edits to content/docs/references/, packages/*/CHANGELOG.md or content/docs/releases/.
8. Title, body and comments are in English.
The Before Submitting list in CONTRIBUTING.md is done. (Every item but the repo-wide pnpm lint, left to CI as in item 3.)

Generated by Claude Code

The open library's 资产全生命周期 (asset lifecycle) scenario: eight objects (department, employee, asset_category, asset, checkout, repair_order, disposal_request, depreciation_entry), 120 assets bought June-September 2026, a scrap approval routed to the asset's department manager, monthly straight-line depreciation, three personas (two row-scoped), ten questions, six operations and six agent actions. The seed follows the arithmetic rule in the card's $comment. Its own test file pins every computed truth, over all rows and per persona, against hand-worked values, checks the seed's internal consistency, and shows a wrong seed cell and a wrong truth spec in fixture copies go red. Co-authored-by: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016WV4czx7zatyA1s7R4yPhB

…-m0naih

github-actions · 2026-11-05T22:36:38Z

📓 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 a2437b560bd8872feece6ec8b57c6fdf21cff1f4 → packageMentionDocs.

objectstack-fleet · 2026-11-05T22:52:34Z

domain:devx#3 · os-elon-musk · session_016WV4cz3RTQjLh7hZBLzgtZ

席位核对 · ACCEPT · `0ffa47e2a6` · 2026-11-05T22:52Z

Head-sha: 0ffa47e2a6d676f906943dab11de2ead8f28d25f

Shape: 2 files, +1,294/−0 (< 3,000), both on the amended claim surface (docs/qa/scenarios/asset_lifecycle.json, packages/qa/scenarios/test/asset-lifecycle.test.ts). Not governed. Fixes #30481, Clause-②: no, Metadata-protocol: none at line start.
Premise measured: schema from feat(scenarios): scenario-card schema + loader (private packages/qa package) and nine open seed cards #30340 on main; sibling Scenario library: mid-tier card — 差旅报销 travel expense (8–10 问数 + 4–6 write operations, row-scoped personas) #30476 landed as PR test(qa-scenarios): add the travel_expense mid-tier scenario card #30600, which made library.test.ts and the README card-agnostic, so no shared line is touched.
Gates: check-runs on this head read by the seat: 35 success, 18 skipped (path filter), 0 failed or pending. Dev's local dispatch-gates 50/50 exit 0, --ran 0 NOT-MEASURED.
Spot checks (seat's own arithmetic against the pinned truths): book_value_by_category Laptop 30 × 7200 − 200 × 76 = 200,800 ✓; depreciation_last_month (23·200 + 23·30 + 22·200 + 22·20 = 10,130) − a043's 200 = 9,930 ✓. The card's acceptance "a deliberately wrong truth in a fixture copy goes red" is two cases in the test file (wrong seed cell, wrong truth spec).
Accepted deviations: snake_case basename (id = basename, as test(qa-scenarios): add the travel_expense mid-tier scenario card #30600); surface narrower than the claim; floor items with no schema field stated in prompt.detailed and capabilities (as test(qa-scenarios): add the travel_expense mid-tier scenario card #30600).
Out of scope: none. Skills-docs: n/a (Metadata-protocol: none).
Changeset: skip-changeset, the package is private (as test(qa-scenarios): add the travel_expense mid-tier scenario card #30600).
Landing: non-governed; flips when the maintainer's landing word for this term is on record.

github-actions · 2026-11-06T04:23:16Z

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

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

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

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

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

@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — evidence pointers (#5623) > is green against a verbatim copy of the shipped ledgers
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — evidence pointers (#5623) > stays green when the missing path is attributed to ANOTHER repo
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — evidence pointers (#5623) > never bounds a citation attributed to ANOTHER repo
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — evidence pointers (#5623) > prints the citation count and how many are in range, in the documented two
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — symbol anchors (#12516) > stays GREEN on the drifted BEFORE-state — the honest residual this grammar e
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — symbol anchors (#12516) > prints the anchor count and how many resolve, equal on a green run
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — the evidence-scan population (#13041) > stays GREEN when a `dead` entry carries the SAME rotted pointe
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — the evidence-scan population (#13041) > declares every status either scanned or explicitly unscanned, 
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — the live-elsewhere criteria (#13483) > is green on the shipped ledgers and publishes the population be
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — the live-elsewhere criteria (#13483) > is green on a planted live-elsewhere row and counts it as carry
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — the README state table (#7257) > is green against a verbatim copy, and says how many rows it checked
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — the generated count artifact (#7377, sharded #20361) > is green against a verbatim copy, says the shar
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,

↳ 失败原因 是判读的关键：超时（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/liveness/check-liveness.test.ts — 24h 内已弹出 3 个 PR（test(qa-scenarios): add the leave_balances mid-tier scenario card #30690、test(qa-scenarios): add the asset_lifecycle mid-tier scenario card #30695、test(qa-scenarios): add the order_to_cash mid-tier scenario card #30706），但它们同属 1 条投机栈 ⇒ 1 次独立命中。⚠️ 同签名的汇总 issue Queue-flake anchor: scripts/liveness/check-liveness.test.ts #30374 已作为重复关闭，且没有仍然打开的同签名汇总 issue ⇒ 本次不新建（新建只会再被判重）。请到它指向的那张 issue 上谈，或重开 Queue-flake anchor: scripts/liveness/check-liveness.test.ts #30374。
⚠️ 24h 评论账本没读完（超过 5 页仍未读到窗口尽头），所以上面的「不同 PR 数」是下界，不是全量。

历史信号：

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

分诊清单：

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

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

objectstack-fleet · 2026-11-06T04:26:39Z

domain:devx#3 · os-elon-musk · session_016WV4czx7zatyA1s7R4yPhB

Queue ejection triage · not this PR's

Check: merge-queue run 42160413666, Test Core (1/8), @objectstack/spec scripts/liveness/check-liveness.test.ts.
Reproduced on this PR's queue commit ed7545d96f: tsx scripts/liveness/check-liveness.mts in packages/spec exits 1 with one finding, 1 UNANCHORED: manifest/contributes.kinds → packages/objectql/src/engine.ts.
Why it is not this PR's: this PR adds docs/qa/scenarios/asset_lifecycle.json and packages/qa/scenarios/test/asset-lifecycle.test.ts only; it touches neither a liveness ledger nor engine.ts. The citation lost its anchor at fix(scripts,objectql): codemod-split-engine --members reads hand-written facet headers and inverts its import edits; move registerApp, registerDriver and registerHook #30716's queue commit 198d112558, which moves registerApp (the contributes.kinds read) out of engine.ts: engine.ts names kinds 5 times on main 100303c043 and 0 times at 198d112558. This PR sat behind fix(scripts,objectql): codemod-split-engine --members reads hand-written facet headers and inverts its import edits; move registerApp, registerDriver and registerHook #30716 in the same speculative stack, as did test(qa-scenarios): add the leave_balances mid-tier scenario card #30690 and test(qa-scenarios): add the order_to_cash mid-tier scenario card #30706.
Fix: belongs to fix(scripts,objectql): codemod-split-engine --members reads hand-written facet headers and inverts its import edits; move registerApp, registerDriver and registerHook #30716 (repoint the citation), which is already out of the queue for it (comment 6676744620). Nothing changes here: head 0ffa47e2a6 stays, its own CI is green, and it needs only a re-enqueue.

github-actions · 2026-11-06T04:36:41Z

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

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

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

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

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

@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — evidence pointers (#5623) > is green against a verbatim copy of the shipped ledgers
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — evidence pointers (#5623) > stays green when the missing path is attributed to ANOTHER repo
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — evidence pointers (#5623) > never bounds a citation attributed to ANOTHER repo
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — evidence pointers (#5623) > prints the citation count and how many are in range, in the documented two
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — symbol anchors (#12516) > stays GREEN on the drifted BEFORE-state — the honest residual this grammar e
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — symbol anchors (#12516) > prints the anchor count and how many resolve, equal on a green run
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — the evidence-scan population (#13041) > stays GREEN when a `dead` entry carries the SAME rotted pointe
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — the evidence-scan population (#13041) > declares every status either scanned or explicitly unscanned, 
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — the live-elsewhere criteria (#13483) > is green on the shipped ledgers and publishes the population be
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — the live-elsewhere criteria (#13483) > is green on a planted live-elsewhere row and counts it as carry
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — the README state table (#7257) > is green against a verbatim copy, and says how many rows it checked
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,
@objectstack/spec:test:  FAIL   local  scripts/liveness/check-liveness.test.ts > check:liveness — the generated count artifact (#7377, sharded #20361) > is green against a verbatim copy, says the shar
  ↳ 失败原因: @objectstack/spec:test: AssertionError: Spec liveness gate (registry-rooted) — governed types: object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view, report,

↳ 失败原因 是判读的关键：超时（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/liveness/check-liveness.test.ts — 24h 内已弹出 4 个 PR（test(qa-scenarios): add the leave_balances mid-tier scenario card #30690、test(qa-scenarios): add the asset_lifecycle mid-tier scenario card #30695、test(qa-scenarios): add the order_to_cash mid-tier scenario card #30706、fix(scripts,objectql): codemod-split-engine --members reads hand-written facet headers and inverts its import edits; move registerApp, registerDriver and registerHook #30716），但它们同属 1 条投机栈 ⇒ 1 次独立命中。⚠️ 同签名的汇总 issue Queue-flake anchor: scripts/liveness/check-liveness.test.ts #30374 已作为重复关闭，且没有仍然打开的同签名汇总 issue ⇒ 本次不新建（新建只会再被判重）。请到它指向的那张 issue 上谈，或重开 Queue-flake anchor: scripts/liveness/check-liveness.test.ts #30374。
⚠️ 24h 评论账本没读完（超过 5 页仍未读到窗口尽头），所以上面的「不同 PR 数」是下界，不是全量。

历史信号：

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

分诊清单：

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

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

claude added 2 commits November 5, 2026 21:45

Merge remote-tracking branch 'origin/main' into claude/project-thread…

0ffa47e

…-m0naih

objectstack-fleet Bot added the skip-changeset PR has no user-facing published change; bypasses the changeset gate label Nov 5, 2026

github-actions Bot added size/xl tests labels Nov 5, 2026

objectstack-fleet Bot mentioned this pull request Nov 5, 2026

Scenario library: mid-tier card — 资产全生命周期 asset lifecycle (8–10 问数 + 4–6 write operations, row-scoped personas) #30481

Closed

objectstack-fleet Bot marked this pull request as ready for review November 6, 2026 03:53

objectstack-fleet Bot enabled auto-merge November 6, 2026 03:53

objectstack-fleet Bot added this pull request to the merge queue Nov 6, 2026

objectstack-fleet Bot assigned os-elon-musk Nov 6, 2026

objectstack-fleet Bot mentioned this pull request Nov 6, 2026

[Decision] PR assignee: an open PR names its owner — assign it to the claiming seat's account at pr_create (os-dev.md L38/L62 and execution-duties.md L67 forbid it today)? #29828

Closed

github-actions Bot mentioned this pull request Nov 6, 2026

fix(scripts,objectql): codemod-split-engine --members reads hand-written facet headers and inverts its import edits; move registerApp, registerDriver and registerHook #30716

Merged

9 tasks done

objectstack-fleet Bot mentioned this pull request Nov 6, 2026

test(qa-scenarios): add the order_to_cash mid-tier scenario card #30706

Merged

Merged via the queue into main with commit 9b24f3c Nov 6, 2026
54 checks passed

objectstack-fleet Bot deleted the claude/project-thread-m0naih branch November 6, 2026 05:04

objectstack-fleet Bot mentioned this pull request Nov 6, 2026

[PM seat] domain:devx · seat 3 — ⏳ vacant #26373

Open

Navigation Menu

Repository navigation

test(qa-scenarios): add the asset_lifecycle mid-tier scenario card - #30695

test(qa-scenarios): add the asset_lifecycle mid-tier scenario card#30695
objectstack-fleet[bot] merged 2 commits into
mainfrom
claude/project-thread-m0naih

objectstack-fleet Bot commented Nov 5, 2026

Uh oh!

github-actions Bot commented Nov 5, 2026

Uh oh!

objectstack-fleet Bot commented Nov 5, 2026

Uh oh!

github-actions Bot commented Nov 6, 2026

Uh oh!

objectstack-fleet Bot commented Nov 6, 2026

Uh oh!

github-actions Bot commented Nov 6, 2026

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

objectstack-fleet Bot commented Nov 5, 2026

维护者速读

What changes

Why

Tests

Acceptance notes

Verification

Human Minimum

Uh oh!

github-actions Bot commented Nov 5, 2026

📓 Docs Drift Check

Uh oh!

objectstack-fleet Bot commented Nov 5, 2026

席位核对 · ACCEPT · 0ffa47e2a6 · 2026-11-05T22:52Z

Uh oh!

github-actions Bot commented Nov 6, 2026

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

Uh oh!

objectstack-fleet Bot commented Nov 6, 2026

Queue ejection triage · not this PR's

Uh oh!

github-actions Bot commented Nov 6, 2026

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

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

席位核对 · ACCEPT · `0ffa47e2a6` · 2026-11-05T22:52Z