v0.6.0: MCP server (#30) * MCP server: ask your coding assistant why a run failed tracedown mcp (stdio, extra [mcp]) exposes eight tools over the HTTP API: list_failed_runs, explain_run, get_step, suggest_fixes, check_replay, check_claims, list_incidents, diagnose_trace. Plain-text answers that say verdicts are ranked suspects. Tests cover each tool on the demo runs and a real MCP session over stdio. Docs: docs/mcp.md, README, wiki. * MCP server: fixes from end-to-end testing and review - run ids with / ? # % or spaces are refused (the server decodes %2F before routing); other ids are quoted - the API key is not sent on to a redirected host - every failure is a tool error with a plain sentence; 401 says how to set TDN_API_KEY; non-Tracedown replies and bad --endpoint values are explained - explain_run falls back when the key may not run analysis - get_step reads one step's payloads instead of the whole bundle - read-only hints on tools; quieter logs; works with mcp 1.x and 2.x - docs: permissions per tool; tests for each of the above * MCP server: keep the API key on same-host redirects; tests pass on mcp 1.x and 2.x * Release 0.6.0: MCP server Version 0.6.0 in every package; wiki roadmap: 0.5.0 and 0.6.0 done, proven fixes in TypeScript moves to 0.7.
Wiki: keep the pages in wiki/ and publish them with a workflow README and CONTRIBUTING link the wiki; the roadmap drops the hosted demo (live since 0.4.2) and shows proven fixes in progress.
Wiki: understand, contribute, run and maintain