> ## Documentation Index
> Fetch the complete documentation index at: https://smithers.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# report-slideshow

> Generate a concise HTML slideshow report from a Smithers run state and artifacts.

`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.

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
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.

## Stages

1. **gather**: deterministic capture via `bunx smithers-orchestrator inspect RUN_ID`, flattening the run state, nodes, and a summary (no agent).
2. **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

| Input         | Type           | Default                                               |
| ------------- | -------------- | ----------------------------------------------------- |
| `targetRunId` | string         | (required) the Smithers run id to report on           |
| `title`       | string or null | `null` (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`.