[objectstack-fleet]

Part of #20126
Clause-②: no

This PR covers remainder (b) of the currency-mode class-closure card: sites 5–10, appended by the seat in comment 5853407641 and kept in this lane by triage (5853734589). It does not close the card. What stays open is listed under Remainder at the end.

What was wrong

CurrencyConfigSchema declares two modes. Under currencyMode: 'fixed', the field has one currency, defaultCurrency. Under dynamic (the default), the field has no currency of its own: amounts display in the tenant default currency (localization.currency), or as a plain number when none is set, and defaultCurrency is not read, including its parse default CNY. The value is a bare number either way (ADR-0104).

The readers were re-measured for this PR, and each reads defaultCurrency only under 'fixed':

• Analytics relay, at base 1c8b320a8. AnalyticsServicePlugin's sourceFieldMeta (packages/services/service-analytics/src/plugin.ts, the fixedCurrency ternary) answers currencyConfig.defaultCurrency only when currencyMode === 'fixed', and undefined otherwise. queryDataset then resolves mc.currency ?? meta?.defaultCurrency ?? context?.currency. context.currency is the tenant localization.currency (packages/core/src/security/assemble-execution-context.ts).
• objectui's resolveFieldCurrency, at objectui main 25c7d584. packages/i18n/src/currency.ts:60 takes config.defaultCurrency only under currencyMode === 'fixed'.

Six texts under packages/spec/** and examples/** still described an unconditioned defaultCurrency step, or called the chain "ADR-0053". ADR-0053 is the date / datetime semantics record and never names currency.

What changed: text only, site by site

Site 5, packages/spec/src/contracts/analytics-service.ts, the AnalyticsResult.fields[].currency TSDoc. It ships in the published .d.ts. The ADR-0053 label is gone. The middle step is now "the source field's FIXED currency (currencyConfig.defaultCurrency, read only under currencyMode: 'fixed' — a dynamic field has no currency of its own, so its defaultCurrency is not read)". The text cites CurrencyConfigSchema and ADR-0104, and it says the column is also absent when no step answers. The date-bucketing ADR-0053 Phase 2 citation in the same file (now :300) really is a date use, and is untouched.

Site 6, packages/spec/src/data/percent-scale.ts, module header. "This mirrors the ADR-0053 currency chain" now reads "This mirrors the currency chain", with the three steps and the fixed condition spelled out.

Site 7, packages/spec/src/api/analytics.zod.ts, AnalyticsResultResponseSchema docblock. "(the ADR-0053 / percent-scale renderer chains)" now reads "(the currency / percent-scale renderer chains)".

Site 7, in-class extra in the same file: the data.fields[].currency describe. This is the .describe() mirror of site 5, and it said "source-field default" with no mode:

• FROM: Resolved ISO 4217 code for a MONETARY measure (explicit measure `currency`, then source-field default, then tenant default). Absent on non-monetary columns, which must never render a symbol.
• TO: Resolved ISO 4217 code for a MONETARY measure (explicit measure `currency`, then the source field's fixed currency — its `currencyConfig.defaultCurrency`, read only under `currencyMode: 'fixed'` — then the tenant default). Absent on non-monetary columns, which must never render a symbol.

Site 8, packages/spec/liveness/dataset.json (currency) and packages/spec/liveness/field.json (currencyConfig). Evidence text is hand-maintained. check:liveness resolves its paths and #symbol anchors, and gen:liveness-counts tallies statuses only, so the owning route is a hand edit gated by check:liveness.

• dataset.json: the evidence drops the ADR-0053 label and names the middle step "the source field's FIXED currency". It gains a gate-checked anchor at the relay, packages/services/service-analytics/src/plugin.ts#AnalyticsServicePlugin.
• field.json: re-measured at objectui 25c7d584, and the pointers moved with the code: currency.ts :32 → :60, and CurrencyField.tsx :45/:51 → :55/:91. At the old pin 11c1e71e the read was unconditioned, so rewording the text without re-measuring would have pinned a false sentence to that sha.
• Both rows get verifiedAt re-dated to 2026-09-27 and a dated note. Both verdicts stay live; no measurement falsified either one. state-counts.md is unchanged.

Site 9, packages/spec/src/data/field.zod.ts:447, the defaultCurrency describe string only. The .default('CNY') and every other line of the region-split file are untouched. The diff is one line.

• FROM: Default or fixed currency code (ISO 4217, e.g., USD, CNY, EUR)
• TO: The currency code (ISO 4217, e.g. USD, CNY, EUR) of a `fixed`-mode field: its one currency. Not read under `dynamic` (the default), where amounts display in the tenant default currency.

gen:docs regenerated the two matching rows of content/docs/references/data/field.mdx. check:generated proved that one artifact stale, and no other.

Site 10, examples/app-showcase/src/ui/datasets/chart-gallery.dataset.ts. The comment stated the chain with no mode, cited ADR-0053, and spelled the key as a default- / Currency wrap, so a line grep for defaultCurrency missed it. It also told authors to "set a field currencyConfig" to pin a symbol, which pins nothing without currencyMode: 'fixed'. project.budget / spent declare no currencyConfig at all, since Field.currency() injects none. The comment now states the conditioned chain and the fixed form an author would actually write.

In-class extras found by the census, fixed in place

All four conditions of the bounded in-place rule hold for these:

• they are the same defect class;
• each is a mechanical one-phrase text change;
• no other claim holds the files (all 10 open non-release PRs' file lists were read, and none touches any file here; 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's field.zod.ts hunks are at :29 and :2306);
• there is no new verification surface.

The extras:

• packages/spec/src/api/analytics.zod.ts, the fields[].currency describe (above).
• examples/app-showcase/src/data/objects/account.object.ts:63 and semantic-zoo.object.ts:53: "spec channel: currencyConfig.defaultCurrency" gains "read only under currencyMode: 'fixed'". Both fields already declare 'fixed'.
• examples/app-showcase/e2e/detail-shapes.spec.ts:125: "currencyConfig.defaultCurrency drives a real $ symbol" now reads "the fixed-mode currencyConfig.defaultCurrency (USD)". The field is semantic-zoo.budget, fixed / USD.
• packages/spec/src/data/field.test.ts:176: this test-block comment names currencyConfig.defaultCurrency as the declarable nested form. It now adds "under currencyMode: 'fixed' — the only mode that reads it". It is a comment only, with no assertion change.

Census: the seed for remainder (c)

Instrument: a scratchpad script (not committed) that reads each file at a git ref. The scopes are packages/spec/src/**, packages/spec/liveness/** and examples/**: 1881 files at both refs. Base is 1c8b320a8. Head is 6ff1a15c, the final head after merging main e7f69dbb; it reads identically to the pre-merge head 452bd5d4.

Reading	Base	Head
ADR-0053 within five lines of currenc	6 (the six site lines)	0
defaultCurrency lines	79	86 (the corrected text adds lines)
default- / Currency wrapped tokens, which a line grep misses	1 (site 10)	0

Controls.

• The base reading of 6 is the lit leg of the same instrument.
• 38 ADR-0053 lines remain in these scopes at head. All are date uses outside the window: analytics-service.ts:300 (date bucketing, the :294 the order excluded, shifted by this diff) and execution-context.zod.ts:91 (timezone, ADR-0053 Phase 2). No genuine date-bucketing use falls inside the window.

Sentence-level judgment at head. Every prose sentence naming defaultCurrency in these scopes carries the fixed condition or says it is not read under dynamic:

Sentence	Where
Corrected by this PR	field.zod.ts:446, :447, :460–:463, :1060, :1066–:1068; analytics.zod.ts:111–:116; analytics-service.ts:79–:90; percent-scale.ts:14–:18; both ledger rows; chart-gallery.dataset.ts:44–:51; account.object.ts:63; semantic-zoo.object.ts:53; detail-shapes.spec.ts:125; field.test.ts:176
Code, not sentences	the aliases map (field.zod.ts:427), the precision-check code (:465, :505, :512, :2327), and every test fixture
Judged pass, flagged for the pin's author	field.test.ts:202, the it title "names the declarable nested form, currencyConfig / defaultCurrency". It labels exactly what its assertions check (the refusal message contains both tokens), and its body parses the fixed form. Retitling it to claim fixed would need a new message assertion, which is outside a text-only PR. A pin that scans test titles should decide this line deliberately.

Acceptance notes (observed, not filed)

• examples/app-showcase/src/data/objects/semantic-zoo.object.ts:54–:55 says a bare field-level currency key "gets stripped at parse". FieldSchema refuses it: field.test.ts:198 pins success: false, and the guidance message is at field.zod.ts:1066. This is a different defect class, left untouched.
• Released CHANGELOG entries still say "ADR-0053 currency chain": packages/spec/CHANGELOG.md :28383 and :66160, and packages/services/service-analytics/CHANGELOG.md :1976 and :8504, all under 17.0.0. These are release-owned. AGENTS.md routes an amendment to a dedicated docs-only PR, never a rider here.
• objectui 25c7d584, packages/i18n/src/currency.ts:22 and packages/fields/src/widgets/CurrencyField.tsx:52, still cite ADR-0053 for the tenant step. :30 still quotes the spec's pre-docs(spec): currencyMode says what each mode does; the currency-chain text states the fixed condition #20179 "user selectable" wording. The code is right; the comments are in objectui's lane.

Verification

All readings are at head 6ff1a15c: this branch plus a merge of main e7f69dbb. Main brought no file this PR touches. The branch delta against main is byte-identical before and after the merge: git patch-id --stable gives 224b6215 on both.

Build and tests (one os-verify-lock.sh invocation, VERDICT command-exit 0):

• turbo run build --filter=./packages/* --filter=./packages/*/* --concurrency=2: "Tasks: 71 successful, 71 total".
• pnpm --filter @objectstack/spec run check:generated: "All 15 generated artifacts are up to date". This is the second leg: before gen:docs, the same command read "1 of 15 artifact(s) stale: content/docs/references/**", and exactly the 2 defaultCurrency rows moved.
• pnpm --filter @objectstack/spec exec vitest run --project local --maxWorkers=2: "Test Files 540 passed (540) / Tests 15878 passed | 2 todo (15880)".
• pnpm --filter @objectstack/spec run typecheck: exit 0 (tsc --noEmit, check:scripts-typecheck, and "check:test-typecheck: OK").
• pnpm --filter @objectstack/example-showcase run typecheck: exit 0.
• pnpm --filter @objectstack/example-showcase exec vitest run --maxWorkers=2: "Test Files 29 passed (29) / Tests 384 passed (384)".

What ships. The measurement was taken on the built dist, with a positive control:

• The new TSDoc is in dist/contracts/index.d.ts and dist/percent-scale-*.d.ts / .d.mts.
• Both new describes are in dist/ui and dist/api.
• "ADR-0053 currency chain" has zero hits in dist.
• The field.test.ts comment is not shipped.

Consumer fixture triage. No test or snapshot pins any changed string. git grep for the old describe texts and the old example comments outside their own files gives 0 hits, and the same search over examples/app-showcase lights on the edited files as a control. The one generated consumer, field.mdx, is regenerated.

Gates.

• dispatch-gates.mjs --commands --repo objectstack-ai/objectstack at 6ff1a15c derives 109 commands (13 paths vs merge base e7f69dbb). All 109 were run, each exit code recorded before any pipe, and all 109 exit 0. --ran answers "Run reconciliation — 109 derived, 109 run, 0 NOT-MEASURED, 0 UNRUN" (a derived zero: every line carries its exit code).
• The roster families whose roster sits under a touched directory, 6 of them, all exit 0: check-changeset-fixed, spec check:meta-url-spelling, spec check:spec-changes, check:authz-resolver, check:error-code-casing, check:filter-alias-parity.
• check:partof-closing-keyword on this body, offline via PR_BODY: exit 0.

Lint. The run is narrowed, since CI owns pnpm lint. eslint --no-inline-config --format json on the 9 touched .ts files: 9 files, 0 errors, 0 warnings, none ignored. --print-config puts each file in eslint's population, with 4 or 5 rules each. eslint.config.mjs sets no parserOptions.project, so no type-aware linting runs and this diff cannot move a verdict on an untouched file.

Bytes. A control-byte scan over all 13 files gives grep exit 1 (none); the control fixture is lit. check:nul-bytes is in the union.

Ablation. None. The diff is text only: describes, TSDoc, ledger text and comments. No assertion or runtime line changed, so there is no negative pin to ablate. The check:generated red-then-green above is the regenerated artifact's own two-leg reading.

Remainder after this PR

• (a) skills(objectstack-ui): dashboards.md teaches the measure-currency chain with no currencyMode: 'fixed' condition and cites ADR-0053 — remainder (a) of #20126 #20196: skills/objectstack-ui/rules/dashboards.md, the Tier H site. It is open (pm:queue) as this PR opens, per a REST read at 2026-09-27T10:34Z, so this PR is Part of and carries no enumerating pin.
• (c) The enumerating pin. It is seeded by the census above: widen the ADR-0053 scope to packages/spec/src/**, packages/spec/liveness/** and examples/**, and judge the sentence, not the line. The wrapped default- / Currency token this PR removed is one concrete case a line grep cannot see.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

This PR changes 1 package(s): @objectstack/spec, touching 3 documentable anchor(s). ⚠️ 3 changed file(s) yielded no anchor (packages/spec/liveness/dataset.json, packages/spec/liveness/field.json, packages/spec/src/data/percent-scale.ts), so the pages documenting them are NOT COVERED by this run — this is not a clean bill of health for those files.

2 hand-written doc(s) NAME something this change touched and may need an implementation-accuracy re-verification:

• content/docs/api/client-sdk.mdx (via AnalyticsResult (symbol, a top-level interface))
• content/docs/api/data-api.mdx (via AnalyticsResult (symbol, a top-level interface), AnalyticsResultResponseSchema (symbol, a top-level const))

⛔ 2 release-owned page(s) also name something this change touched. These are read-only:

• content/docs/releases/v17/17-3.mdx (via AnalyticsResult (symbol, a top-level interface))
• content/docs/releases/v9.mdx (via AnalyticsResult (symbol, a top-level interface))

content/docs/releases/ is RELEASE-OWNED (AGENTS.md "Documentation Guardrails"): release
notes are written centrally at release time, and a code PR that edits them is the exact PR
that guardrail exists to stop. They are still audited — read-only. If one of them is actually
wrong, file an issue or open a dedicated docs-only PR; do not edit it here.

What this run could not see

• 3 changed file(s) yielded no anchor (packages/spec/liveness/dataset.json, packages/spec/liveness/field.json, packages/spec/src/data/percent-scale.ts) — pages documenting those are invisible to this run
• the SDK route bridge reached 54 of 207 client-bound route-ledger rows — the other 153 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 153: 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; 98 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 585c9af587a165c066c7815185a6652c2b9c545e → packageMentionDocs.

Which tree this was computed on

This run read content/docs from 0358f62a9aabc9c4edbd4fdedc0c0288195e0cd4 — the merge of head 6ff1a15cf4998a432bada27954b4b9bf359ca3c4 into base 585c9af587a165c066c7815185a6652c2b9c545e, 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 0358f62a9aabc9c4edbd4fdedc0c0288195e0cd4 && git checkout 0358f62a9aabc9c4edbd4fdedc0c0288195e0cd4
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin 585c9af587a165c066c7815185a6652c2b9c545e 6ff1a15cf4998a432bada27954b4b9bf359ca3c4 && git checkout -B drift-repro 585c9af587a165c066c7815185a6652c2b9c545e && git merge --no-ff 6ff1a15cf4998a432bada27954b4b9bf359ca3c4

node scripts/docs-audit/affected-docs.mjs --json 585c9af587a165c066c7815185a6652c2b9c545e

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

Advisory only, and a precision-first one (#9192): a page is listed because it names a
symbol, wire route or SDK method this diff touched — not because it mentions a changed
package. Each row says which anchor put it there, so a wrong row is reportable rather than
merely annoying. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs 585c9af587a165c066c7815185a6652c2b9c545e → pass the list as
args.docs, on the commit named under Which tree this was computed on.

[objectstack-fleet]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 6ff1a15cf4998a432bada27954b4b9bf359ca3c4

① Derived judgments

Inputs read: card #20126 body and comments 5853407641 / 5853734589 / 5855121790 / 5855122068; docs/adr/0053-date-and-datetime-semantics.md and docs/adr/0104-field-runtime-value-shape-contract.md at origin/main; the PR body, diff.patch, pr.json, and the head's check-runs; the repo at origin/main (3875ae67) and at the head; objectui at /home/user/objectui (pin f8a9d0fb, origin/main 25c7d584). The supplied diff.patch is byte-equal (modulo index lines) to git diff origin/main...6ff1a15c: 13 files, +71/−34, merge base e7f69dbb.

• The readers, quoted at the head (all three files byte-identical on origin/main). The relay reads defaultCurrency ONLY under fixed: packages/services/service-analytics/src/plugin.ts:1101-1104 — const fixedCurrency = f.currencyConfig?.currencyMode === 'fixed' ? f.currencyConfig.defaultCurrency : undefined; return { type: f.type, max: f.max, defaultCurrency: fixedCurrency };. The resolver, analytics-service.ts:1809-1812 — const monetary = !!mc.currency || meta?.type === 'currency'; if (monetary) { const resolved = mc.currency ?? meta?.defaultCurrency ?? context?.currency; if (resolved) fc.currency = resolved; }. No other production sourceFieldMeta provider exists (git grep at head: only the plugin's). The spec's own reader, field.zod.ts:464-465 — if (config.precision === undefined || config.currencyMode !== 'fixed') return; const contradiction = currencyPrecisionContradiction(config.defaultCurrency, config.precision);. RIGHT: every in-repo reader is mode-conditioned.
• 「the tenant default currency (the localization.currency setting)」 is accurate. packages/core/src/security/resolve-authz-context.ts:1570/:1584/:1610 read settings namespace localization, key currency, scope: 'tenant'; assemble-execution-context.ts:368 sets currency: anonymous ? undefined : localization?.currency; the resolver consumes it as context?.currency (:1811). RIGHT.
• objectui resolveFieldCurrency, at the pin AND at main. At the Console pin .objectui-sha = f8a9d0fb (same at head and origin/main), packages/i18n/src/currency.ts:32 reads field?.currencyConfig?.defaultCurrency || UNCONDITIONALLY: the fix ea9d17fb6 (objectui#10461) is NOT an ancestor of the pin. At objectui main 25c7d584, currency.ts:60 reads (config?.currencyMode === 'fixed' ? config.defaultCurrency : undefined) ||. So the new defaultCurrency describe's 「Not read under dynamic」 holds against every reader in this repository and against objectui main, and does NOT hold against the field faces of the Console vendored here. This is the same state the seat recorded as non-blocking for the release lane at the docs(spec): currencyMode says what each mode does; the currency-chain text states the fixed condition #20179 ACCEPT (5853407641), and the identical claim is already published on main in the currencyMode describe (field.zod.ts:446, 「defaultCurrency is not read」). Not new to this PR; see ③.
• Site 9, field.zod.ts:447 defaultCurrency describe (→ field.mdx:32 / :240). One line; .length(3) and .default('CNY') untouched. Text is TRUE per the readers above and CONSISTENT with the currencyMode describe at :446 (both: fixed = the field's one currency; dynamic = tenant default, defaultCurrency not read). The two regenerated field.mdx rows are byte-equal to the describe; the old string 「Default or fixed currency code」 survives nowhere at head but the changeset's FROM line, and the new string appears only in field.zod.ts, field.mdx and the changeset (no other generated artifact carries describe text). Build Docs check-run success. RIGHT.
• Site 7 extra, analytics.zod.ts:111-116 fields[].currency describe. Node evaluation of the new concatenation equals the changeset's TO byte-for-byte, and of the old equals FROM. The stated order (measure currency → the field's fixed currencyConfig.defaultCurrency, read only under fixed → tenant default) is the :1811 chain plus the :1101 relay. Ships via the ./api export. RIGHT.
• Site 5, contracts/analytics-service.ts:79-90 TSDoc. The chain matches :1809-1812; 「absent … when no step answers」 is if (resolved) fc.currency = resolved;; 「renders as a plain number」 is objectui's formatMeasure (packages/core/src/utils/dataset-format.ts:352, no-currency fall-through to plain numeral formatting) and formatAmount; 「CurrencyConfigSchema in spec/data」 — packages/spec/src/data/index.ts:132 re-exports field.zod, and ./data is in the exports map; 「bare number (ADR-0104)」 — ADR-0104 :60 / :144. The :300 ADR-0053 Phase 2 citation in the same file is date bucketing and is untouched. RIGHT.
• Site 6 percent-scale.ts:14-18 and site 7 analytics.zod.ts:80 docblock. Comment-only; the spelled-out chain and its cross-reference (AnalyticsResult.fields[].currency) are consistent with the above. ADR-0053 (docs/adr/0053-date-and-datetime-semantics.md) contains no occurrence of currenc, so dropping the label is correct. RIGHT.
• Site 8, liveness/dataset.json currency. Both #symbol anchors resolve at head (analytics-service.ts:841 export class AnalyticsService, plugin.ts:261 export class AnalyticsServicePlugin); Spec property liveness check-run success. The monetary rule and the chain are quoted correctly; 「Re-closed by hand against 1c8b320」 — that commit is an ancestor of the head and already carries the fixedCurrency ternary (:1101). Verdict live unchanged. Nit, not a falsehood: the chain sits in the private enrichResultColumns (:1735), which queryDataset calls at :1434 and :1691; 「(queryDataset: the currency chain …)」 is pre-existing wording and loosely right. RIGHT.
• Site 8, liveness/field.json currencyConfig. Re-measured at objectui 25c7d584 (= objectui origin/main): currency.ts:60 (conditioned read), CurrencyField.tsx:55 (resolveFieldCurrency call) and :91 (formatAmount, → formatDisplayNumber → Intl.NumberFormat, packages/i18n/src/utils/formatting.ts:122) all exist as cited; 「since objectui#10461」 is ea9d17fb6; the old pin 11c1e71e really read unconditionally at :32, which is why re-wording without re-measuring would have been false. The README's house style is satisfied: re-attestation is 「re-reading at its current head, re-pin the commit, stamp the date」 (liveness/README.md:311-313), the sha is pinned in the prose, evidenceScope: cross-repo kept; no ledger row cites the .objectui-sha pin (rows cite 11c1e71e, 87af769e, 08ca73f8, 53ded82bf7, 9ce096fb0), so citing main is convention-consistent. Verdict live unchanged. RIGHT.
• verifiedAt re-dates (2026-08-28 → 2026-09-27; 2026-08-10 → 2026-09-27). Justified: the evidence was materially re-measured (new anchor, moved line pointers verified above), which is the README's re-verification event, not a re-stamp. state-counts.md is untouched.
• Site 10, chart-gallery.dataset.ts:44-51. project.object.ts:63-64 — budget: Field.currency({ label: 'Budget', min: 0 }), spent: Field.currency({ …, defaultValue: 0 }): no currencyConfig; the factory (field.zod.ts:2551, ({ type: 'currency', ...config })) injects none. The chain and the prescribed fixed form are correct; the old wrapped default-/Currency token (the one a line grep missed) is gone. RIGHT.
• The four comment-only extras. account.object.ts:63 — the field declares currencyMode: 'fixed', defaultCurrency: 'USD' (:71); semantic-zoo.object.ts:53 — :60 fixed/USD; detail-shapes.spec.ts:125 — the asserted $100,000 is semantic-zoo.budget, fixed/USD, and renders the symbol at both objectui shas since a fixed read is unconditional either way; field.test.ts:176 「the only mode that reads it」 — two modes, only fixed reads; no assertion changed (the it at :202 and its success:false pin at :198 are untouched). No new false statement.
• Behaviour: text only. Every hunk is a describe string, TSDoc, comment, JSON evidence/note/verifiedAt string, the changeset or the generated mdx. The only source-level change of form is the re-split string concatenation in analytics.zod.ts, evaluated identical above. field.zod.ts differs from the merge base by that one line. Build Core, Type Check · source gates, Lint & Repo Gates, Check Changeset, Spec property liveness, Build Docs are success at the head; at my last poll 29 success / 5 skipped / 3 in progress (Test Core 1/6, 6/6, Type Check · workspace) / 0 failing.
• Main drift since the merge base. origin/main moved to 3875ae67; of the 13 files only field.zod.ts changed on main (fix(spec): a currency field's precision is total digits — stop refusing precision: 18 on a fixed-USD field (#20011) #20209, hunks at :29-:33 and :2306-:2330 — the FieldSchema-level precision check removed), not :447; GitHub reports mergeable: true. The changeset's 「the spec's own precision refinement in CurrencyConfigSchema」 stays true after fix(spec): a currency field's precision is total digits — stop refusing precision: 18 on a fixed-USD field (#20011) #20209 (the CurrencyConfigSchema twin at :464 is kept).
• Own census (scopes packages/spec/src/**, packages/spec/liveness/**, examples/**; base e7f69dbb → head). ADR-0053 within five lines of currenc: 6 → 0, the six lines being exactly sites 5–10; wrapped default-/Currency: 1 → 0; ADR-0053 lines overall 44 → 38, every remaining one a date use; defaultCurrency lines 79 → 86. Sentence by sentence at head: every prose sentence naming defaultCurrency in scope carries the fixed condition or the not-read-under-dynamic negation (field.zod.ts:446/:447/:460-:462/:1060/:1067, analytics.zod.ts:114, contracts/analytics-service.ts:82-:84, percent-scale.ts:17, both ledger rows, the four example/test comments); every other line is code or a fixture; the it title at field.test.ts:202 is a label, correctly flagged for (c). A grep for chain sentences that avoid the key token (「source field」/「tenant default」 near currenc) finds only percent-scale.ts:18, conditioned. Nothing in scope was missed.

② Semver level

'@objectstack/spec': patch is the right level. @objectstack/spec publishes dist, src/**/*.zod.ts and liveness (package.json files), so the describes, the emitted TSDoc, the two .zod.ts sources and both ledger files ship — a changeset is owed and skip-changeset would be wrong (AGENTS.md step 3). Clause-②: no matches the diff (no key, default, accept set, type or export moves), and only yes takes at least minor, so patch is both floor and ceiling. Precedent: #20179's .changeset/20126-currency-mode-describe.md, the same class, patch, merged. The FROM → TO pairs are accurate (both evaluated byte-equal to the old and new source strings). No ADR-0087 entry is owed: a disposition marker is required only on a BREAKING changeset (AGENTS.md:1085), nothing authorable is removed or renamed, and spec-changes.json is untouched. Check Changeset check-run success.

③ Boundary flags

• Console pin vs. published text (non-blocking, recorded). At .objectui-sha f8a9d0fb the Console's field faces still read defaultCurrency unconditionally (currency.ts:32); the describe, the changeset sentence naming 「objectui's resolveFieldCurrency」 and the field.json row are true of objectui main 25c7d584. Same state as the docs(spec): currencyMode says what each mode does; the currency-chain text states the fixed condition #20179 ACCEPT recorded for the release lane, and the :446 describe already on main makes the identical claim. The PR body cites objectui main only and does not restate the pin fact; the card carries it (5853407641). Not a defect of this PR; it closes when the pin bumps past ea9d17fb6.
• Family append 5855122068. The released CHANGELOG entries (packages/spec/CHANGELOG.md:28383 / :66160; service-analytics/CHANGELOG.md:1976 (17.0.0) / :8504 (17.0.0-rc.2)) are correctly left out: AGENTS.md:699 makes them release-owned, amended only in a dedicated docs-only PR. One more line of the same kind that the append does not list: packages/services/service-analytics/CHANGELOG.md:10728 (under ## 10.0.0), 「source-field currencyConfig.defaultCurrency → tenant default (ctx.currency)」 — same disposition, pointer for the family. The objectui comment pointers (currency.ts:22/:30, CurrencyField.tsx:52 at 25c7d584) are objectui-lane and correctly not filed here.
• Part of with skills(objectstack-ui): dashboards.md teaches the measure-currency chain with no currencyMode: 'fixed' condition and cites ADR-0053 — remainder (a) of #20126 #20196 open. REST read this act: skills(objectstack-ui): dashboards.md teaches the measure-currency chain with no currencyMode: 'fixed' condition and cites ADR-0053 — remainder (a) of #20126 #20196 is open, pm:queue, domain:skills. So Part of #20126, no closing keyword (check-run Part-of PR must not also close its card success), and the enumerating pin deferred to remainder (c) per triage 5853734589 is the right shape — (c) covers skills/** and can only go green after (a).
• For (c)'s pin design, two further pointers from the whole-repo census (minus CHANGELOGs) at head: the remaining ADR-0053-near-currenc lines are skills/objectstack-ui/rules/dashboards.md:308 (= skills(objectstack-ui): dashboards.md teaches the measure-currency chain with no currencyMode: 'fixed' condition and cites ADR-0053 — remainder (a) of #20126 #20196), this PR's own .changeset negation sentences (a count-based rule over .changeset/** would red on them), current-user-endpoints.ts:908 (a 「used to … citing ADR-0053」 negation), localization.manifest.ts:6 (ADR-0053 Phase 2 as the lineage of the localization settings family, which includes currency — lineage, not the chain), and two plugin-email date uses. The scope triage set for (c) excludes all of these except the skills site.
• Concurrency. All 12 open PRs' file lists were scanned: none touches any of the 13 files. Check-runs No other open PR may claim the same single-writer path / …the same issue success.
• PR is a draft; mergeable_state: blocked reflected required checks still in progress at read time, not a conflict.

Implemented-by: claude/issue-20126-currency-chain-spec-sites
Reviewed-by: session_01Rjy9MeetSfq34PKn81CRiN

VERDICT: PASS