[skulitom]

The 0.11.3 release candidate (Compass C-058): main holds the fixes merged since v0.11.2 that users don't have yet. Version, runtime patch and release text only; no tool, command or behaviour change.

What changes

• Version 0.11.3 in src/Anode/Anode.csproj, server.json, packaging/mcpb/manifest.json, .claude-plugin/plugin.json, and docs/INSTALL.md's pinned installer example (CONTRIBUTING's release process, steps 1 and 4).
• .NET 10.0.13 (from 10.0.12): RuntimeFrameworkVersion and System.ServiceProcess.ServiceController. Microsoft released 10.0.13 on 2026-10-13 as a security update (44 CVEs, per its release metadata), and CONTRIBUTING asks for the current patch before each release. It goes in this PR because the live check and the tag use the commit that sets 0.11.3.
• CHANGELOG.md: ## Unreleased becomes ## 0.11.3 — 2026-10-15, with a runtime line and one line for the docs and release tooling ([compass] Feature: CI runs the environment self-test on GitHub's Windows runner #35, [compass] README: link the Anode Business licence now that it is on sale #40, [compass] An Anode release path the agents can run: scripts/release-check.ps1, the owner's live check as one command #43, [compass] Fix: TROUBLESHOOTING tells CLI users to pass a pace option anode type doesn't have #45, [compass] Clean up tests: quick-check waits and key names (about 2.4 s faster) #46); the log-times entry now says exactly which forms changed.
• .github/RELEASE_NOTES.md (the release body): what's new for users ([compass] Fix: anode quit leaves Anode running while the sign-in dialog is open #34, [compass] Fix: seat_key refuses the backtick key under the names agents try, and ctrl++ presses ctrl alone #36 to [compass] Fix: anode selftest writes its stand-ins' made-up launches and failures into the user's log #39, [compass] Fix: log timestamps follow the Windows culture (Thai year 2569, Finnish 23.34.16) #41, [compass] Fix: a detached seat can't be reconnected by the button its message names, and agents aren't told capture is down #42, [compass] Fix: a display change that ends during a stop reports the stopped seat detached #44), the known issues that are still open, validation, the runtime, and the upgrade step.
• docs/RELEASE-READINESS.md: a 0.11.3 section: scope (including [compass] Anode Business, ready to switch on: the terms and a README line that it isn't on sale yet #19, the Business licence terms, released for the first time), the checks run without a seat, where the owner's live-check summary is recorded, and coverage limits.

Not changed: bucket/anode.json and packaging/winget/* describe a published release, so they change after the tag (CONTRIBUTING step 7), as in #30.

Checks

• scripts\build.ps1 -QuickTest -Package -Mcpb on the candidate with .NET 10.0.13: 108 quick self-tests passed, the documentation check passed (41 documents, 41 tools), anode version prints anode 0.11.3, and the exe embeds the 10.0.13 runtime.
• The release workflow's own package steps (registry-entry.ps1 -Tag v0.11.3, the bundle checksum, test-distribution.ps1 -Release): all distribution checks passed.
• scripts\test-release-check.ps1 passed; scripts\release-check.ps1 -DryRun passed and names the commit that sets 0.11.3.
• Real client on the MCPB bundle (a rehearsal, see below): Claude Code 2.1.280 (-p --mcp-config --strict-mcp-config) ran the extracted bundle's server/anode.exe mcp with ANODE_CHANNEL set to a throwaway channel, so it could not reach an installed Anode. It listed 41 tools, and seat_status answered daemonRunning: false. Nothing started.
• Windows CI on the final head 13c340b (run 38706632329): build (with packaging, installation and distribution checks) and the environment self-test pass.
• Second review (a fresh Claude subagent; Codex is out until 20 Oct): one P1, fixed in eaa7ad6: the candidate still bundled .NET 10.0.12, though 10.0.13, a security update, shipped on 13 Oct. One P2 (the readiness record had no coverage limits) and five P3 wording, scope and link fixes, all applied. Its re-check found no credible problem; its last P3 (B-040's wording) is fixed in 13c340b.

After merge

1. The owner's live check (steps): build the candidate, install it, start the seat, then run powershell -NoProfile -ExecutionPolicy Bypass -File scripts\release-check.ps1. When it passes, its last line is the tag command for exactly the tested commit; run it and git push origin v0.11.3, or say "tag it".
2. The release is the tag's Release workflow. It builds the MCPB bundle as a workflow artifact.
3. The registry moves off 0.11.0 after that, not in this PR: the tag's own bundle is checked with a real MCP client, uploaded to the release, and publish-registry.yml is dispatched for v0.11.3 (Compass C-058 item 3, in place of the Claude Desktop test PUBLISHING.md names). The registry entry hashes that tag's bundle, so the pre-merge bundle check below is a rehearsal, not that gate.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-15T08:23:33.507900Z	5fc2771	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.