Release v0.1.18: Auto-Topup Settings

13 February 2026

What changed

• Auto-Topup UI on the billing page — new section with a toggle to enable/disable, a threshold input ("top up when balance falls below X credits"), a package selector dropdown, a summary card showing what will happen, and a save button with dirty-state tracking.
• New API endpoints — GET /api/credits/auto-topup returns current settings and available packages; PUT /api/credits/auto-topup saves settings with Zod validation and audit logging (IP + user agent).
• Bug fix — getCreditBalance() now returns the autoTopupPackageId field that was present in the DB schema but missing from the response.
• Stripe dependency added — stripe ^17.0.0 added to prepare for payment integration.
• 14 new tests covering authentication, validation, business rules, and success paths for both endpoints.

Why it matters

You can now configure auto-topup directly from the billing page so your monitoring never lapses because you ran out of credits. Set a threshold, pick a package, and credits will be purchased automatically when your balance drops.

Technical notes

• When enabling auto-topup, both threshold (1–10,000) and packageId are required; when disabling, they're optional.
• Audit log failures are caught silently so they never break the main save flow.
• Form state initialises from existing account data on page load.