Docs: publish ROADMAP.md (path to 1.0)

[debugmcpdev]

Motivation

Users and organizations evaluating mcp-debugger for agentic workflows ask two questions the repo doesn't currently answer in one place: is the tool surface stable enough to build on? and what's left before 1.0? A public ROADMAP.md answers both — and a published roadmap is also expected by the OpenSSF Best Practices criteria this project tracks.

Proposal

A top-level ROADMAP.md, linked from the README, dated and refreshed at each release.

Path to 1.0 (criteria, not dates):

• Tool-schema freeze: declare the 28-tool surface and response shapes stable under SemVer
• Per-platform CodeLLDB packages published and verified across install channels
• A full release cycle with no breaking behavioral changes
• Supply-chain milestones: OpenSSF Best Practices Silver, attestation coverage for every distributed artifact (Supply chain: attest the Docker image and PyPI launcher (npm tarballs already carry provenance) #422)

Near-term themes:

• Environment self-check: mcp-debugger doctor + consolidated diagnostics guide (Feature: mcp-debugger doctor — environment self-check command + consolidated diagnostics guide #423)
• Turnkey Kubernetes debugging recipe (Docs: turnkey Kubernetes debugging recipe (example manifests + attach presets) #424)
• Published-artifact canary matrix (CI: scheduled canary install-and-debug matrix across install channels and platforms #425)

Non-goals, to set expectations: an IDE-replacement UI, languages without a maintained DAP backend, editing/refactoring tools (this is a debugger).

This issue tracks writing and landing the file; the skeleton above gets refined in the PR.

[debugmcpdev]

Landed in #429 (squash ce2832a): top-level ROADMAP.md, linked from the README's Documentation list and Project Status section, dated and refreshed at each release. Path-to-1.0 criteria as proposed (tool-schema freeze incl. completing parameter/response docs for the four summarized tools in the tool reference, per-platform CodeLLDB packages verified, one clean release cycle, Silver + full attestation coverage), near-term themes #423/#424/#425, and explicit non-goals.