Release notes
OpsProbe v0.3.25: save a diagnostic as a monitor.
The first commercial-loop step now connects a useful anonymous result to a protected, standard monitoring workflow.
Quick answer
After a visitor explicitly saves a completed probe, OpsProbe preserves only its URL for up to one hour, continues through same-browser sign-in, and creates a pending website in the Console. Ownership verification is required before scheduled monitors run.
Highlights
- Added Save as monitor to anonymous probe results.
- Added duplicate-safe pending-site creation after authentication.
- Added a visible fixed profile for HTTP, DNS, SSL, and the default TCP endpoint.
- Recorded diagnostic-originated saves as instant_probe_saved for server-side funnel analysis.
- Kept monitor activation behind ownership verification.
Safety and product boundary
The browser continuation stores only a canonical HTTP or HTTPS URL and timestamp. It excludes evidence, IP addresses, headers, OAuth data, and identity. This release does not include paid plans, Ops Credits, multi-region probes, browser journeys, or custom monitor profiles.
Verification
- cargo fmt --check
- cargo test
- cargo build --release
- node --check web/app.js
- scripts/release-check.sh 0.3.25
- Playwright mocked authenticated conversion checks at desktop and mobile widths.