docs(skills,adr): homeAmount.rateDate is date/datetime, the currency row lists all four currencyConfig keys, and ADR-0144 Open item 1 records the settled pointer spelling

Should-fixes 3-5 of contract review 6526217217 on PR #28096: the field-types
paragraph under-taught `rateDate` as `date` only, the Numbers table row named
two of the four real `currencyConfig` keys, and ADR-0144 Open item 1 gains a
dated note recording `rateDate` / `rateField` as landed.

Fixes #28203

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016WV4d156vwPo83g9GQuJSt

Author: claude

docs/adr/0144-multi-currency-record-currency-dated-rates-write-time-home-projection.md

@@ -320,6 +320,14 @@ Where a source leans one way, the lean is quoted here, not adopted. This record
    workload row M2-1 and #27191 is corrected to required. Workload row M2-1 drafts the names `rateDate` and
    `rateField`; in that draft, `rateDate` is "a `date`/`datetime` field on the same object (⛔ no default)". The design
    record §6 says the document date must not default to `created_at` (「⛔ 不默认 created_at」).
+   *Note (2026-10-31):* settled: the pointers are spelled `rateDate` (the document date) and `rateField` (the rate
+   used), the names workload row M2-1 drafts, landed in PR #28096 (`73b72709`). Beside them `homeAmount.field` names
+   the home field, and all three are required with no default
+   (`packages/spec/src/data/field.zod.ts#HomeAmountSchema`). `rateDate` names a `date` or `datetime` field on the
+   same object (`packages/spec/src/data/object.zod.ts#HOME_AMOUNT_RATE_DATE_TYPES`) and `rateField` a `number` field;
+   both the home and the rate field declare `readonly: true`, and the object judges what each pointer names
+   (`packages/spec/src/data/object.zod.ts#refuseDishonestHomeAmount`). Review: contract review
+   [`6526217217`](https://github.com/objectstack-ai/objectstack/pull/28096#issuecomment-6526217217) on PR #28096.
 2. **Which row counts as "the document date's rate"** (#27192). The ruling says "a platform rate table by effective
    date". Workload row M2-2 and the measurement round read this as the row with the latest `effective_date` on or before
    the document date. The measurement round also rules out a "nearest-future rate". The design record §5 says

skills/objectstack-data/rules/field-types.md

@@ -50,7 +50,7 @@ fields: {
 | Type | When to Use | Config |
 |:-----|:------------|:-------|
 | `number` | Generic numeric value | `min`, `max`, `precision`, `scale` |
-| `currency` | Monetary amounts | `currencyConfig` (currencyMode, defaultCurrency) |
+| `currency` | Monetary amounts | `currencyConfig` (currencyMode, defaultCurrency, currencyField, homeAmount) |
 | `percent` | Percentage values (0-100) | `min`, `max`, `precision` |
 
 ## Date & Time
@@ -178,8 +178,8 @@ stored field to `'record'`? Backfill: `os migrate record-currency-codes`.
 
 `homeAmount` (`'record'` only, all three required): the engine stores the
 home-currency amount in `field` (a `'dynamic'` `currency`) at the `rateDate`
-(`date`) rate, and that rate in `rateField` (`number`), both `readonly: true`.
-Cross-currency totals sum `field`.
+(`date`/`datetime`) rate, and that rate in `rateField` (`number`), both
+`readonly: true`. Cross-currency totals sum `field`.
 
 ### Select with Default