Week of July 27: runtime readiness, packet evidence, and Agent verification
Prepared the beta.72 release path, tightened PostgreSQL-only runtime readiness, improved Wireshark-backed evidence fidelity, and hardened Agent verification workflows.
Platform
- Prepared the v10.0.0-beta.72 release candidate path with refreshed supported application dependencies and clearer runtime readiness lanes.
- Completed the PostgreSQL-only runtime transition by removing legacy datastore guidance and aligning production readiness documentation around the current database architecture.
- Clarified enterprise upload entitlement limits in public docs so SaaS evaluation and paid-plan capture sizes stay easier to compare.
Performance
- Advanced the Wireshark 4.7.3 release branch and retap fixes used for packet export and evidence generation.
- Improved packet-evidence alignment with current Wireshark decoding, including connection correlation snapshots and large-capture hygiene checks.
- Strengthened release test artifacts and bounded test lanes so production validation can catch runtime and evidence regressions earlier.
Agent
- Hardened Agent improvement and verification workflows so preliminary findings, follow-up checks, and grader expectations stay better aligned.
- Expanded the weekly Agent arena and selector benchmarks used to validate large-capture investigation behavior before release.
Bug fixes
- Restored exact summary counter findings in packet evidence surfaced to analysis and report workflows.
- Fixed worker runtime-home and nonroot authentication persistence issues that could affect long-running Agent or worker execution.
- Rebuilt Wireshark artifacts more safely and aligned release packaging outputs with the current runtime image.
Security
- Refreshed production dependency coverage and supply-chain reporting for the supported application stack.
- Packaged the egress firewall entrypoint used by controlled outbound deployments.
On-prem
- Retired obsolete Elasticsearch migration and deployment references from active guidance so on-prem operators see the current PostgreSQL-only path.

