stabbur 0.10.3

A project is now self-contained in the way 0.10.2 claimed it was — and you can change
one after you have made it.

stabbur configure

Run it inside a project to change what stabbur init asked once, now that you know
what you are building. Four tabs:

• Assistant — the bound model (the project's own chat models, plus curated ones it
  can download) and the system prompt.
• Tools — the MCP servers in .mcp.json, pre-checked, space to toggle.
• Voice — the reply voice, whether the Voice surface shows at all, and which voice
  models the project holds.
• Library — what is on disk with sizes, selectable for removal.

Nothing is written or downloaded until you save; escape leaves the project untouched,
and a save you did not touch changes nothing. It writes stabbur.toml and .mcp.json
first and does the downloads and deletions after, so an interrupted pull cannot cost
you the settings.

A project runs its own model

A machine-wide chat_server (stabbur config set server) applied to every run,
including inside a project. So a project that had just downloaded its own copy of a
model attached to a remote instead and ran someone else's build of it — the manifest
said one thing and the session did another.

Inside a project that names a model, that default is now ignored and the project's own
model loads, saying so rather than silently. An explicit --server still attaches: the
project beats the default, not a request.

A project's tools are its own

This changes behavior. The machine-global ~/.config/stabbur/mcp.json and a
project's .mcp.json used to merge. A project whose file named three servers therefore
answered with twenty-two, and the same project answered differently on another machine,
because the extra tools came from the machine and did not travel with the directory.

A project's .mcp.json is now the whole toolset. Outside a project the machine set
applies, unchanged — that is what free-play stabbur chat runs with.

If you relied on machine-global servers inside a project, add them to that project's
.mcp.json (stabbur mcp add <name>, or the Tools tab in stabbur configure).

If you are upgrading

The tools change is the one to know about; everything else is additive. Nothing moves on
disk, and no existing model or library is touched.

uv tool upgrade stabbur