fix(spec)!: refuse scale on a currency inline grid column; prefix promises no default symbol (#20045)

[objectstack-fleet]

Fixes #20045
Clause-②: no (narrowing)

Clause-②: no (narrowing) per the seat's ruling 5855671317 on #20045: this diff widens nothing and only refuses a shape that parsed; the claim's yes is corrected there.

Branch claude/issue-20045-inline-currency-column-scale, base 1c8b320a89. It is merged with origin/main twice through scripts/pm/os-regen-merge.sh: first b09ce67870 as 4a6e8ed61a, then, in rework round 1, 805af4f290 as 9f01270dd2. The regeneration is its own commit, df6b175e58. Head is 4ab1d0cac2. Every reading below was taken at head 4ab1d0cac2 unless it names another commit.

What changes

Triage direction: comment 5825687357, option A. Triage read the card as inherited from ruling B 5791803339 on #19629 (scale retired from the currency field) and ruling 乙 5805782503 on #19910 (「a currency's ISO 4217 minor unit decides its display」).

1. InlineGridColumnSchema (packages/spec/src/data/field.zod.ts) now refuses an authored scale on a column that declares type: 'currency'. The refusal is one custom issue at the column's scale, and it applies to any value, scale: 0 included, computed or not. The message carries ruling B's shape:
   • first sentence: "scale is not valid on a currency inline grid column — delete the key." This is the field refusal's first sentence with only the subject swapped;
   • remedy: the currency's ISO 4217 minor unit (2 for USD, 0 for JPY, 3 for KWD) decides how the cell displays the amount and the width a computed amount is rounded to. It names no other key.
   • No alias and no grace window.
   • scale on a number column, and on a column that declares no type, is unchanged.
2. The prefix describe no longer says 「(default '¥')」. It now reads: the symbol replaces the resolved currency's own symbol; there is no default; it replaces the symbol only. prefix is still accepted. The scale describe drops "numeric/currency" and names the currency refusal.
3. ADR-0087: the D3 semantic entry 18.inline-grid-column-currency-scale-refused is added, and registry.ts was regenerated with gen:migration-registry.
4. The changeset makes @objectstack/spec minor, with a BREAKING banner, a FROM → TO table and the registered disposition marker.
5. dropped-refinements.baseline.json gains the new refinement's rows, exactly as the build's ratchet printed them: data/InlineGridColumn (root) plus one …inlineColumns.element site on each of the 12 published schemas that embed the column. The header totals moved with the body: 208 schemas, 590 sites after the merge.
6. content/docs/references/data/field.mdx was regenerated (check:generated --fix, which proved only check:docs stale).

ADR-0087 disposition: why D3 only

• A D3 entry is owed. Ruling B on [Decision] 一次退役，要写一条记录还是两条？—— 迁移条目的 D2/D3 约定，两处成文相互矛盾 #17152 (5615360777, restated 5634031140) says 「D3 每家族一条,D2 可无损表达者亦然;D2 只承载数据修复」.
• No D2 conversion. The card inherits ruling B on [finding] FieldSchema.scale on a currency field is offered to authors by the field designer, ignored by every display face, and still enforced on writes — half-live in the direction that surprises #19629, which says no alias and no grace window. Its own entry, field-currency-scale-refused, is "NOT mechanically converted, deliberately". A load-path conversion that dropped the key would accept it on every load, which is the grace window the ruling refused. This entry follows that precedent.
• No retired-keys/ row. The key is not removed. It stays in the walked shape and stays live on number columns, and a RETIRED_KEYS_BY_MAJOR row naming a live key reds gate (b2).

Premise, measured

• On 1c8b320a89, InlineGridColumnSchema was a bare strictObject with no refinement, and scale was declared for a "computed numeric/currency result".
• The ablation below is the executable half of that reading. With the new refinement short-circuited, all six refusal pins go red, because every currency-plus-scale shape parses again.
• The objectui side was read by content:
  • at objectui origin/main 25c7d58, GridField.tsx has function currencyAdornment ×1 and function currencyWidth ×1, and c.prefix || '¥' ×0;
  • at this repo's .objectui-sha pin f8a9d0fb0596, it has c.prefix || '¥' ×2 and the currency ? 2 default ×1 (see Acceptance notes).

Mechanism hypothesis H1, measured

• InlineGridColumnSchema was at :895, a strictObject, with prefix at :924 and scale at :938. Confirmed.
• "Reuse the refusal sentence or the shared helper" was partly falsified. No helper exists: ruling B's sentence is a string literal inside FieldSchema's superRefine (:2295–2307 on base). That block is outside this claim's file surface. So the column carries the sentence and remedy in its own constant, INLINE_GRID_CURRENCY_SCALE_REFUSAL.
• A parity pin keeps the two refusals from drifting apart. It reads both refusals and asserts that the first sentences match (subject swapped), that both carry the same minor-unit clause, and that neither names currencyConfig or precision.
• FieldSchema's currency-precision anchor was not touched. It changed on main during this run (finding(spec): the #7918 anchor reads a currency field's precision as its display width, refusing precision: 18 on a fixed-USD field though the key is "Total digits" and ruling 乙 gives decimals to the currency #20011, PR fix(spec): a currency field's precision is total digits — stop refusing precision: 18 on a fixed-USD field (#20011) #20209). It merged cleanly and is disjoint from this diff.

Authored instances (H2), census on 1c8b320a89

• git grep inlineColumns over the whole tree gives 30 files. Exactly one authored block: examples/app-showcase/src/data/objects/invoice.object.ts, with 7 identity-only { name } columns, 0 declaring type and 0 declaring scale. This is the control: the same instrument counts 7 column entries in that block.
• Platform objects, skills/**, content/docs/** prose and examples, and JSON/YAML fixtures: 0 inline grid columns.
• Objectui at the pin: 0 authored inlineColumns fixtures. Its only hits are the two renderer files.
• Test fixtures: 1 carried scale: 2 on a currency column (inline-related-columns.test.ts, the "every renderer-read key" case). It was re-judged: scale was deleted there, and the key stays covered by the identity-only computed amount column in the same fixture.
• Deployed metadata: NOT MEASURED, because no instrument reaches it.

Tests, at head 4ab1d0cac2

All heavy runs went through scripts/pm/os-verify-lock.sh under one stable slot, and each verdict below is read from its VERDICT line.

• @objectstack/spec build: exit 0.
• check:generated: "All 15 generated artifacts are up to date", including ✓ check:migration-registry.
• registry.ts was regenerated with gen:migration-registry from the merged entries/ directory. The output is byte-identical to the merge. Quoted-exact git grep -c -F on 4ab1d0cac2, 1 hit each:
  • 'inline-grid-column-currency-scale-refused' (this PR);
  • 'dataset-filter-nested-relation-equality-array-refused-at-save' (fix(spec)!: a dataset or measure filter with a list inside a nested relation is refused on save (#20080) #20207), plus two of fix(spec)!: a dataset or measure filter with a list inside a nested relation is refused on save (#20080) #20207's rewritten sibling-entry lines;
  • 'view-overlay-options-bag-judged' (fix(spec)!: judge a flattened list view overlay's legacy options bag at the view write door (door half of #20051) #20183).
• check-adr-0087-registration --base origin/main: exit 0, "1 declared-breaking changeset(s), each carrying an ADR-0087 disposition … [BREAKING+bang+clause-②-narrowing] registered inline-grid-column-currency-scale-refused".
• check-changeset-no-major --base origin/main --event with THIS body: exit 0, "✓ LEVEL AXIS: this PR declares clause-② no (narrowing)".
• Targeted, the 5 files (the new file, inline-related-columns, field-currency-scale-refused, validation-boundary-description, authoring-key-lint): 5 files / 71 passed.
• spec vitest --project local: 545 files passed; 16045 passed, 2 todo.
• spec vitest --project repo: 32 files / 586 passed.
• spec typecheck: exit 0 (check:test-typecheck: OK — 53 file(s) / 255 error(s) / 142 pinned signature(s) held).
• The new file inline-grid-column-currency-scale-refused.test.ts covers:
  • refusal through FieldSchema, ObjectSchema and the standalone column, located at …inlineColumns[i].scale, with code: 'custom';
  • every value, computed or not;
  • controls: a number column, an untyped column, prefix accepted, and the remedy parsing and re-parsing unchanged;
  • field/column shape parity;
  • the two describes;
  • the D3 entry being registered.

Ablation, from committed state aa4b6ca14f, run with scripts/ablation-replace.mjs:

• The anchor if (column.type === 'currency' && column.scale !== undefined) { was hit ×1 and went ×1 → ×0. The replacement if (false && … went ×0 → ×1. The blob changed from 147220988d04 to ddf1ebbf0437.
• Result: 6 failed | 22 passed (28). All six refusal/parity pins went red, and the controls stayed green, which is the expected direction.
• Restore: blob 147220988d04 == HEAD, and git diff HEAD is empty.
• The subject is imported from src (./field.zod), so no dist rebuild was involved.

Gates. dispatch-gates.mjs --commands was re-derived on 4ab1d0cac2 and gave 111 families, the same list as on 4a6e8ed61a. All 111 were re-run on 4ab1d0cac2. --ran reconciliation: "111 derived famil(ies) accounted for — 109 run, 2 NOT-MEASURED".

• NOT MEASURED: check:dual-build-cjs-loads, reason: PREREQUISITE NOT MET. Packages have no dist/, and only a full-repo build satisfies that. This diff changes no entry point, export map or build config.
• NOT MEASURED: check:type-check-debt, reason: PREREQUISITE NOT MET (@objectstack/driver-turso has no built type entry point in this worktree). Its --re-measure otherwise starts a workspace-closure build outside the verify lock. This diff changes no exported type (check:api-surface is green) and touches none of the four DEBT-ledgered packages.

Rework round 1, diff 4a6e8ed61a → 4ab1d0cac2 (107 files, +6088/−682):

• From main (b09ce67870 → 805af4f290):
  • 102 files are byte-identical to 805af4f290;
  • in the 4 files this branch also touches, the change set equals main's own line for line (field.zod.ts 2 lines, registry.ts 224, field.mdx 4, dropped-refinements.baseline.json main's rows).
• Regenerated:
  • registry.ts, by gen:migration-registry, byte-identical to the merge;
  • field.mdx, by gen:schema && gen:docs (df6b175e58). The os-regen driver had kept the branch side and dropped main's two defaultCurrency rows, and the regeneration restores them;
  • the ledger header totals, recounted from the merged body: 588 → 601 sites, 208 schemas.
• Anything else: exactly one line, the changeset's Clause-②: yes (narrowing) → Clause-②: no (narrowing). The PR body's Clause-② line moved in this same edit.

Deviations

• File surface. packages/spec/dropped-refinements.baseline.json is outside the claim's listed surface. The build refuses a new refinement without it. The file is hand-edited on purpose and has no generator, and its rows were applied exactly as the gate printed them, including the merge-time header recount. The claim's surface names "its own refinement", so this is reported as that refinement's mechanical consequence, ⛔ not as scope growth.
• Merges. Both merges conflicted only on the ledger's header totals: fix(spec)!: refuse an array under $ne at the shared comparand-shape face and at FieldOperatorsSchema.$ne #20204 in the first, and fix(spec)!: a dataset or measure filter with a list inside a nested relation is refused on save (#20080) #20207 in rework round 1. Each was resolved by keeping both sides' rows and recounting the merged body.

Acceptance notes

• Reach of the refusal. Only a DECLARED column type is judged. A column that declares no type gets its type from the child field when objectui hydrates it (deriveMasterDetail.ts hydrateColumns, which spreads the authored column). So { name: 'amount', scale: 2 } over a currency child field still parses. The column schema cannot see the child object. Once the objectui follow-up stops reading an authored scale on currency columns, that key is ignored on such a column. That lands on the objectui follow-up card (triage note 4), not here.
• Pinned console vs this describe. The new prefix describe ("No default") is true of objectui main (25c7d58). The console bundled at .objectui-sha f8a9d0fb0596 still falls back to ¥ and rounds a computed currency with no scale to 2. The describe becomes true of the bundled console when the pin moves past objectui PR objectstack init scaffolds a project whose pnpm install exits 1 on pnpm 11 — its rendered pnpm-workspace.yaml omits allowBuilds #10405. Deleting scale loses no decimals under either console: the pin falls back to 2, and main to the ISO minor unit. So no zero-decimal window opens.
• Stale notes outside this surface, recorded only (carrier: none):
  • packages/spec/liveness/field.json → inlineColumns.children.prefix / .scale notes still cite c.prefix || '¥' and c.scale ?? currency default 2;
  • the packages/spec/src/data/field-scale.ts docblock sentence "The one 2 that looks like a currency default belongs to an inline grid COLUMN's rounding" describes the pre-objectui#10355 grid.
• The objectui GridField follow-up (drop the authored-scale read on currency columns) is objectui's own card, per triage note 4. Nothing in objectui changes here.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

3 anchor(s) derived from 1 changed package(s); no hand-written page names any of them. ⚠️ 1 changed file(s) yielded no anchor (packages/spec/dropped-refinements.baseline.json), so the pages documenting them are NOT COVERED by this run — this is not a clean bill of health for those files.

What this run could not see

• 1 changed file(s) yielded no anchor (packages/spec/dropped-refinements.baseline.json) — pages documenting those are invisible to this run
• 4 name(s) were too generic to anchor anything (single lowercase words)
• the SDK route bridge reached 54 of 206 client-bound route-ledger rows — the other 152 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 152: 0 are remediable by widening that discovery convention (an in-repo file declares the path; the convention did not scan it); 55 are structural — on a ledger where NOT ONE row is declared in-repo, so no discovery change reaches them at any price; 97 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.
• 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 — 136 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 805af4f290565955d6e6b56ee46fed45f721d955 → packageMentionDocs.

Which tree this was computed on

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

node scripts/docs-audit/affected-docs.mjs --json 805af4f290565955d6e6b56ee46fed45f721d955

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

[objectstack-fleet]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 4ab1d0cac243ff74c4ec7951e3471c718974fb55

① Derived judgments

Diff read three-dot against objectstack origin/main 66e266c931 (merge-base 805af4f290): 8 files, +388 / −10 — the changeset, content/docs/references/data/field.mdx, packages/spec/dropped-refinements.baseline.json, packages/spec/src/data/field.zod.ts, the new pin inline-grid-column-currency-scale-refused.test.ts, one fixture line in inline-related-columns.test.ts, the D3 entry 18.inline-grid-column-currency-scale-refused.ts and its registry.ts row.

1. One accept-set change, a narrowing, exactly as declared. InlineGridColumnSchema gains a .superRefine that adds one custom issue at path: ['scale'] when column.type === 'currency' && column.scale !== undefined. Nothing else in the strict object moves: scale's own rule (int().nonnegative().max(MAX_RENDERABLE_SCALE)) and prefix: z.string().optional() are unchanged. The condition reads only the DECLARED type, so an identity-only column, whose type the console derives from the child field at hydration, keeps parsing; the docblock, the changeset and the D3 entry all say so under "Reach". scale has no schema default, so undefined always means "not authored" and parse(parse(x)) is stable; the pin's remedy test asserts the re-parse.
2. The message is the field refusal carried, not reworded. INLINE_GRID_CURRENCY_SCALE_REFUSAL opens with FieldSchema's currency refusal (field.zod.ts:2301 on main) with "currency field" → "currency inline grid column", then the same ISO 4217 minor-unit clause and the same remedy (delete the key, nothing replaces it, scale stays valid on a number column). The pin proves parity by String.replace of the field sentence, not by copying the constant, and refuses currencyConfig|precision in either message.
3. Published text is true. prefix's describe drops "(default '¥')" for "No default: when omitted, the cell shows the symbol of the currency it resolves" — objectui GridField.tsx:1132-1133 reads currencyAdornment(c, currency, locale), "never a default ¥" (objectui#10355), so the old sentence described a fallback the renderer no longer has. scale's describe now says "computed numeric result" and names the currency refusal. field.mdx updates the same two rows in both InlineGridColumn tables (:209, :219 and :359, :369) byte-for-byte to the describes.
4. The pin can fail, and its controls are the right ones. Refusal via FieldSchema (the card's repro, computed scale: 4, one issue at ['inlineColumns', 1, 'scale']), every declared value including scale: 0 computed or not, via ObjectSchema (['fields', 'invoice', 'inlineColumns', 0, 'scale']), and standalone; controls: number column keeps scale: 3, undeclared-type column keeps scale: 2, prefix round-trips on a currency column, the remedy (delete scale, add nothing) parses and re-parses unchanged; shape parity; both describes; the D3 entry under major 18 with a replacement that says DELETE and names no carrier. Reverting the .superRefine turns the four refusal tests green-to-red (the safeParse succeeds), and the old strings fail the describe tests. inline-related-columns.test.ts drops scale: 2 from its currency column with a comment naming the pin.
5. The JSON Schema ledger grows by the one route it allows. dropped-refinements.baseline.json: +1 schema (data/InlineGridColumn), +13 sites (588 → 601, 207 → 208), each new site an …inlineColumns.element under a schema that already lists …currencyConfig at the same depth — the same class as the currency FIELD refusal. The projection closed list (required-one-of, non-blank-string, dependent-required, banned-keys, banned-key-pattern) has no conditional-forbid pattern, so the ledger is the correct carrier and build-schemas.ts accepted the moved lines (Build Core green). Consequence, stated: the published JSON Schema still accepts scale on a currency column; the parse refuses it — the ledger's own description names this class. ③.
6. Population, re-measured at 66e266c931. inlineColumns authors outside packages/spec/src, tests and generated references: the showcase invoice.object.ts (identity-only columns), prose in docs, ADR-0035, audits, CHANGELOGs, the liveness and authorable-surface ledgers, builtin-column-collision.ts, the census script and the relationships skill rule. A scale on a type: 'currency' column appears in none of them (the one scale: 2 near an example, fields.mdx:67, is Field.percent). Matches the changeset's census; deployed metadata is NOT MEASURED and the changeset says so.
7. ADR-0087. The D3 entry and the step18 registry row carry the same id, surface, replacement, reason and acceptanceCriteria; the changeset carries <!-- adr-0087: registered inline-grid-column-currency-scale-refused -->; Check Changeset, Lint & Repo Gates and Spec property liveness are green at head.
8. Mergeability and CI. git merge-tree --write-tree origin/main refs/pull/20223/head at 66e266c931 exits 0 with no conflict. Check runs on 4ab1d0cac2: 33 success, 2 skipped (Console Pin Gate, Packed-tarball smoke — both on the expected-skip roster), 0 red.

② Semver level

@objectstack/spec: minor with a **BREAKING** banner, a FROM → TO table and the registered marker — the launch-window grade for an accept-set narrowing, and every changeset sentence checks out against items 1-7. The changeset's Clause-②: no (narrowing) is exactly the clause2-line.mjs:95 arm: not a widening, but breaking. The PR body's line reads a bare Clause-②: yes, copied, as the body says, from the claim comment 5854472496; a bare yes declares a widening this diff does not contain. Both spellings take at least minor and both mark the change breaking (banner, arm), so no gate outcome differs and the published text is the right one. Recorded, not blocking; the claim's spelling was the seat's line, not the dev's.

③ Boundary flags

• Dev flag, stale notes outside this surface (carrier: none): packages/spec/liveness/field.json notes on inlineColumns.children.prefix / .scale still cite c.prefix || '¥' and c.scale ?? 2; the field-scale.ts docblock's "one 2 that looks like a currency default belongs to an inline grid COLUMN's rounding" describes the pre-objectui#10355 grid. Both describe objectui code that has moved and neither is published text; correctly kept out of this PR. The director seat attaches a carrier card with this record (filed, or an existing one if the board already holds it).
• Item 5: the JSON-schema silence for this refinement is the ledger's known class, with the currency FIELD refusal as precedent; adding a conditional-forbid arm to the projection list is a public-contract decision, not this PR's.
• The objectui GridField follow-up (drop the authored-scale read on currency columns) is objectui's card per triage note 4; nothing in objectui changes here.
• NOT GOVERNED paths; Fixes #20045 closes only the intended card.

Implemented-by: claude/issue-20045-inline-currency-column-scale
Reviewed-by: session_01AsCNgFBs8HCjwhyHQsFbx3

VERDICT: PASS

Rendered at tier by the director seat (summon #30 续) on the fetched head. Not a governed path; the landing pre-checks are met on this head (fresh PASS, CI green, no conflict), so needs:contract-review comes off with this record and ready + auto-merge follow through the relay.

---

Generated by Claude Code