surface plugins

by Lauri Gates

Project infrastructure standards - comprehensive project configuration for pre-commit, CI/CD, Docker, testing, linting, formatting, and more

by Job Schepers

A headless run surface: where a run becomes recorded rather than watched. An MCP server implementing two surface capability groups — lifecycle (open_dashboard, start_run, record_prompt, set_run_context, update_stage, finish_run, list_runs, get_run) and export (export_report) — keeping stage status, output, gate decisions, QA scenarios and the handoff marker on disk so a resumed session picks the run up where it stopped, and writing the run's Markdown report at the end. No page, no port, nothing rendered: the right surface for scheduled and unattended runs. Declares no dependency and names no engine.

by Job Schepers

A run surface: the live dashboard a run is watched in. An MCP server implementing all three surface capability groups — lifecycle (open_dashboard, start_run, record_prompt, set_run_context, update_stage, finish_run, list_runs, get_run), render (render_diagram, render_markdown), and export (export_report) — with a run timeline carrying stage output, QA scenarios and their evidence, a Mermaid diagram viewer and a Markdown document viewer, and hook-captured tool and token telemetry. Rendered inline as an MCP App where the host supports it, served on 127.0.0.1 where it does not. Declares no dependency and names no engine.