TASK-C06: Learning Path and Extension Playbook

• Status: Ready
• Scope Type: Onboarding and safe-contribution guidance
• Recommended Model Tier: Balanced
• Recommended Reasoning: Medium

Objective

Create the newcomer learning path and the extension playbook so a learner knows both how to study the system and how to change it responsibly.

Scope

Create course modules for:

• system tour and happy path
• domain and state model
• architecture walkthrough
• extending the system safely

The extension playbook must explain:

• how requirements, ADRs, specs, tasks, and tests fit together
• how to add one bounded feature slice
• what mistakes to avoid when using AI coding tools
• which docs to read before touching UI, runtime, or infrastructure

Non-Scope

• new product slices
• deep architecture rewriting
• replacing the existing implementation workflow docs

Files To Read First

• docs/requirements.md
• docs/adrs/index.md
• docs/specs/index.md
• docs/tasks/index.md
• docs/implementation/index.md
• docs/implementation/ROADMAP.md

Deliverables

• docs/course/01-system-tour-and-happy-path.md
• docs/course/02-domain-and-state-model.md
• docs/course/03-architecture-walkthrough.md
• docs/course/07-extending-the-system.md

Verification

• the reading order is coherent for newcomers
• the extension playbook matches the repo’s real workflow
• 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: Create the newcomer learning path and feature-extension playbook.

Create:
- docs/course/01-system-tour-and-happy-path.md
- docs/course/02-domain-and-state-model.md
- docs/course/03-architecture-walkthrough.md
- docs/course/07-extending-the-system.md

The extension playbook must explain:
- how requirements, ADRs, specs, tasks, and tests work together
- how a newcomer should add one bounded feature slice
- what mistakes to avoid when using AI coding tools on this repo
- which docs to read before editing runtime logic vs UI vs infrastructure

Also add a short learning-path section for:
- operator-minded learner
- .NET or WPF developer
- architecture-focused learner

Verify with npm run docs:build.