feat(reader): show workflow kit on chapter pages

workflows/chapter-structure.md

@@ -25,6 +25,7 @@ This is the blank chapter, matching PRD §5.4 (locked 2026-08-31). Review the sh
 - Method shows real tool output, not a description of it.
 - Nested recipes stay open. Do not hide Method behind "click to reveal."
 - Every recipe has a stable ID and a heading it can link to.
+- Every recipe names its kit (who runs it, tools, files, model, time, cost, artifact). The chapter page shows the union at the top and the kit on each nested recipe.
 - No chatbot on the page. No crypto or Web3 language.
 - PDF must match this stack: essay + in-place recipes.
 
@@ -53,6 +54,16 @@ Fill every `[bracket]`. Two nested recipes are shown so the essay-wraps-workflow
 
 **Skip to a Try-it:** [XX-01](#xx-01) · [XX-02](#xx-02)
 
+## What you need
+
+The chapter page shows this before the essay. Union of the nested workflows. Named tools, sample files, Try-it time, sample-run cost. No live client data.
+
+- Tools: [named]
+- Files: [named samples we ship]
+- Model: [named, or "the model you already use"]
+- Time: [each Try-it]
+- Cost: [sample-run total, or "unknown"]
+
 ## [Essay: the stakes]
 
 [Why this work is hard here. Specific to the vertical, not a generic AI preamble. Name the actual failure: a listing that stalls, a client file that leaks, a committee that will not move.]
@@ -73,6 +84,18 @@ Fill every `[bracket]`. Two nested recipes are shown so the essay-wraps-workflow
 
 **XX-01** · v0.1 · ~[N] min · ~$[cost or "free with tools you already have"]
 
+#### Kit
+
+Shown at the top of the nested recipe. Inventory, not instructions. Setup below still explains how to use these.
+
+- You run: [role]
+- Tools: [named tools, versions if it matters]
+- Files: [sample files we ship]
+- Model: [named, or "the model you already use"]
+- Time: ~[N] min
+- Cost: [amount or "free with tools you already have"]
+- You produce: [artifact]
+
 #### Problem
 
 [The real task. One job, not a category.]
@@ -139,6 +162,18 @@ Ordered steps. Paste the actual tool output inside the step that produced it. A
 
 **XX-02** · v0.1 · ~[N] min · ~$[cost]
 
+#### Kit
+
+Shown at the top of the nested recipe. Inventory, not instructions. Setup below still explains how to use these.
+
+- You run: [role]
+- Tools: [named tools, versions if it matters]
+- Files: [sample files we ship]
+- Model: [named, or "the model you already use"]
+- Time: ~[N] min
+- Cost: [amount or "free with tools you already have"]
+- You produce: [artifact]
+
 #### Problem
 
 [ ]