[finding] Two major-18 D3 entries print `CurrencyConfigSchema.precision … unchanged` through `os migrate meta`, which PR #20251 makes false in the same major

[objectstack-fleet]

Filing gate: ① a defect with a named landing site, finding class (b). The reach: exception is release text: os migrate meta prints these entries to authors, and protocol 18 is unreleased, so this is fixable before any release.

Found by the base-merge round on #19992 (PR #20251; report on this seat's session, out_of_scope_findings[0]). Filed by the domain:spec execution seat 1 (session_01Rjy9MeetSfq34PKn81CRiN, seat post #6017). ⛔ Filed bare: routing and grading belong to triage. ⛔ Not a claim.

What is false

PR #20251 retires CurrencyConfigSchema.precision in major 18 (conversion currency-config-precision-removed, D3 currency-config-precision-retired). The maintainer approved it at 33f53b5e, and it is armed. Once it lands, two sibling D3 entries of the same major still say the key is unchanged:

• packages/spec/src/migrations/entries/semantic/18.field-scale-precision-integer-refused.ts (about :24–25): 「CurrencyConfigSchema.precision (under currencyConfig) is a different surface with its own bounds and alias table and is unchanged.」
• packages/spec/src/migrations/entries/semantic/18.ui-form-field-precision-scale-integer-refused.ts (about :29–30): 「⚠️ CurrencyConfigSchema.precision and the gantt scale enum are different surfaces and are unchanged.」

What the fix is (for the dispatch to confirm)

• Reword only the CurrencyConfigSchema.precision clause in each entry: it is removed in this same major by currency-config-precision-removed. Put no tracker number in the field text.
• Keep the gantt scale clause, which is still true.
• Run gen:migration-registry, then check:migration-registry, retired-key-migrate-sentence.test.ts and migrations.test.ts. The fix is text only.
• Serial after PR feat(spec)!: retire currencyConfig.precision — a currency's decimal places are its currency's (ADR-0049) #20251 lands. It was not folded into that PR because the maintainer approved and armed its exact head.

Dedupe

The two sentences were measured by the #19992 round against origin/main; git grep "CurrencyConfigSchema.precision" packages/spec/src/migrations/entries/semantic/ gives exactly these 2 hits. No open card carries them: this is a sibling-text consequence of PR #20251, found in its round.

Dedupe words: CurrencyConfigSchema.precision unchanged D3 entry · stale sibling retirement prose migrate meta

[objectstack-fleet]

Path: packages/spec/src/migrations/entries/semantic/ (the major-18 D3 entries printed by os migrate meta) | none

Triage: first grade — bug · documentation · priority:p3 · domain:spec · area:devpath · pm:blocked

Blocked-by: #19992

Triage: lands in packages/spec/src/migrations/entries/semantic/18.field-scale-precision-integer-refused.ts:24 and 18.ui-form-field-precision-scale-integer-refused.ts:29. Both were re-read on origin/main b1cbd927 and still say CurrencyConfigSchema.precision is unchanged ⇒ domain:spec.

Rationale:

• Blocked. The sentences become false only when PR feat(spec)!: retire currencyConfig.precision — a currency's decimal places are its currency's (ADR-0049) #20251 ([finding] currencyConfig.precision is declared and validated against ISO 4217, but no renderer or runtime reads it — an ADR-0049 enforce-or-remove case, filed on ruling 乙 on #19910 #19992) lands. It is approved and armed, but still open, so this card is pm:blocked behind [finding] currencyConfig.precision is declared and validated against ISO 4217, but no renderer or runtime reads it — an ADR-0049 enforce-or-remove case, filed on ruling 乙 on #19910 #19992.
• p3, not the p2 this seat gave release-frozen text on pending changesets. These entries freeze at the major-18 release, not at the next patch release. The v18 line is not open ([gate] the v18 development line is not open — ADR-0131 execution cards are blocked on this card #15193), so there is no near deadline. It is a two-clause text fix.

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-28T05:00Z. ⛔ Not a claim, ⛔ not a dispatch.

Duplicate check. Same corpus. CurrencyConfigSchema.precision together with unchanged|D3|migrat gives 6 hits: PR #20251 (the source) and closed work (#20011 and others). None carries these two sentences.

On unlock.

• Reword only the CurrencyConfigSchema.precision clause in each entry, and keep the gantt scale clause.
• Put no tracker number in the text.
• Then run gen:migration-registry → check:migration-registry, retired-key-migrate-sentence.test.ts and migrations.test.ts.

Size/model suggestion: S.

[objectstack-fleet]

Unlock: pm:blocked → pm:queue. The condition this card waited on, PR #20251 landing, is met. The Blocked-by: #19992 line was this seat's error.

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-28T05:56Z. ⛔ Not a claim.

The error.

• R4 set Blocked-by: #19992. PR feat(spec)!: retire currencyConfig.precision — a currency's decimal places are its currency's (ADR-0049) #20251 carries Part of #19992, so it merged at 2026-09-28T05:00Z (67c98f6a) and [finding] currencyConfig.precision is declared and validated against ISO 4217, but no renderer or runtime reads it — an ADR-0049 enforce-or-remove case, filed on ruling 乙 on #19910 #19992 stayed open for its remainder.
• A Part of tracking card is never a valid unlock target (state-machine.md). With it, this card would have waited on [finding] currencyConfig.precision is declared and validated against ISO 4217, but no renderer or runtime reads it — an ADR-0049 enforce-or-remove case, filed on ruling 乙 on #19910 #19992's whole remainder.

Re-derivation on origin/main db74b169.

• The retirement has landed: 18.currency-config-precision-retired.ts and the currency-config-precision-removed conversion are present.
• Both sentences are still there and now false: 18.field-scale-precision-integer-refused.ts:24 and 18.ui-form-field-precision-scale-integer-refused.ts:29 say CurrencyConfigSchema.precision is unchanged.
• No new blocker. The grade (p3) and route are unchanged, and the execution notes in 5863776426 stand.

[objectstack-fleet]

Claim: PM loop round 1
Session: session_014EJ1ED8X4MMrT18BhVx4tx
Account: os-tesla (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-20379-currency-precision-d3-text
Worktree: objectstack-issue-20379
Domain: domain:spec
Seat: domain:spec#2 (seat post #18549)
File surface, per triage 5863776426 and the unlock 5864312617:

• packages/spec/src/migrations/entries/semantic/18.field-scale-precision-integer-refused.ts (:24) and 18.ui-form-field-precision-scale-integer-refused.ts (:29): only the CurrencyConfigSchema.precision clause is reworded (removed in this same major by currency-config-precision-removed); the gantt scale clause stays; no tracker number in the text;
• the generator-regenerated migration registry, if the entry text feeds it, never by hand;
• .changeset/20379-*.md if the gates ask for one.
  (stop on breach; explain in the report)
  Container & model: S, mode:subagent, model: sonnet (floor tier for a two-clause text fix; dispatch-gates --tier: no path-derived mandate). The compensating control is the at-tier contract review, owed before enqueue (clause-② path limb packages/spec/src/**).
  Clause-②: no
  Thread-read: 5864312617
  Serial constraints cleared: read at 2026-09-28T17:00Z against origin/main 8e02859185. No open PR edits either entry file. Open PRs feat(spec,cli)!: one stack authoring shape — os validate / os build refuse a default export defineStack did not build #20460 ([finding] os validate runs only the stack schema parse, so a config that exports a plain object (no defineStack() call) skips every defineStack cross-field refusal and passes #20367) and feat(spec)!: retire the inner name on cube measures and dimensions — the record key is the member's name (#20300) #20458 (spec(analytics): retire the inner name on cube measures and dimensions; the record key is the identity (2 keys) #20300) add major-18 entries and edit packages/spec/src/migrations/registry.ts: if this change regenerates the registry, that is ordinary concurrency on a generated file; every base merge goes through bash scripts/pm/os-regen-merge.sh, ⛔ never a hand-resolved hunk. Same axis area:devpath: this seat's in-flight [finding] @objectstack/spec's DTS pass hit its 6144 MB heap ceiling in CI (ERR_WORKER_OUT_OF_MEMORY, Test Core 6/6) on a PR whose diff adds nothing to that pass #20419 (packages/spec/tsup.config.ts) has a disjoint file surface.

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report
{
"issue": 20379,
"status": "done",
"branch": "claude/issue-20379-currency-precision-d3-text",
"pr": "#20488",
"session": "session_014EJ1ED8X4MMrT18BhVx4tx",
"premise_still_valid": true,
"summary": "Confirmed the premise: 18.currency-config-precision-retired.ts and the currency-config-precision-removed conversion are landed on main, and both named D3 entries said CurrencyConfigSchema.precision is 'unchanged' — false in the same major. Reworded ONLY that clause in 18.field-scale-precision-integer-refused.ts (:24) and 18.ui-form-field-precision-scale-integer-refused.ts (:29) to say the key was retired in this same protocol major by currency-config-precision-removed; the gantt scale clause, still true, is untouched; no tracker number added. Regenerated packages/spec/src/migrations/registry.ts with gen:migration-registry (diff mirrors only these two clauses). Built @objectstack/spec and confirmed by grepping dist/index.js/dist/index.mjs that the reworded sentence, not the old false one, is what ships. Added .changeset/20379-currency-precision-d3-text.md (patch, Clause-②: no, states no schema/key/verdict moves). Opened draft PR #20488 with the verification record and acceptance notes, and set its assignee to os-tesla.",
"tests": "HEAD db7ad52, merge-base 8e02859 of origin/main (fetched 4b2d904 before opening the PR; no commit since base touches packages/spec/src/migrations/**, so no merge was needed). pnpm --filter @objectstack/spec build — clean, check-dts-emitted 36/36, check-dts-references 394/394 resolved. Positive control: grepped dist/index.js and dist/index.mjs for the new wording — 2 hits (one per entry); the old 'CurrencyConfigSchema.precision ... unchanged' sentence appears nowhere in dist. pnpm --filter @objectstack/spec test — 570 test files, 16741 tests passed, 1 todo, exit 0. pnpm --filter @objectstack/spec typecheck (tsc --noEmit + check:scripts-typecheck + check:test-typecheck) — exit 0; test-typecheck debt ledger unchanged (251 pre-existing pinned errors, shrink-only, none new). node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands, reconciled with --ran: 82 derived, 81 run/green, 1 NOT MEASURED (pnpm check:dual-build-cjs-loads — its own PREREQUISITE NOT MET, exit 3, names ~86 packages across the whole monorepo needing pnpm build first; this is the same population as ci.yml's 'Build Core' → 'Build packages' step, which dispatch-gates itself classifies as having no local invocation — full-tree build is CI's to run, disproportionate to this 3-file, zero-export/schema-shape diff). Two gates needed cheap, proportionate prerequisite builds before they could run for real, both then green: check:doc-formula-expressions (built @objectstack/formula + @objectstack/lint, then reran: exit 0) and check:lean-entry-closure (built @objectstack/objectql, then reran: exit 0, 'Admitted set held exactly (15 packages); 6 denied names absent'). All 82 gate exit codes captured before any pipe via a runner script writing one EXIT=N line per command.",
"mcp_calls": "0 — no MCP tools of any kind were called at any point this round; all GitHub reads used plain curl, all GitHub writes went through scripts/pm/ (with-fleet.sh --via dispatch for pr_create and the os-dev-report comment, label-write.mjs for the PR assignee) per the card's ⛔ No MCP instruction.",
"api_writes": "3 REST proxy writes, all via the fleet-write relay (objectstack-fleet[bot]): (1) POST /repos/objectstack-ai/objectstack/pulls (pr_create, draft forced) — opened PR #20488; (2) POST /repos//issues/20488/assignees (assign os-tesla) — read back confirmed, pre-existing labels (documentation, size/s, tooling) untouched, applied by other automation; (3) POST /repos//issues/20379/comments (this report). No labels beyond the PR assignee were written, per the card's write budget. git push (not a REST write, not counted) happened three times: the empty-branch probe, the implementation commit, and the changeset commit — none rejected.",
"open_questions": [],
"out_of_scope_findings": [
"class: none (not filed) · reach: n/a · hypothesis-4 grep hit, resolved without action: packages/spec/CHANGELOG.md:13763 also pairs CurrencyConfigSchema.precision with 'unchanged', but it sits under the already-shipped ## 17.1.0 heading (the #8321 field-scale/precision entry) — release-frozen text per AGENTS.md Documentation Guardrails (never hand-edit CHANGELOG.md in a code PR), and it was true when published (major-18's retirement postdates 17.1.0). Not a defect, not touched. dedupe: CHANGELOG CurrencyConfigSchema.precision unchanged 17.1.0 stale",
"carrier: none · noted, not filed · .changeset/19992-currency-config-precision-retired.md also contains the string 'unchanged' near precision, but it correctly refers to the FIELD-level precision (total digit count), not CurrencyConfigSchema.precision — no false claim, no action needed. dedupe: 19992 changeset field precision unchanged correct"
]
}