[objectstack-fleet]

Requested by Sam · project thread
Fixes #27114

Clause-②: no
Metadata-protocol: none

维护者速读

• 改了什么:在 json-stdout-purity.e2e.test.ts 的 FAMILY 里补上 migrate record-currency-codes 及其驱动参数,仅此一个测试文件。
• 为什么改:feat(objectql,cli,metadata-protocol): backfill the currency code of rows stored before an amount switched to record mode, and acknowledge the switch with a 409 at the save #28128 新增的命令带 --json 且启动内核,被 discoverFamily() 自动发现(26 个),而 FAMILY 只列 25 个,夜间 tier 因此变红。
• 风险与回滚:只改测试,不发布任何包;回滚即 revert 这一个文件。
• 先看:packages/cli/test/json-stdout-purity.e2e.test.ts 新增的那一条 FAMILY 及其注释。
• 两分钟验证:cd packages/cli && OS_TEST_TIERS=nightly pnpm exec vitest run --project integration test/json-stdout-purity.e2e.test.ts,预期 80/80 通过(约 6 分钟)。
• 需要你做的:无,席位落地。

What changes

migrate record-currency-codes joins FAMILY with argv --object jp_ticket --field title --code USD. All three flags are required, so without them the run stops at flag parsing and never boots. It runs as a dry run (the default), which boots read-only and writes nothing. discoverFamily() is unchanged and no case is skipped.

The face it reaches was measured, not assumed: on this deliberately uncompiled fixture the command answers its "No app objects are loaded" refusal after the boot, as one compact JSON document on stdout (exit 1), with the boot diagnostics (no compiled artifact, Bootstrap complete, Graceful shutdown complete) on stderr. The comment beside the entry names that face. No PREPARE entry was needed.

Tests

Nightly integration tier, local, under the verify lock, tree at merge base 22ce3d13 with the cli dependency closure built.

• Red (test file restored from origin/main at a0f86549, which is byte-identical to 22ce3d13 for this file): Tests 1 failed | 76 passed (77). The one failure is the reconciliation pin, and the received-vs-expected diff is exactly + "migrate record-currency-codes". That confirms 26 vs 25 and that no other member is missing.
• Green (with the entry, commit a8c47a44): Test Files 1 passed (1), Tests 80 passed (80). The second commit 1bdda92a changes only the comment beside the entry.

Acceptance notes

• Skip-changeset: the diff is one test file, which no package ships.
• This file runs only in the nightly tier (OS_TEST_TIERS=nightly), so PR CI does not exercise it. The next nightly on main is its real verdict.

Verification

Derived gate families (node scripts/pm/dispatch-gates.mjs --commands, 48 commands) were run locally. 45 exited 0. --ran reconciliation: 48 derived, 46 run, 2 not measured.

• check:dual-build-cjs-loads and check-plugin-teardown-shape --self-test exited 3 (prerequisite not met: full dist missing, and a shallow clone).
• check:dts-closure exited 1 only because the local closure was built with OS_SKIP_DTS=1. Its self-test passed.

None of these three reads a test file, and CI runs all three.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 0 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 02d6507275eaa7d821e98585df9bb31eed8dedca → packageMentionDocs.

[objectstack-fleet]

domain:devx#1 · os-zhuang · session_01QUs3BvP5Aq9USg5GtmgAAR

席位核对 — ACCEPT · domain:devx#1 · head 1bdda92a6c509aab0fd8db69a7c6a1821ca8e94b · 2026-10-31T07:22Z

Checked against GitHub and origin/main, not against the report (os-dev-report 6540560399 on #27114).

• Shape: draft → main, Fixes #27114, no other closing keyword, no assignees or reviewers. skip-changeset correct: test file only, nothing published.
• Path surface (/pulls/28375/files): packages/cli/test/json-stdout-purity.e2e.test.ts only, +11/−0: one FAMILY entry plus its comment. discoverFamily() is untouched and no case is skipped, as the stop-bleed required (6540032843). check-governed-merges: NOT governed.
• Drive verified on main (packages/cli/src/commands/migrate/record-currency-codes.ts): --object, --field, --code are each required: true; a dry run passes deferSchemaDdl: true, readOnlyProbe: true; the "No app objects are loaded" refusal is emitted { compact: true } and then this.exit(1), so the entry's comment describes the face it drives accurately.
• Red/green: the dev reports red at main's file (1 failed / 76 passed) and green with the entry (80/80, nightly tier). This tier does not run on PR push, so the nightly run after landing is the confirming reading; the seat checks the card's next Swept line.
• Accepted deviations: worked in the platform checkout rather than a separate worktree. Three gates were environment-only in the dev's container (shallow clone, DTS-skipped build): 2 NOT-MEASURED, left to CI.
• Landing: non-governed; seat landing authorised by the maintainer (2026-10-31T06:58Z); lands once every check on this head is green.