TASK-C02: Scenario Pack

• Status: Ready
• Scope Type: Hands-on training content
• Recommended Model Tier: Balanced
• Recommended Reasoning: Medium

Objective

Write the first scenario pack so a newcomer can run the app and learn by observing behavior instead of reading design docs first.

Scope

Create scenario pages for:

1. happy path inspection run
2. stop versus abort
3. fault injection and recovery
4. recipe refresh and load
5. run history and simulator profile comparison

Non-Scope

• deep architecture explanation pages
• broad rewriting of lessons
• finished Draw.io assets

Expected Structure For Each Scenario

Each page should include:

• why the scenario matters
• steps to run in the app
• expected UI and state transitions
• code hotspots to inspect afterward
• common mistakes or confusing points
• related lessons and specs
• one short diagram brief section

Files To Read First

• docs/specs/SLICE-001-first-strong-vertical-slice.md
• docs/specs/SLICE-002-persistent-run-history.md
• docs/specs/SLICE-003-json-recipe-file-management.md
• docs/specs/SLICE-004-operational-maturity.md
• docs/implementation/SLICE-004-POST-IMPLEMENTATION-REVIEW.md
• relevant UI and application services as needed

Verification

• links resolve from the scenarios index
• each scenario references actual implemented features
• npm run docs:build

Copy/Paste Prompt

You are working in C:\Lcn.Workspaces\lcn-wafer-inspection-desktop.

Audience: a newcomer software engineer or automation engineer learning this project.
Goal: turn this repo into a high-quality engineering training course, not just reference docs.
Style: practical, detailed, blog-quality English; clear headings; concrete examples; no fluff.
Ground all claims in the repo docs and code. Do not invent behavior that the current project does not support.
Prefer reusing and linking existing content under docs/lessons, docs/specs, docs/tasks, docs/adrs, docs/implementation, and the source code when helpful.
For diagrams, do not generate binary assets. Instead, produce a Draw.io-friendly diagram brief: title, purpose, nodes, edges, grouping, caption, and destination file path.
If you edit docs, keep VitePress navigation coherent and make sure npm run docs:build passes.

Task: Write the first scenario-based training pack for this repo.

Create under docs/scenarios:
- index.md
- scenario-01-happy-path.md
- scenario-02-stop-vs-abort.md
- scenario-03-fault-injection-and-recovery.md
- scenario-04-recipe-refresh-and-load.md
- scenario-05-run-history-and-profiles.md

Each page must include:
- why this scenario matters
- step-by-step operator actions
- expected UI and state changes
- what code or services to inspect after running it
- troubleshooting notes
- related lessons and specs
- a small Draw.io-friendly diagram brief

Keep the writing grounded in the current implemented slices.
Verify with npm run docs:build.