[objectstack-fleet]

Requested by Leehom · project thread

domain:devx#4 · os-project-manager · session_01FEkQ5kWURVLmS49GR3jwxs

Part of #33351 (section A only; this PR lands the two rows that are fixture additions on main today. Section B and the rows listed below as owed, decided or out of scope stay on the card.)

Clause-②: no
Metadata-protocol: none

维护者速读

• 改了什么:示例应用 showcase 给三张外币发票(INV-1007 日元、INV-1009 和 INV-1010 欧元)各补一行发票明细;18.0 预发布数据库的恢复脚本在恢复时把活动日志分片改成“昨天”的日期。
• 为什么改:多币种测试项原先只有两张外币发票金额非零,其余三张只能看到汇率选择、看不到换算;恢复出来的活动日志分片日期停在 10 月 27 日,首次启动就被 7 天保留策略删掉,测试项读不到那 66 行。
• 风险与回滚:只动示例应用种子数据和测试夹具脚本,都不发布(两个包都是 private);回滚即 revert 本 PR。
• 先看:examples/app-showcase/src/data/seed/index.ts 新增的三行发票明细;packages/qa/dogfood/test/upgrade-harness/cli-prerelease-fixture.ts 的 restore。
• 两分钟验证:pnpm --filter @objectstack/dogfood exec tsx test/upgrade-harness/cli-prerelease-fixture.ts restore --to /tmp/x/n5.db,预期多打印一行 re-dated shard sys_activity__r20261027 → sys_activity__r<昨天>。
• 需要你做的:无,席位落地。卡上另有三个待决问题(第 92、135、263 行,以及 90+153 合并的一问),见下文与报告评论。

What changes

Two files, fixture space only.

1. Row 220 · records-forms.multi-currency-invoice (examples/app-showcase/src/data/seed/index.ts): one invoice line each under INV-1007 (JPY), INV-1009 (EUR) and INV-1010 (EUR), so all five foreign invoices carry a non-zero total and both rate rows of each currency are exercised. Measured on a stock boot of this head (a throwaway probe, deleted after the run):

   INV-1004 EUR amount=450    home=500     rate=0.9
   INV-1007 JPY amount=95400  home=629.7   rate=151.5
   INV-1008 JPY amount=237864 home=1593.73 rate=149.25
   INV-1009 EUR amount=2016   home=2191.3  rate=0.92
   INV-1010 EUR amount=276    home=300     rate=0.92
   

   Before this PR, INV-1007, INV-1009 and INV-1010 had no lines (amount 0), as the QA record measured.

2. Row 209 · cli-18-prerelease-db restore (packages/qa/dogfood/test/upgrade-harness/cli-prerelease-fixture.ts): restore now passes both dumps through the harness's own fixture-as-of.ts (shardRenamesAsOf + renameShardTables), so the restored telemetry sibling's sys_activity shard is dated the day before the run and the first boot's rotation retention keeps it. It prints each rename. Measured: at base d3f3f4ab the restore writes sys_activity__r20261027; at this head it writes sys_activity__r20261113 (66 rows) on 2026-11-14. Neither manifest.json nor the recipe names the shard, so no census read changes.

Per-row dispositions (all 16 section A rows, re-measured on origin/main d3f3f4ab)

row	disposition	evidence
80	already done on main	packages/services/service-storage/src/attachment-member-grant.ts contributes read + create on sys_attachment to every member's baseline since fd6374713 (2026-11-13 07:58Z); the QA run was at ee9ad834 (03:17Z), which does not contain it (merge-base --is-ancestor fd6374713 ee9ad834 exit 1; fd6374713 in HEAD exit 0; control ee9ad834 in HEAD exit 0)
89	out of scope (product)	app packages cannot author settings namespaces (spec migration 18.translation-per-app-settings-platform-only), and no built-in manifest declares scope: 'user' (packages/services/service-settings/src/manifests/*.ts). A user-scope secret is a platform manifest change, not a fixture
90	needs_decision (with 153)	the item needs one item name held by two installed packages; no stock boot carries a second package, and the showcase is one app package
91	already runnable; item text owed	identity-auth.self-signup-gate knownGaps[0] records the env door (OS_AUTH_AUDIENCE_POSTURE, OS_AUTH_AUDIENCE_ALLOWED_EMAIL_DOMAINS, OS_AUTH_AUDIENCE_SELF_REGISTRATION_PERMISSION_SET) measured live; variants[1]/[2] still say blocked(fixture). identity-auth.json is held by batch A PR #33362, so the re-point is owed there
92	premise does not hold; not changed; needs_decision	showcase_task.assignee is Field.text and the showcase stores an EMAIL in it on purpose: the seed writes persona emails (seed/index.ts "#7746" block), the notify flows read it as a recipient, invoice.owner and private_note.owner follow the same email convention, and search.json / records-forms.json tell runners to assign by email. The QA run had PATCHed a user id into it by hand (record 6846028996: "the run had set assignee to a user id"). Switching the rule to ids would hide every seeded task from its assignee
135	needs_decision	Ada holding showcase_finance or showcase_legal also makes her a required approver of the seeded invoice dual sign-off (showcase_invoice_signoff, unanimous over finance + legal, flows/index.ts), so the stock demo changes beyond the quorum item
151	out of scope (product)	mandatoryTopics is reachable only as a MessagingServicePlugin constructor option (packages/services/service-messaging/src/messaging-service-plugin.ts); a declarative door is product work. Carrier: #33352
152	environment-bound	the agent catalog is served only by the Cloud/Enterprise @objectstack/service-ai; platform-core.keyboard-shortcut-surface knownGaps[1] already scores that half blocked(environment). Belongs with section B
153	needs_decision (with 90)	measured: a second app (active: false) in the showcase is refused at build, "An 'app' package must define at most one app" (defineStack single-app validation, ADR-0019). The fixture needs a module package composed beside the showcase. Tried in d2faa4b58, withdrawn in the next commit
155	recipe text owed	the flow is runner-built from studio-authoring.flow-edge-type-authoring fixtures.requires[1] ("Start → Decision → two End nodes"); adding a loop is text in studio-authoring.json, held by batch B PR #33360
208	held	scripts/qa/qa-fixture.mjs walled-boot is held by #33334
209	landed here	see What changes 2. The recipe text in cli.json is routed to batch D (#33330)
218	out of scope (product)	stamping environment rows with a host package is hosted-runtime behaviour, not seed data. Carrier: #33352
220	landed here	see What changes 1. The item text ("only INV-1004 and INV-1008") lives in records-forms.json, held by batch B PR #33360
227	recipe text owed	there is no committed 18.3.0 fixture: the file is runner-built (platform-core.activation-ledger-package-key-upgrade route (a)/(b)). Planting a connector instance and an assignment rule is recipe text in platform-core.json / cli.json, held by batch D (#33330)
263	needs_decision	records-forms.gantt-interactions: the stock task gantt view declares no lockField / dependenciesField; either the showcase task gains them (plus a dependency field and seed), or the item keeps the documented overlay route and narrows

Totals: 16 rows · 2 landed here (209, 220) · 2 already right (80, 91) · 4 needs_decision questions over 5 rows (92; 135; 90+153; 263) · 3 owed as recipe or item text in held area files (155, 227, plus the 91 and 220 text) · 1 held by #33334 (208) · 3 out of scope as product (89, 151, 218) · 1 environment-bound (152).

No packages/** outside packages/qa, no new door, no area file (every one this card would touch is held by an open batch PR or card: #33362, #33360, #33359, #33327, #33330), no RUNNER.md.

Why

The v18.4.0 sweep parked 22 fixture rows (#32908 ledger /mnt/project-files/pm-orders/devx/32908-ledger.md, routed to #33351 by triage). Section A is the 16 rows that looked like seed or fixture additions. Each was re-measured on main here first; two are fixture additions that hold today and land in this PR, and the rest are answered row by row in the table above. Source records: #32908 comments 6844741021, 6846028996, 6846283471, 6850382730, 6850413952, 6850460138, 6850495479 and 6852480973.

Tests

showcase suite + typecheck, dogfood typecheck (head 2b2bca1)

pnpm --filter @objectstack/example-showcase test       Test Files 48 passed (48) · Tests 545 passed (545)
pnpm --filter @objectstack/example-showcase typecheck  exit 0
pnpm --filter @objectstack/dogfood typecheck           exit 0
os-verify-lock: VERDICT command-exit 0

dogfood suites that boot the showcase and read invoice lines

pnpm --filter @objectstack/dogfood exec vitest run --maxWorkers=2 \
  test/showcase-invoice-seed-isolation.dogfood.test.ts test/showcase-invoice-cbp.dogfood.test.ts \
  test/showcase-invoice-line-contributor-pair.dogfood.test.ts test/showcase-readonly-when-parent.dogfood.test.ts \
  test/showcase-crud-persona-matrix.dogfood.test.ts test/master-detail-batch-atomic.dogfood.test.ts \
  test/home-amount-projection.test.ts test/upgrade-harness-fixture-as-of.test.ts test/external-member-directory.dogfood.test.ts
Test Files 9 passed (9) · Tests 153 passed | 15 skipped (168)
os-verify-lock: VERDICT command-exit 0

No ablation: the diff adds seed rows and changes a fixture script, and pins no new tested behaviour.

Acceptance notes

• Rows 90 and 153 want the same thing: a second package on the stock boot (one holding a name the showcase also holds; one carrying a switched-off app). One module package composed beside the showcase would serve both; that is a choice about the example's shape, so it is a question on the card, not a change here.
• Row 92's ruling rested on "assignee stores a user id". On main it stores an email by the showcase's own convention, so the rule was left as it is and the question goes back on the card.

Verification

Local subset at head 2b2bca197, derived by node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack (73 changed lines at derivation; 33 after the withdrawn app, same path families):

• dispatch-gates --ran: 54 derived, 53 run with exit 0, 1 NOT MEASURED: pnpm check:dual-build-cjs-loads exit 3 PREREQUISITE NOT MET (reads every package's dist; studio, client-react, scenarios and others are unbuilt here). The diff changes no published package's build output; CI's Build Core runs it.
• check-plugin-teardown-shape.mjs --self-test first answered exit 3 on the shallow clone (pinned control 621a4876 unreachable); after git fetch --depth=1 of that commit it answered exit 0, 48 cases.
• pnpm exec eslint --no-inline-config on both touched files: exit 0.
• Changeset: none. @objectstack/example-showcase and @objectstack/dogfood are both "private": true, so nothing publishes (skip-changeset).
• CI families (Test Core, lint farm, type-check lanes) are read off this PR's check runs by the seat.

Full record: /mnt/project-files/pm-orders/devx/33351-gates-ran.txt.

Human Minimum

• 1. Schemas start as Zod; packages/spec holds no runtime logic. (not touched)
• 2. Every name I added uses the casing for its kind. (no names added)
• 3. No formatter ran; pnpm lint passes. (eslint on both touched files: exit 0)
• 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: both packages are private, skip-changeset)
• 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 维护者速读 block is the seat's required Chinese summary)
• The Before Submitting list in CONTRIBUTING.md is done.

---

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 6538ba48fc4590402cd6280cf83a8902f6de83d3 → packageMentionDocs.

[objectstack-fleet]

domain:devx#4 · os-project-manager · session_01FEkQ5ooRyyS95kdyC2dPEX

席位核对 · ACCEPT · head 2b2bca19 · 2026-11-14T18:22Z

• 形态: draft → main, attribution first, Part of #33351 (section A only; this PR lands the two rows that are fixture additions on main today. Section B and the rows listed below as owed, decided or out of scope stay on the card.). Paths from the PR's file list: examples/app-showcase/src/data/seed/index.ts (+8/-0), packages/qa/dogfood/test/upgrade-harness/cli-prerelease-fixture.ts (+25/-3). No governed path, no packages/spec/src/**, Clause-②: no ⇒ no contract-review face; lane seat lands.
• Diff read: Section A rows 220 and 209 only. seed/index.ts: one invoice line each under INV-1007 (JPY), INV-1009 and INV-1010 (EUR), so all five foreign invoices carry a non-zero total (the dev's stock-boot probe read 95400 / 2016 / 276). cli-prerelease-fixture.ts: restore re-dates the dump's rotation shards through the existing shardRenamesAsOf / renameShardTables exports of fixture-as-of.ts (both present on origin/main, L73/L99) before loading, and logs each rename. Seat check: governedPathsIn returns none; showcase tests 545/545 and the 9 invoice/upgrade dogfood suites the dev ran are green; check:dual-build-cjs-loads was not measured locally and CI Build Core is green.
• 门禁 check-runs (head 2b2bca19): 55 runs · 34 success · 21 skipped · 0 not green; Lint & Repo Gates success, TypeScript Type Check success. K = 10 merges behind main (< 15).
• Changeset: skip-changeset holds: the touched paths ship in no package.
• 接受的偏差: Part of #33351, not Fixes: the card's other section-A rows are owed text in area files, product, or held for a ruling, and section B follows.
• 范围外去向: four section-A rows await a maintainer ruling (anchor 6881987608 on qa fixtures: 22 seed and environment gaps that block checklist rows (v18.4.0 sweep) #33351); owed item text for rows 91, 155, 220 and 227 rides qa fixtures: 22 seed and environment gaps that block checklist rows (v18.4.0 sweep) #33351's follow-up once the area-file batches land; 151/218 → test doors: 8 product arms that no door reaches (v18.4.0 sweep): add a door or pin as unit-only #33352; 208 → qa runner kit: write the v18.4.0 sweep's 12 environment facts into RUNNER.md and fix two qa-fixture.mjs gaps (walled-boot flags, contributor-member --position) #33334. Skills-docs: not owed (Metadata-protocol: none).
• 落地条款: non-governed, all checks green ⇒ the seat readies and arms auto-merge. Ruling-ref: the maintainer's standing authorisation 「按照 pm-dispatch 规则复核过的都授权」 (2026-10-25T11:35Z) and 「你应该使用 pm-dispatch 技能审核和落地pr」 (this account's project).