0.31.1

Nothing about running prikk changes, and this release cannot strand a machine. No command,
flag, exit code, message, object format or on-disk layout differs from 0.31.0, and repositories
written by 0.31.1 are readable by 0.31.0 — the opposite of the previous release, which was
one-way. Not one line of runtime source changed between the two tags; only crate manifests and one
test file did.

Why it exists — the published crates were miscatalogued

Every crate published up to and including 0.31.0 carried no categories, no keywords, and no
documentation URL. crates.io renders a crate's page from its published manifest, so the fix had
to travel in a release; there was no other way to deliver it.

All eight published crates now carry:

• categories — development-tools, command-line-utilities (checked against the live crates.io
  category list; there is no version-control category anywhere in it)
• keywords — vcs, version-control, dvcs, patch, merge
• documentation — a per-crate https://docs.rs/<crate> link
• homepage — previously set on one crate of eight

The project has a front page

https://prikk-vcs.github.io/prikk/ now serves a landing page, and the documentation moved to
https://prikk-vcs.github.io/prikk/docs/. Existing links to the book need /docs/ inserting;
links to the site root still work and now land on the front page.

This shipped when it was published, not with this tag — it is noted here because the URL moved.

Also in this release

• CONTRIBUTING.md, describing how work is actually reviewed in this repository.
• A Git → prikk mapping page, a
  command-correspondence table plus the four places the two models genuinely differ.
• A slimmer README.md, with the command surface, current state and repository layout routed into
  the book.
• The documentation-currency gate now reads HTML code context, so the landing page's commands are
  checked against the live command registry like every other declared page.

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> --locked

cargo 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.