codebase-to-courselisted

# Codebase to Course Turn a real codebase into a factual, interactive HTML course for a reader who needs to understand and change the system, not memorize terminology. ## Routing This Skill owns a course artifact whose subject is a codebase. - Use `quick-learn` for multi-session teaching, assessment, and durable learner progress. - Use `code-review` for findings about correctness or maintainability. - Use `source-post` for a public article. - Use `frontend-slides` for a presentation. - Use `web-artifacts-builder` only when accepted course interactions genuinely need an application framework rather than a self-contained document. Do not combine those outputs by default. A course is a learning artifact, not a review report with quizzes attached. ## Evidence Contract Inspect before explaining: 1. Read the repository contract, README, entry points, configuration, tests, and the smallest set of implementation files needed to trace one representative user or operator journey. 2. Identify the system's real actors, ownership boundaries, data movement, external dependencies, and one meaningful failure or debugging path. 3. Separate observed facts from inference. Every implementation claim in the course must point to a current repository-relative file and line or symbol anchor. 4. Use only short, exact source snippets. Do not simplify source code and present the result as verbatim code. 5. Exclude credentials, secrets, customer data, generated vendor trees, and unrelated propri