docs/opencode.md now says that runs need OpenCode 2.x, that the install script and npm's `opencode-ai` still give 1.x, and that 2.x comes from npm's `@opencode/cli`, the desktop app's bundled CLI or the GitHub releases, with how to point the backend at it. It also warns not to start OpenCode during a build, since its shared service takes over the build's session. STATUS.md records the Linux live runs, and the roadmap gains the two problems they found.
OpenCode model discovery, which also runs before every OpenCode turn, now uses --standalone unless the person chose a --server. Plain opencode api started OpenCode's shared service, which resumes every unfinished session on the computer, in any project, and carries on with its commands.
Part of #1115.
The older, cut-off copy of the standalone-server sentence in opencode.md's configuration section goes; the newer copy, which also says where the file goes over SSH, stays.
Five STATUS rows that merges had kept twice, with different updates in each copy, are now one row each, the most complete copy (OpenCode models and thinking now says once that SSH runs get the tools), and opencode.md loses its older doubled paragraph. A pitfall says how to merge a conflicting table row.
A stopped, failed or timed-out OpenCode turn deletes the session it started, so OpenCode's own service can't resume it later. A turn records its session while it runs, so one left by a killed app is deleted at the next turn or by doctor, on this computer or over SSH.
Part of #1115. Includes #1176.
One ssh run checks `craft-anything-cli` on the host and writes the private config file there, and the run reads it through `OPENCODE_CONFIG`; a build checks this first. Refs #481.
A run with an explicit OpenCode model or thinking choice used to be refused. The adapter now writes our MCP server to a temp config file named by OPENCODE_CONFIG and runs `opencode run --standalone`, and reads OpenCode V2's tool call ids so tool calls reach the feed. Runs over SSH still have no Craft Anything tools.