@happyvertical/smrt-support 0.40.70 → 0.42.0

package/AGENTS.md

@@ -238,10 +238,43 @@ by #1955. No inter-`smrt-*` `peerDependencies`.
 
 ```sh
 pnpm --filter @happyvertical/smrt-support test
+pnpm --filter @happyvertical/smrt-support test:postgres
 pnpm --filter @happyvertical/smrt-support typecheck
 pnpm --filter @happyvertical/smrt-support build
 ```
 
+`test:postgres` is the lane that holds the money/rate line — SQLite's type
+affinity stores a REAL in an INTEGER column without complaint, so a money field
+that reverted to DECIMAL passes every SQLite suite.
+
+## Money and rates
+
+- **Money is integer minor units** (cents) — `$19.99` is `1999`.
+  `SupportPlan.availabilityFeeAmount`, `SupportCharge.amount` and
+  `SupportCompensation.amount` initialize `= 0`, never `= 0.0`: the integer
+  literal is what maps them to INTEGER columns (BIGINT on fresh PostgreSQL/DuckDB databases; #2401, #2373).
+- **Rates stay DECIMAL but their unit changed.**
+  `SupportPlan.overageHourlyRate` / `onCallHourlyRate` and
+  `SupportCompensationPlan.hourlyRate` are **minor units per hour**, so
+  `hours * rate` yields minor units. INTEGER would truncate a sub-unit rate to
+  zero, which is why they keep a decimal initializer.
+- **`roundMoney()` is the single rate↔money boundary.** It rounds
+  `(seconds / 3600) * hourlyRate` to a whole minor unit, which is what lets the
+  `thresholdAmount` comparison in `determinePath()` be an exact `>` with no
+  tolerance. `TimeApprovalPolicy.thresholdAmount` is in the same unit as
+  `SupportCharge.amount`.
+- **Migrating an existing database**: `preflightSupportMoneyMinorUnits(db)`
+  reports which columns still hold major units and which rows would be rounded
+  or exceed JavaScript's safe-integer range; `migrateSupportMoneyToMinorUnits(db)` converts them
+  (idempotent via `_smrt_backfills`). The **rate columns are not in that list**
+  — their type does not change, but their stored values must still be
+  multiplied by the same scale in the same deploy step. Frozen `rateSnapshot`
+  JSON on settled charges is history and is left alone. On SQLite the values
+  are rescaled but the declared type needs the table-rebuild path (#2370).
+  Fresh PostgreSQL/DuckDB INTEGER columns are BIGINT and hydration rejects
+  values outside JavaScript's safe-integer range; existing PostgreSQL `int4`
+  columns require #2424.
+
 ## Gotchas
 
 - **Writes go through the facades** — the case-side generated routes are

package/dist/index.d.ts

@@ -1,3 +1,4 @@
+export { migrateSupportMoneyToMinorUnits, preflightSupportMoneyMinorUnits, SUPPORT_MONEY_COLUMNS, SUPPORT_MONEY_MINOR_UNITS_BACKFILL, } from './migrations/moneyMinorUnits.js';
 export * from './models/index.js';
 export { APPROVE_TIME_ENTRY_PERMISSION, ensureSupportPermissionsRegistered, MANAGE_PLANS_PERMISSION, REASSIGN_CASE_PERMISSION, registerSupportPermissions, SUPPORT_PERMISSION_DEFS, type SupportPrincipal, supportPrincipalFromPermissions, } from './permissions.js';
 export * from './services/index.js';

package/dist/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AAKH,OAAO,wBAAwB,CAAC;AAIhC,cAAc,mBAAmB,CAAC;AAClC,OAAO,EACL,6BAA6B,EAC7B,kCAAkC,EAClC,uBAAuB,EACvB,wBAAwB,EACxB,0BAA0B,EAC1B,uBAAuB,EACvB,KAAK,gBAAgB,EACrB,+BAA+B,GAChC,MAAM,kBAAkB,CAAC;AAC1B,cAAc,qBAAqB,CAAC;AACpC,cAAc,YAAY,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AAKH,OAAO,wBAAwB,CAAC;AAKhC,OAAO,EACL,+BAA+B,EAC/B,+BAA+B,EAC/B,qBAAqB,EACrB,kCAAkC,GACnC,MAAM,iCAAiC,CAAC;AACzC,cAAc,mBAAmB,CAAC;AAClC,OAAO,EACL,6BAA6B,EAC7B,kCAAkC,EAClC,uBAAuB,EACvB,wBAAwB,EACxB,0BAA0B,EAC1B,uBAAuB,EACvB,KAAK,gBAAgB,EACrB,+BAA+B,GAChC,MAAM,kBAAkB,CAAC;AAC1B,cAAc,qBAAqB,CAAC;AACpC,cAAc,YAAY,CAAC"}