release: v0.5.9 notes — add #1004

[maxy-player]

Adds a section for #1004 to the existing ## v0.5.9 notes. Notes only — one file, one section.

Commit range read: b9ee77f1..00c05bb8 (60 entries including the merge commit; #1004 merged
09:49Z on 16 Sep by @pmilic021), plus the #1004 PR body. Base commit for this branch is exactly
00c05bb8, off a fresh fetch of MakePrisms/main.

What the section says

The two automated routes (Proxy swap, [[sandbox.mcp_tools]]; Holder,
[[sandbox.held_tools]]), the manual and unsupported routes, the routing tree and skill paths, the
driver/acp.rs McpServer wire shape, and the two shipped limits (Docker Engine 26+ for the volume
subpath mount; the proxy constrains the destination host, not the operations).

Live validation and source-level checks are stated separately, because they are not
interchangeable:

• Proxy swap is named as validated live against a third party — 2026-09-14 against GitHub's
  remote MCP server, real proxy, real launch, real claude-agent-acp turn — and the bounding
  credential (fine-grained, read-only, public repositories, read-only endpoint) is named as what
  bounded the job, not the proxy.
• Holder is named as a live run of the mechanism with the kit's fakes standing in for the vendor,
  with "no real vendor CLI was exercised" stated explicitly, matching the limit its own bundle
  README records (evidence/20260914T103608Z-holder-route-two-tools/README.md: "the vendors and the
  CLI are the kit's fakes").
• The routing tree, manual-setup steps and unsupported-route prints are named as source-level
  only, with no run claimed behind them.

Scope

• Historical sections are byte-identical: awk '/^## v0.5.8/,0' RELEASE_NOTES.md | md5 matches the
  same slice at 00c05bb8.
• No version pin touched. Diff is 1 file changed, 57 insertions(+), 1 deletion(-), two hunks — the
  new section and one clause added to the v0.5.9 lead paragraph so it no longer omits the release's
  largest change.

Gates at the pushed head 8d2c70f4

Worktree clean (git status --porcelain empty) and remote head = 8d2c70f4 at both ends of the run.

Gate	Result
scripts/verify-release-version.sh 0.5.9 target/debug/maxplayer	exit 0 — crate, npm packages, payload pins, notes name 0.5.9; the artifact arm ran: binary answers maxplayer 0.5.9 (8d2c70f4…) on both dispatch forms and its build stamp resolves to this tree's HEAD
scripts/verify-release-surface.sh --no-artifacts	exit 0 — npm payload, launcher optionalDependencies and resolver PLATFORM_PACKAGES match .github/release-platforms.json. The built-artifact check is skipped by that flag, as the flag says; the tree surfaces are what passed
scripts/verify-release-workflow.sh	exit 0 — no pull_request trigger, no RELEASE without a pushed tag, no quiet skip, dispatch publish reaches nothing a release can name

A bare verify-release-version.sh with no arguments exits 1 on usage; it takes <version> [path-to-binary], as CI passes it.

No tag is pushed and nothing is merged by this branch. Cutting v0.5.9 is a human act.

[vercel]

Someone is attempting to deploy a commit to the MakePrisms Team on Vercel.

A member of the Team first needs to authorize it.