id: CORE-001D
title: External Boundary and Persistence Cleanup for Decimal Unit Types
status: backlog
priority: P2
effort: M
depends_on:
  - CORE-001B
  - CORE-001C
tags: [core, decimal, persistence]
summary: Make Decimal/unit-safe values reliable across persistence, APIs, and provider boundaries.
acceptance_criteria:
  - Persistence format for unit-safe values is explicit and stable.
  - Decimal-bearing JSON/API serialization is documented and tested.
  - Float-heavy integrations have named conversion boundaries.
  - Remaining raw-float domain hotspots are identified or removed.
technical_notes:
  - Prioritize portfolio/workspace persistence, provider normalization, and cache serialization seams.
  - Pre-launch policy: unit-aware schema changes may be breaking until persistence is considered live; old flat payloads may fail loudly instead of being migrated.
  - See `docs/CORE-001D_BOUNDARY_CLEANUP_PLAN.md` for the current hotspot inventory and proposed sub-slices.