v0.5.0

Changes

• Clean up stopped session and agent histories even when their stored spawn relationship remains Open. Writer ownership, retained-history dependencies and exact file/SQL effect checks remain enforced.
• Assess newer versions against the source paths and storage behavior that affect cleanup. Reuse the qualified native helper when execution inputs remain compatible, and import signed support records without restarting the MCP server.
• Install and update a matched Python/native bundle with verified GitHub provenance and hash-locked dependencies. Preserve previous installations needed to inspect saved cleanup receipts.
• Use the shared cleanup pipeline through CLI, Textual and MCP, including explicit selection, project/work grouping, sorting and supported Guardian histories.

Using this release

Follow the installation and upgrade guide. The attached installer verifies the release before activation. Reconnect existing MCP clients after updating the application.

Select stopped work. Related updates to the selected histories' metadata and publication of dependency references must have finished; unrelated sessions may continue running. Fresh validation can refuse an operation if its approved effects have changed. Use reconciliation to inspect an uncertain result; do not resend an uncertain deletion.

Cleanup removes the approved histories directly without copying their contents to a backup or substituting compression for deletion.

Full preview validates the entire managed history namespace, including retained dependencies. It can take substantial time on large or slow filesystems. Blocked filesystem calls have no finite completion guarantee; catalogue browsing and full preview are separate operations.

Compatibility

Qualified for Linux x86_64 with the documented runtime and local-filesystem requirements, including the supported Codex 0.166.0 persistent workflows. Plain and Zstandard-compressed histories and paginated storage remain supported within the qualified profile. See the compatibility guide and cleanup contract for exact conditions.

The bundle, wheel, source archive and installer have GitHub artifact attestations. The support record is separately attested. SHA256SUMS lists the assembly checksums; the native material is additionally pinned by the source qualification and bundle manifests.

The native-material.tar.gz asset is the qualified native build input for maintainers and CI. End-user installation uses the verified installer and matched runtime bundle.