Read Gaplessly's own invoices to this org, newest first (admin)

What `UsageCard` renders on `/billing`. A read of the append-only `book_usage_events` ledger via `lib/usage.ts`. **Two metered resources since pass 2 (2026-08-08), and they are not symmetric.** `sms` is gated and re-billed: every `sendSms()` call site goes through `meteredSendSms`, and each segment is billed at A$0.09 per text. `email` is neither: every `meteredSendEmail` send is counted, but email is included on every plan, is not re-billed, and cannot be capped (see that function's own header). Bookings remain the one documented chokepoint still uninstrumented. **No cap or block lives here or anywhere else** (2026-08-07): `sms` is either off entirely (a plan without texts, or a trialing tier that hasn't converted to paid, per `planAllows`'s own trial gate) or fully on with no allowance and no ceiling. This route only ever reports what was sent, never a reason a send was refused for running out of anything. `allowed: false` zeroes `usedThisPeriod` without reading the ledger for SMS, because there is nothing to meter for a business that cannot use the feature. **It no longer short-circuits the whole response**: pass 1 did, which would now hide the email count from every company whose plan has no texts, i.e. most of them. The four top-level fields keep their pass-1 shape and meaning exactly and describe SMS alone; `email` was added as a nested object rather than a reshuffle, so this stayed an additive change. `included` is always `0` (no tier or add-on bundles a free allowance any more, see `TIER_LIMITS`'s own comment), kept in the response rather than dropped so `UsageCard` never has to special-case its absence. One billing-period boundary serves both resources, derived from `book_billing.current_period_end` via `periodStartFor()`.