stabbur 0.10.7

Every project now ships the manual it was missing.

stabbur.example.toml

stabbur init writes a fully documented example beside the manifest: every option a
project understands, commented, with its default. stabbur never reads it — it exists so
the options are discoverable without going to the docs, which is where they were and
therefore where nobody found them.

Named stabbur.example.toml, not stabbur.toml.example, so an editor still highlights
it as TOML.

Remote backends, at last visible

This is the part worth knowing: a project has always been able to name several
OpenAI-compatible servers and run its models on them, and nothing said so anywhere a
user would look.

[[backends]]
name = "gpu-box"
url = "http://gpu-box:8080/v1"

[[backends]]
name = "lab-rig"
url = "http://lab-rig:1234"

Declare as many as you run; the name is how you pick one. stabbur's agent loop, tools
and UI stay local while the weights live on the other box. A single unnamed remote is
the shorter upstream = "http://gpu-box:8080/v1". A trailing /v1 is optional.

The example also documents the serving and runtime knobs — bind address, port, the
browser UI, an auth token, tool and confirm timeouts — and says plainly that tools do
not live in this file at all.

One thing to watch in TOML

Top-level keys must come above the first table: TOML binds a bare key to the table
above it, so a port uncommented at the foot of a file lands inside the last
[[backends]] entry and silently does nothing. The shipped example is ordered so that
uncommenting anything in place works.

If you are upgrading

Additive: an existing project is untouched, and nothing reads the new file. Copy one
into a project you already have with stabbur init in a scratch directory, or take it
from the repository.

uv tool upgrade stabbur