feat(analytics): resolve a monetary measure's currency via field config + tenant default

[xuyushun441-sys]

Phase 1b — analytics measure-currency chain

Builds on #2119 (ExecutionContext.currency). The dataset measure-currency enrichment honored only an explicit measure currency literal (the original #2102 behavior) — so a measure summing a currency field, or any measure on a tenant with a configured default currency, rendered symbol-less unless the author restated the code on every measure.

Now a monetary measure resolves through the documented chain:

explicit measure `currency`
  → source-field `currencyConfig.defaultCurrency`
  → tenant default (`ctx.currency`, from the localization setting wired in #2119)

A measure is monetary iff it declares a currency or aggregates a currency-type field — so count / avg-of-a-number measures never receive a (wrong) currency code.

Changes

• analytics-service: AnalyticsServiceConfig.measureCurrency(object, field) → source-field { type, defaultCurrency }; the enrichment applies the chain, gated on monetary type.
• plugin: wires measureCurrency from the data engine's getObject().fields — the same accessor the dimension label resolver already uses (no new dependency).

Tests

query-dataset → 15 passed (+4):

• currency-field measure with no explicit currency → inherits field defaultCurrency
• currency field with no default → falls back to ctx.currency
• explicit measure currency wins over field default + tenant ctx
• a non-currency field measure stays code-less even with a tenant default

Follow-ups

• Template-engine ({{ x | currency }}) still hard-defaults to USD; threading ctx.currency there is a small separate change (different package).
• Phase 2 (objectui): one shared resolver/formatter + a client context exposing the tenant default; replace the ~20 ad-hoc client sites.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
spec	Ready	Preview, Comment	Jun 21, 2026 9:47am

[github-actions]

📓 Docs Drift Check

This PR changes 1 package(s): packages/services.

5 hand-written doc(s) reference the affected code and may need an implementation-accuracy re-verification:

• content/docs/guides/packages.mdx (via packages/services)
• content/docs/guides/runtime-services/audit-service.mdx (via packages/services)
• content/docs/guides/runtime-services/index.mdx (via packages/services)
• content/docs/guides/runtime-services/settings-service.mdx (via packages/services)
• content/docs/protocol/objectos/i18n-standard.mdx (via packages/services)

Advisory only. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs origin/main → pass the list as args.docs.