v0.3.0-dev.1 — gates, edits, watch and delivery drafts

Preview: checks, edits, progress and delivery drafts on top of project continuity. Pre-release, single-user, Linux x86_64 (and WSL2). One static binary.

New since v0.2.0-dev.1

• Gates with pinned receipts. writfold kb gate run | status | verify | lines | attest | waive. A gate is a small TOML file under .writfold/gates/ naming a command and the paths it covers. gate run records one receipt per evaluation in the current run, pinned to the exact bytes of the paths in scope. gate status derives each gate's state on every read: open, satisfied, stale, failed, unknown, attested or waived. A timeout or crash is never a pass, and a hand-written receipt counts as invalid. gate verify re-runs a recorded command at its recorded commit. Writfold's own pushes to main are now gated this way.
• Splicery edits in a run. writfold kb edit apply RECIPE.spl … replays recipes against the run's worktree (uncommitted edits included), refuses everything if any recipe or file fails, writes each file atomically with a re-check, and records an edit receipt. A crash between files leaves a journal; writfold kb edit recover finishes the batch.
• writfold watch. A read-only terminal view of runs, checkpoints, gate states, receipts and drafts, built only from the same verbs. --once prints one frame as text.
• Delivery drafts. writfold kb deliver prepare | check | status | attest | waive: a PR comment or Slack summary is kept in the run as the exact candidate payload, checked for paragraph length, references denied for the audience, and fresh citations. Editing a candidate makes its checks stale. Nothing is ever sent.
• Optional guard. A Claude Code PreToolUse hook, off unless configured, that denies a listed publishing command unless a ready candidate holds the exact bytes. It is a guard, not enforcement.

Install

curl -LO https://github.com/writfold-dev/writfold/releases/download/v0.3.0-dev.1/writfold-x86_64-linux-musl
curl -LO https://github.com/writfold-dev/writfold/releases/download/v0.3.0-dev.1/writfold-x86_64-linux-musl.sha256
sha256sum -c writfold-x86_64-linux-musl.sha256
install -m 755 writfold-x86_64-linux-musl ~/.local/bin/writfold
claude plugin marketplace add writfold-dev/writfold
claude plugin install writfold@writfold

How we know

• Golden tests, kill tests at every write step of receipts, edits, candidates and checkpoints, and "remove the check, a test fails" for each staleness and re-check rule.
• The release commit passed quality and unit through writfold kb gate run; the receipt lines are in the commit message.

Limits

• Single user, cooperating: receipts resist mistakes, not adversaries; tampering shows in Git history and gate verify. Nothing is signed.
• Nothing is sent anywhere; there are no Slack or PR adapters.
• MCP, trailer and tracker edges, and --at are planned.