Read-only grid-status MCP server for live pipeline observability

[WilfordGrimley]

Build a small read-only MCP (Model Context Protocol) server exposing live pipeline state as typed tools, authored with the mcp-builder skill (owner has it on claude.ai; install into ~/.claude/skills/ on the server to use in Claude Code sessions).

Candidate tools (finalize after streaming shakedown shows which counters matter):

• review-queue size + resolved-printing count (live, dedup'd)
• PilotRunLedger recent rows / outcomes (incl. throttled + halted counts once observable)
• envelope state: current_trip(), recent trips, envelope signal samples
• Stage E streaming status: flag, micro-batch config, concurrency cap, recent dispatch outcomes

Motivation:

• Tron's Add Stage E streaming dispatch concurrency cap #450 gate anomaly 4: throttled dispatches emit only logger.info — no queryable signal for shakedown tuning (the runbook's own first tuning knob).
• Every session re-derives docker-exec ORM one-liners for the same status queries; typed tools kill that repeat cost.
• As a remote connector it can give owner-side claude.ai/phone sessions live pipeline visibility, pairing with the Signal workflow.

Constraints: strictly read-only (no authorization-gate surface); index-not-store unaffected (metadata only); defer build until post-#450 shakedown so the tool list is driven by measured needs, not guesses.