Haps v0.1.13

Haps now requires an audit of the exact release by default. When an audit is missing, the interactive installer offers to review pinned source with your installed agent, rebuild it, and compare the complete payload before installing. Omarchy’s supported default agent is offered first.

• Use haps install PACKAGE --allow-unaudited to bypass the audit threshold for one operation. The flag also works with update and rollback; it preserves the threshold for later operations and does not create an audit.
• Prepare and finish a manual source review with haps audit prepare and haps audit finish. Choose whether to keep signed audits private or publish them, and configure your preferred agent and model.
• Preserve signature, payload integrity, social trust, and warning checks when bypassing audits.
• Fix Windows command stack usage and require public relay delivery when publishing release announcements.

Verified with the native test suites on Linux, macOS, and Windows; the audit flow was also exercised in Arch Docker with actual Omarchy launchers and a real Codex review, matching rebuild, installation, and successful program run. This was not a full graphical Omarchy desktop test. Audits describe the checks performed and are not a guarantee of safety.

The five native bundles include checksum-pinned htree and git-remote-htree helpers. SHA256SUMS covers every archive.

Installation: https://haps.hashtree.cc/#install