create

Create — Render the Session as an Interactive Document

You are invoked via /walkthrough:create [optional focus], or auto-invoked when the user asks to visualize/recap the session. Produce ONE self-contained interactive HTML file in the house style, then offer to open it. The renderer is six references/ files (including concept-coverage.md) plus the references/components/ catalog (its index.md routes to per-group recipe files you read on demand). Load them as the steps direct.

Step 1: Scope

If an argument was given (e.g. architecture decisions), scope synthesis to that focus. Otherwise cover the whole session. If the session is trivially short, ask via AskUserQuestion (2 fixed options: "Generate anyway" / "Skip") before proceeding.

Step 2: Gather

The session transcript is the source of record — synthesize from the conversation, not from repository state. Read any source files you will cite so code locations (path:line) are real — never invent a line number; if unverified, cite path only or omit.

Step 3: Synthesize the session model

Build the structured model per references/session-model.md (title, summary, typeTags, sections[], nodes[], edges[], decisions[], files[], timeline[], metrics[], openQuestions[], details{}) BEFORE writing any HTML.

Step 4: Coverage critic

Run references/completeness.md Part 1 against the session before selecting components. Fold omitted salient items into the model; note intentional omissions for the coverage note.

Step 5: Select components

Using references/authoring-guide.md, map the model to component names, then look each name up in references/components/index.md to find its group file. Apply "omit empty, never stub". For content that fits no catalog entry, compose a bespoke component per the authoring-guide recipe + looks-native checklist. Before accepting a catalog diagram, run the authoring-guide § 1 diagram-fidelity check: cyclic / guarded nodes[]+edges[] → state / transition diagram; timed messages between actors → sequence / swimlane diagram; a shape the catalog still cannot draw faithfully → compose a bespoke diagram. Never force-fit a state machine or a message trace into a flow / architecture map.