v1.5.0
Starting instances are now visible and stoppable (ADR-0010). A server still loading its model (answering 503) used to be invisible to every command; now discovery reports it, status and the interactive menu show it as starting… (with "starting": true in status --json), and stop/unload kill the in-flight load. A plain load onto a Starting address refuses with guidance, while load --restart displaces it. Stop verification no longer reports success when a still-loading server survived the stop.
Also in this release:
- A build-tagged integration-test layer drives the real backends end-to-end (
make test-integration, plus newmake test/make test-alltargets); the suite bypasses Go's test cache so a green run always means real servers ran. - The MCP adapter's
server_status,stop_server,tail_log, andunload_modeltool descriptions now document the Starting state (no behaviour change — the adapter inherits the new semantics from the CLI). llama-launcher configusage now lists all three subcommands (validate,init,reset).- Doc corrections:
make installdocs no longer claim a~/.local/bincopy (it points at Homebrew), stale ADR references and line drift fixed.
See CHANGELOG.md for the full details.