[Serraniel]

Two commits, reviewable separately.

1. docs: correct claims that the project was never released

Six files said Sendan has no published release. Seven exist; the claims have been false since v0.1.0 was tagged on 31 August. These were not harmless — the worst of them tells a reader that the project's headline guarantee does not work:

Nothing published carries these signatures yet. v0.1.0 is tagged, but the workflow that builds and signs its artefacts was never started, and the release keys do not exist. — SECURITY.md

Checked before removing it. The v0.3.3 manifest verifies under both documented keys:

$ minisign -Vm manifest.json -P 'RWQt826yhqM+nKsvcrv1lu/eePUVXmE2haeCmGUBpgzwu7CWVZxyRUVk'
Signature and comment signature verified
Trusted comment: sendan v0.3.3 client asset manifest

$ go run ./tools/pq-sign verify release.pqpub manifest.json
manifest.json: signature verified

Both match the constants in cmd/sendan-cli/verify.go, so the note was wrong about the keys existing too.

docs/design.md opened with "This document describes software that has not yet been implemented." It is the first row of the README's documentation table, so that was the first thing a reviewer of the design read.

Two real bugs fell out, not just stale prose

Image tags carry no v	the registry holds 0.1.0 … 0.3.3 and zero v-prefixed tags, so cosign verify ghcr.io/serraniel/sendan:v0.5.0 was wrong in form as well as version — it would have failed for anyone substituting a real release. compose.yaml now records the convention where somebody pinning a deployment reads it
docs/cli.md asked for Go 1.25	go.mod requires 1.26.0, so the documented build could not work on the version it named

v0.5.0 placeholders are replaced by a $VERSION variable rather than another literal, so the snippets stay copy-pasteable from one edit.

2. docs: give the README an install path

There wasn't one. Headings ran Try it → Features → Cryptographic design → … → Security; anyone wanting to run Sendan had to reach docs/deployment.md through a table two thirds down, and until commit 1 that document opened by saying no image existed.

Adds Run it between Try it and Features: a single docker run for a local trial, compose.yaml for a real deployment with the reason the first isn't one (links come from SENDAN_BASE_URL; streaming needs HTTP/2, so TLS), the :0.3.3-not-:latest pin, and the CLI with the checksum step included rather than left as an exercise.

Both commands were run, not transcribed. The published image starts with no configuration at all:

{"msg":"metadata store ready","location":"sqlite:/var/lib/sendan/sendan.db"}
{"msg":"blob store ready","location":"file:/var/lib/sendan/blobs"}
{"msg":"reaper started","interval":"5m0s","batch":500}
{"msg":"listening","addr":":8080"}
GET /            200, 2617 bytes
GET /api/source  200, v0.3.3

Both documented download URLs return 200.

Also corrects the sendan verify sample in Try it, which showed v0.3.0 and 31 assets. The demo reports v0.3.3 at a5fbc01 and that manifest carries 33 assets, so the numbers are now reproducible against the live demo.

Note

Touches README.md in the same file as #332, which adds a documentation-table row. Whichever merges second may want a trivial rebase.

🤖 Generated with Claude Code