Skip to main content
report-slideshow turns a finished (or in-progress) Smithers run into a single, self-contained HTML slideshow report. Reach for it after a run when you want a shareable summary (objective, decisions, the workflow graph, artifacts, tests and gates, failures and retries, and remaining issues) without scrolling the event log. 
bunx smithers-orchestrator workflow run report-slideshow \
  --input '{"targetRunId":"RUN_ID","title":"Nightly build report"}'
The input is targetRunId, not runId: the engine reserves input.runId for a run’s own id, so a workflow that reports on another run needs a distinct name. It first captures the run deterministically with bunx smithers-orchestrator inspect, then an agent renders a dependency-free HTML document (inline CSS, no scripts) you can open or attach anywhere.

​
Stages

  1. gather: deterministic capture. Shell bunx smithers-orchestrator inspect RUN_ID and flatten the run state, nodes, and a summary (no agent).
  2. render: an agent writes a self-contained HTML slideshow covering the title/objective, decisions, workflow graph, artifacts, tests/gates, failures/retries, and remaining issues.

​
Inputs

InputTypeDefault
targetRunIdstring(required) the Smithers run id to report on
titlestring or nullnull (the render step derives a title from the run)
The rendered HTML is the html field of the render node output. Read it with bunx smithers-orchestrator inspect RUN_ID or bunx smithers-orchestrator output RUN_ID --node render.