Web Debug MCP 0.8.0

Web Debug MCP 0.8.0

0.8.0 makes local MCP startup recover from bounded, identity-verifiably stale registry debris and makes an explicit Web Debug request fail closed when the current Codex task does not own the bundled tool binding. The public MCP catalog remains exactly 13 tools.

Highlights

• Reconciles dead or PID-reused registry records plus exact stale .json/.lock/.tmp artifacts before ordinary admission caps, without signaling during startup repair.
• Removes bounded old orphan sidecars left by abrupt shutdown while retaining live, malformed, recent, unknown, and identity-unverifiable state.
• Emits concise one-line startup diagnostics on stderr and keeps MCP protocol stdout clean.
• Advances doctor output to schema 3 with separate registry readiness and explicit client-binding: warn; only a real bundled web_project_detect call proves Gate 0.
• Makes the Web Debug workflow stop with MCP_CLIENT_BINDING_UNAVAILABLE or MCP_SERVER_STARTUP_UNAVAILABLE instead of substituting Playwright, Puppeteer, raw CDP, another browser connector, a direct MCP SDK client, a naked server, or cleanup.
• Documents the supported Codex Restart/new-task recovery boundary and the direct config.toml required = true strict-host option without adding unsupported plugin manifest fields.

Security and compatibility

Startup reconciliation deletes only owner-only, exactly named registry artifact families after a dead process or PID/start-identity mismatch is established. It never signals a process. The cleanup command retains its separate locked, live-identity signal authority. The normal post-reconciliation registry caps remain 128 entries and 64 records; the bounded recovery envelope handles at most 192 exact record/sidecar entries and 64 records.

Codex CLI 0.152.0 or newer is the documented host baseline for MCP tool availability through cache refreshes and plugin changes. Older hosts remain candidate-only for task-binding recovery. A successful package or doctor check is not evidence that an already-running task refreshed its tool namespace.

Verification

The stable release gate covers deterministic tests, source/test typecheck, build, native harness, three skill validators, plugin validation, production audit, exact stdio tool/schema handshakes, Node 20/22/24 archive execution, public-registry installation, and installed Codex plugin/MCP verification. Exact immutable archive, tag, npm, GitHub, and installed-plugin evidence is recorded in the completed release-0-8-0 ExecPlan.