Capability milestones for the developer platform — what the sandbox surface can actually do. Newest first.
Everything below is a capability and architecture milestone available in the sandbox — not a shipped-GA or “now available in production” announcement. No live money or live patient data is reachable from this tier. When production access opens for a capability, that is said plainly and separately.
Claim and Remittance money fields were migrated off floating-point dollars onto conserving integer cents. This removes float drift from the claim-to-remittance path so the reconciliation waterfall can preserve the cent total exactly.ProviderWallet balances converted from float dollars to drift-safe integer cents. Establishes the integer-cent boundary for wallet reads and writes so no rounding can accumulate across postings.GET /api/op-note/[id] so a saved operative note rehydrates its modal on a fresh session rather than only within the authoring tab. Scoped to your organization; returns a typed refusal rather than a fabricated record when the note is absent.The behavior described runs on real logic in the sandbox. The capability is real as architecture.
That it moved live money, carried live patient data, or shipped to production. Production access is a separate approval, tracked honestly on the security page.
The developer hub indexes every API surface; the security page carries the status register — what is available in the sandbox versus what is still gated on a named approval.