stabbur 0.10.8

Documentation only. No behavior changes — upgrade if you read the docs, skip it
otherwise.

The project flow is written down

Getting started now walks what a project actually is: stabbur init for a new
directory that owns its model, voices, tools and config; uv sync for its
environment; stabbur configure to change any of it later. It says what init
downloads before you run it — roughly 12 GB with the recommended model, 5 GB with
none — that a model is optional, and that every project ships a fully documented
stabbur.example.toml.

stabbur configure had existed since 0.10.3 in the CLI reference alone, which is not
where anyone learns that a command exists. It is in the README's command list now.

The reference is complete again

stabbur benchmark has its own page but was missing from the CLI reference, so the
reference was not the full list it claims to be. Two guides — browser session auth and
the WebMCP assessment — were in the repository and in no navigation, so the built site
never linked them. Both fixed, and the completeness is now checked against the
program's own command list rather than by reading.

Corrections

The contributor notes still described project init as scaffolding into the current
directory and warning about nesting. It has created a new directory, and refused an
existing one, since 0.10.2.

uv tool upgrade stabbur