RELEASE-BLOCKER: @netscript/mcp fails live validation — telemetry adapter normalizes real Dashboard data to zero; doctor breaks its own output contract; docs tools empty in default composition

[rickylabs]

Pre-first-publish live validation (2026-07-17, .llm/runs/beta10-cli--orchestrator/slices/mcp-live-validation/report.md) against a real scaffolded running app (58/0 scaffold.runtime, fresh worker execution, Dashboard provably serving 2 resourceSpans / 26 spans) — verdict HOLD:

1. Telemetry adapter response-shape incompatibility (7 tools affected). /api/telemetry/spans?limit=100 returns {data:{resourceSpans:[…]},totalCount,returnedCount} with live spans, but the MCP telemetry adapter normalizes it to zero resources/spans/runs. get_app_status, list_runs, get_run, get_recent_errors, get_last_job_result, analyze_service_performance, analyze_db_bottlenecks all return contract-shaped false-empty results. Unit tests pass because they consume fixtures — the fixture shape does not match the live Dashboard API (Aspire 13.4.6).
2. doctor violates its own output schema live: JSON-RPC -32603 invalid_tool_result, $.checks must contain at most 20 items — the real check count exceeds the tool's declared cap; the server rejects its own flow output.
3. Docs tools unusable in the real scaffold default: corpus resolves to <project>/docs/site (unpopulated in scaffolds) → list_docs/search_docs return zero, get_doc → doc_not_found. Needs a working default (embedded corpus, --docs-root default to the installed package's docs, or documented behavior).

Correct paths (regression-guard them): initialize/tools/list (13 tools), execute_command allowlist both directions (plugin list OK, deploy denied pre-spawn), list_commands populated.

Acceptance

• Telemetry adapter parses the live Dashboard shape (fixtures regenerated FROM a live capture, so fixtures can't drift silently again); all 7 tools return real data against a running scaffold.
• doctor output fits its contract (aggregate/paginate or raise cap deliberately) — proven live.
• Docs tools have a working default composition in scaffolded projects (or an explicit, documented, non-silent fallback).
• Live validation re-run end-to-end → SHIP verdict recorded before @netscript/mcp's first publish.

Blocks the v0.0.1-beta.10 publish (release PR #801 held).

[rickylabs]

Acceptance complete — all four boxes ticked with live evidence (.llm/runs/beta10-cli--orchestrator/slices/mcp-live-validation/report.md, three rounds):

1. Telemetry adapter parses the live Dashboard shape — round 2: 11 resources / 100 bounded spans normalized from the raw Aspire 13.4 envelope; list_runs → real run resolved end-to-end (get_run, get_last_job_result found the triggered health-check completion); non-zero analyze_service_performance. Fixtures regenerated from a provenance-stamped live capture (PR fix(mcp): clear live validation release blockers #809, fb87169c).
2. doctor fits its contract, proven live — round 2: valid structured result, four family summaries, no -32603; round 3: the false plugin-registry diagnostic fixed (418efd69) — doctor now passes on the canonical green scaffold (per-plugin registry layouts recognized).
3. Docs tools work in the default composition — round 2: shipped corpus searched/listed/retrieved without --docs-root; explicit non-silent empty state verified in code (eval finding).
4. Live validation re-run → final verdict SHIP (round 3, scoped confirmation on 418efd69; command-policy paths green in every round).

Closes via PR #809's merge.

🤖 Generated with Claude Code