Skip to content

SIA v1.8.3 — redaction recovery and btrfs continuity

Latest

Choose a tag to compare

@AnubisQuantumCipher AnubisQuantumCipher released this 01 Oct 15:22
· 4 commits to main since this release
0ba83a0

A redacted agent note no longer leaves the pending publication marker behind the durable redaction total. The accounting updates pending pulse and dream targets in the same memo write and refuses any attempted retraction. When a saved pending marker is invalid, the resident daemon stops visibly instead of retrying indefinitely; other failures retain their normal retry behavior. Recovery errors identify the disagreeing count.

An already-stranded installation needs the documented one-time recovery procedure before it can pass readiness. Installing this release alone does not repair that prior state. See CHANGELOG.md, Recovering a machine that is already stuck.

This release also includes the btrfs continuity change already merged in PR #26. Explicit enrollment permits device-only receipt readmission across a btrfs remount after checking the recorded filesystem, subvolume, directory, and adoption identity. It is disabled without enrollment, preserves audit records, and refuses other identity changes. See docs/MANUAL.md for enrollment, upgrade, and revocation. Readiness does not prove a recent backup.

Omarchy installation uses the existing repository command and an explicit guided first-light or update action. This release does not itself confer marketplace verification or remove the marketplace manual-installation override. Those require separate review of the final exact commit and the supported installation boundary.

Validation: all required jobs passed on final main commit 0ba83a00bad240aaa903f3b7598ebb39de2a42c4: https://github.com/AnubisQuantumCipher/sia/actions/runs/36872868744. The earlier interrupted local full-suite run is not cited as a pass.