Release notes
OpsProbe v0.3.39: close Free, establish Basic P0.
This release closes the current Free hardening boundary and adds a server-authoritative subscription foundation without pretending that checkout is live.
Summary
v0.3.39 is deployed to production. Free workspaces now have ten websites, ninety days of plan-aware history, verified SMTP readiness, and the same bounded monitor execution policy. Basic P0 adds subscription state, cancellation intent, resume behavior, and a signed provider webhook boundary. Real payment collection remains disabled.
Free close
- Ten websites, fifty monitor slots, five-minute scheduling, one TCP port per website, and ninety-day plan-aware history.
- HTTP, DNS, SSL, TCP, Ping, Keyword, and Heartbeat monitoring remain server-enforced.
/readyzreports SMTP configuration state; production Resend delivery was verified with a controlled received message.- Transient transport failures still receive one bounded confirmation retry, and incidents require consecutive matching results.
Basic P0 foundation
- Added additive subscription and billing-event persistence for every workspace.
- Added authenticated billing summary, cancellation-at-period-end, and resume routes.
- Added provider-neutral signed webhooks with a five-minute replay window and duplicate-event suppression.
- Kept checkout explicitly unavailable until a payment provider is configured, so no incomplete purchase flow is exposed.
- Added a Console Settings billing card that shows current state and hands Free users to the pricing preview.
Verification
- 76 deterministic tests passed.
- 114 tests passed with isolated PostgreSQL/Redis integration coverage.
- Workspace line coverage reached 80.89%, above the 80% release gate.
- Formatting, Clippy, dependency audit, JavaScript syntax, and locked release-build checks passed.
- Test schema initialization now uses a database-backed marker, preventing cross-process migration replay during coverage.
Boundary
This release does not activate payment collection, recurring renewals, refunds, failed-payment recovery, real Ops Credits top-ups, multi-node probes, browser journeys, or AI diagnosis. These remain planned boundaries for later releases.