Added — prikk status --format json, and which patches a seal will freeze
prikk status could say how many patches were queued, but not which ones. --format json
(status-report-v1) now carries everything the prose form does, plus the queue itself: for each
queued patch, in queue order, its patch id, its operations' kinds, and the paths those operations
affect. This is for knowing which patches a seal will freeze, not only how many — the same
information a seal ceremony needs to ask for informed consent before an irreversible act, not just
a count of how much is about to happen. Bare prikk status is unchanged and pays nothing new; the
queue is only resolved when --format json actually asks for it.
Changed — six more refusals now say precondition not met, not lock conflict
A full active-patch queue, an active WAL owned by the wrong ref for a commit, an incomplete ref
publication, a non-empty active WAL at rollback-draft or seal-from-accepted time, and an active WAL
holding more than a rollback draft at verify time were all reported as lock conflict: .... None
of them involve a lock: nothing is held, no other writer is racing, and waiting never made any of
them go away — only running seal, doctor, or retrying with the right ref did. They now read
precondition not met: ..., matching what was actually wrong and what actually fixes it.
Prebuilt binaries
Linux (aarch64/x86_64), Windows (x86_64), macOS (aarch64). Each archive contains the prikk binary, LICENSE, and a sibling .sha256
checksum plus .build-info.txt recording the exact toolchain and command used to build
it — reproduce with:
git checkout <tag> && cargo build -p prikk --release --target <triple> --lockedcargo install prikk remains the toolchain-based install path; these binaries are an
additional option, not a replacement.
macOS binaries are unsigned. Gatekeeper will warn on first run — right-click (or Control-click) the binary and choose Open, or clear the quarantine attribute directly with xattr -d com.apple.quarantine <path>. Notarization needs an Apple Developer identity and is a stated gap for a future increment, not an oversight.
Release authority — read before relying on this release
This release does not pass the DC-35 signer-authority audit, and does not claim to. The
committed release-signer set (release-signers.toml) is empty and fail-closed, so no release
currently satisfies that gate. A checksum published beside a binary on this page proves integrity of
transport, not authority of origin. Verify what you obtain by content, not by release authority —
see prikk verify and this project's
release-compatibility reference.