feat(acp): move five pinned agent CLIs to their current releases

Cline 3.0.60 to 3.0.61, OpenCode 1.18.25 to 1.18.26, Kimi Code 0.39.1 to 0.40.1,
Qoder 1.1.40 to 1.1.41, Cursor 2026.08.11-e8db854 to 2026.08.31-4057e58. Each npm
package's declared `engines.node` still matches its `node_required` floor, and
every distribution the registry describes resolves under the new pins.

Cline ships its real binaries as optional per-platform dependencies that npm
skips in silence, so all six `@cline/cli-<platform>` packages are confirmed
published at 3.0.61; the wrapper itself only gains a Windows application-control
diagnostic. OpenCode publishes all six pinned platform assets under the new tag
and each archive still holds a bare `opencode`, so `dir_entry` stays `None`.
Cursor's six release paths all resolve, the tree still carries
`dist-package/cursor-agent` beside its bundled Node, and the entry reports the
pinned build itself.

Kimi stays clear of the 0.37.0-0.38.0 hole, where any stdio MCP server killed the
session outright: its converter still reads an absent transport as stdio and
supplies the runtime_id itself, so the codeg-mcp companion rides every session.
Its bundle shrank because 0.40.0 deleted a stale duplicate ACP server class, not
because anything was lost — the live handshake still advertises list, resume,
close, delete, fork and additionalDirectories. Reading capabilities off the first
match in an older bundle landed on that dead copy and its narrower set, so the
entry now says which class carries the live answer. Qoder's config-dir resolver
keeps its precedence, keys and `.qoder` default, and Kimi's mcp.json schema is
unchanged beneath the new pins; the comments mirroring both now name the version
they were last checked against.