Multiplayer Coordination Dashboard Parity

Multiplayer coordination dashboard parity

The multiplayer coordination dashboard is a read-only composition hub for reference trace summaries, live export maturity, conformance profile posture, and optional operator-runtime conformance. It labels reference corpus rows as reference_corpus and runtime export as code_backed; it does not authorize coordination or mutation.

Maturity: Maintainer-facing reference surface. Use it for remote inspection, automation, and parity checks across HTTP, CLI, agent, MCP, and TUI access.

Surfaces

The same payload is available through:

• HTTP: GET /v1/multiplayer-coordination-dashboard
• CLI: bmo stigmergy multiplayer dashboard --json
• In-agent tool: get_multiplayer_coordination_dashboard
• MCP: bmo_get_multiplayer_coordination_dashboard (when stigmergy read tools are enabled)
• TUI: /multiplayer_dashboard (uses the active session id when present)

The HTTP route and in-agent tool call App.MultiplayerCoordinationDashboard in internal/app/multiplayer_coordination_dashboard.go.

Request controls

Optional session scope for the operator-runtime section:

• HTTP query param: session_id, recent_runs_limit
• CLI flags: --session-id, --recent-runs-limit
• Tool / MCP params: session_id, recent_runs_limit

Omitted session_id returns reference traces and export maturity only.

Authentication

GET /v1/multiplayer-coordination-dashboard is a protected route. Send Authorization: Bearer <token> when the server is configured with an auth token (same as other /v1/ parity routes).

Canonical fields

See multiplayer-coordination-dashboard.md for schema version, maturity labels, warnings, and coordination posture notes.

Relationship to runtime features

runtime_features distinguishes the two access paths:

• multiplayer_coordination_dashboard_api
• multiplayer_coordination_dashboard_tool