[ducnmm]

The release audit of #1350 found that the MCP consent fix would be skipped by the stable publisher: source still used the already-published 0.0.17, and plugin installs still selected 0.0.16. The local integration suite also reproduced an existing SSE watchdog hang when abort did not settle a pending HTTP read.

Changes

• Prepare MCP 0.0.18 across the package, plugin/editor manifests, marketplaces and changelogs. Keep the SDK's existing 0.1.12 bump.
• Prefer the exact stable MCP 0.0.18 in the trusted launcher. While it is unpublished, permit only the explicit published 0.0.17-dev.3 bootstrap, whose npm artifact contains the consent fix. Use it only for npm's exact missing-version error for the preferred package; network, integrity, permission and dependency errors remain fatal. Once stable exists, the launcher selects it automatically. The bootstrap does not contain this PR's new SSE fix; that ships in 0.0.18.
• Wake the SSE iterator directly on abort and cancel the reader for cleanup. Reconnect no longer depends on reader.read() rejecting; test timeouts are unchanged.
• On PRs into main, reject runtime package changes without a version increase relative to the main baseline. Normal development can continue on an unpublished version. Add regression coverage for the version guard and launcher selection.
• Document the separate uploader-gas failure observed in live SDK E2E and its operator validation steps.

Validation

• MCP suite: 331 passed, 0 failed, including the existing idle-watchdog regression.
• Release verifier regression suite: 12 passed.
• Package version comparison against both dev and main passed; manifest/changelog synchronization, compatibility metadata, docs freshness and code-reference checks passed.
• Real cold launcher install from an empty trusted runtime succeeded through the exact unpublished-version bootstrap path. No package was published.
• No Rust server or SDK request implementation changes; no DB/Redis/RPC work added to remember or recall. Launcher selection runs at process startup only.

Release follow-up

After the operator topped up uploader SUI, live SDK E2E attempt 3 passed against dev: 13 passed, 0 failed, 0 skipped on 2026-10-29. The full durable remember/recall/namespace-isolation flow completed in 33.4 seconds; bulk-write cutoff and list/count checks also passed. Post-test health returned status=ok, write_ready=true. This resolves the previously observed uploader-gas validation blocker. All non-skipped PR CI jobs also passed. No wallet funding or production configuration changes were performed by this PR. Merge this fix into dev before promoting #1350; stable MCP publication remains part of the normal main release workflow.