Release notes
OpsProbe v0.3.38: Free V1 P0/P1 hardening.
The standard Free workspace now has predictable limits, clearer operational surfaces, and bounded server-side behavior.
Summary
OpsProbe v0.3.38 publishes the Free V1 P0/P1 hardening work on top of the v0.3.37 preview contract. It keeps the product free to try while making limits, status visibility, alert verification, retention, domain evidence, and resource budgets explicit and server-enforced.
Free workspace boundary
- Five websites, fifty monitor slots, five-minute scheduling, and thirty-day plan-aware retention.
- HTTP, DNS, SSL, TCP, Ping, Keyword, and Heartbeat monitoring, with one TCP port per Free website.
- One tokenized public status page with redacted component and incident summaries.
- Recurring monitoring remains included and does not consume Ops Credits.
Operational hardening
- Controlled alert tests use the same SMTP outbox and delivery worker boundary as incident alerts.
- Retention cleanup preserves the latest monitor result and open incidents.
- Cached RDAP profiles expose safe public registrar and domain lifecycle evidence.
- Scheduler, workspace, anonymous-target, and outbound request budgets bound one-server cost and abuse risk.
- Public pricing, docs, roadmap, latest progress, and LLM metadata now describe the same capability boundary.
Verification
- 72 deterministic tests and 103 coverage tests passed.
- Workspace line coverage reached 80.06%.
- Formatting, Clippy, dependency audit, locked release build, and JavaScript syntax checks passed.
- Playwright responsive smoke passed at 390px, 768px, and 1440px across nine routes.
Known limits
Production SMTP delivery remains disabled until explicitly configured. Real credit purchases, multi-node probes, browser checks, business-flow checks, AI analysis, and a long-running 50-monitor soak remain follow-up work. The current Free limits are bounded and enforced.