report-slideshow is an archived example, not installed by init. Copy it from examples/init-pack/ with its dependency closure, or ask create-workflow for one, then run it:
report-slideshow turns a finished (or in-progress) Smithers run into a single,
self-contained HTML slideshow report you can share without scrolling the
event log.
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.
Stages
- gather: deterministic capture via
bunx smithers-orchestrator inspect RUN_ID, flattening the run state, nodes, and a summary (no agent). - render: an agent writes a self-contained, dependency-free HTML slideshow (inline CSS, no scripts, open or attach anywhere) covering the title/objective, decisions, workflow graph, artifacts, tests/gates, failures/retries, and remaining issues.
Inputs
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.