The stable release is 1.3.3. Documented contracts are established; extended validation is tracked separately and is not completed merely by changing the version number.
1.3.1 — Upgrade from 1.3.0 to 1.3.1
1.3.0 — Upgrade from 1.2.0
1.2.0 — API credentials, journal cursors and Docker command timeouts.
1.1.4 — Guided installation for the agent and local dashboard with first-collection verification.
1.1.3 — After a failed cycle, the dashboard shows the time and contents of the last complete snapshot in read-only mode. There is no history before the first successful cycle.
Available
Cron/serve modes, YAML scenarios, dry runs, resource and filesystem checks, ACLs, restart budgets, protection and maintenance. Mobile-friendly web UI, journal and exports, Prometheus/Grafana and notifications. The explicit ncurses interface has been available read-only since 0.0.82. Version 1.1.0 also provides an optional Textual dashboard with search and details.
Version 1.1.2 adds explicit 140/110 rule errors, an observation-only Compose setup with optional HTTPS UI and a memory tutorial. These delivered features do not close the prolonged observation work below.
1.0 contract established
Configuration and CLI, HTTP /v1, metrics, journal schemas, environments and deprecation have documented references. The five CLI/YAML decisions were implemented in 0.0.80. See the release notes and command contract.
Installation and upgrades
Release checks passed for installed packages, images and UI, with upgrade/rollback rehearsals from 0.0.78, 0.0.79 and 0.0.82. Procedures retain configuration, state, journals and archives. These results do not certify every platform/version combination.
Performance and resilience — continuing work
Finite measurements cover 1/50 MiB journals, concurrent readers, rotation, exports and recovery after injected failures. Resource use, disk I/O and end-to-end latency still need representative workloads and documented acceptable bounds. A local measurement is not a user-latency guarantee.
Field acceptance
- Passed: Docker/PTY tests and real SSH acceptance of 1.0.0 on 28 September 2026, covering navigation, resizing, journal, quit/Ctrl-C and terminal restoration.
- Separate follow-up: a prolonged-observation verdict requires review of the retained final measurements.
- Open: prolonged interactive sessions, abrupt network loss and representative sustained workloads.
No 24-hour outcome is claimed before review. See the release notes for scope and limits.
Later candidates
- Checks and scenarios driven by real usage.
- Journal indexing or alternative storage if measurements justify it.
- History navigation and exports based on feedback.
Principles and participation
Keep DWho, HTTPdis, Sonicprobe, simple local configuration and a light mobile UI. Prefer measured results and documented behavior. Code, UI labels and machine-readable reasons remain English.
The repository roadmap tracks progress. Discuss priorities through GitHub issues.