feat: implement all 45 enhancements — bespoke projects, modernization, platform tools

Transformative update implementing the full ENHANCEMENT_ROADMAP.md:

Tier 0 — Bug Fixes:
- Fix hardcoded path in tools/rebuild_navigation.py
- Fix broken elite links in 14_NAVIGATION_AND_STUDY_WORKFLOW.md
- Fix unquoted variables in shell scripts
- Add ripgrep guards to all shell scripts
- Fix XXXXX and 0.XXXs placeholders
- Extend portable path checker to scan .py files
- Correct project count from 261 to 246

Tier 1 — Quick Wins:
- Add Python Tutor visualization links to all 15 concept docs
- Create reading-error-messages.md concept doc + quiz
- Create FEATURE_UNLOCK.md progressive disclosure chart
- Create AI_USAGE_GUIDE.md with per-level AI policies
- Fix dict ordering in collections-explained.md (Python 3.7+)
- Consolidate duplicate Practice sections across concept docs
- Create 15 advanced coding challenges (Level 6+)
- Normalize quiz input handling across all 20 quiz files

Tier 2 — Strategic Content:
- Replace ALL 165 templated project.py files with bespoke code
- Replace ALL 165 templated test files with project-specific tests
- Update ALL 165 README Alter/Break/Fix/Explain sections
- Create project-specific sample data for all 165 projects
- Adopt uv as default package manager (setup guide, CI)
- Create type-hints, dataclasses, match-case, modern-tooling concept docs
- Add PR-triggered CI with ruff and py_compile checks
- Create TEACHING_GUIDE, PORTFOLIO_GUIDE, CAREER_READINESS, FAST_TRACK
- Create CHANGELOG.md, expand certification protocol
- Add shields.io badges to README

Tier 3 — Major Initiatives:
- Configure mkdocs-material GitHub Pages site with 234-page nav
- Create Pyodide browser exercises for Level 00 (CodeMirror + Pyodide)
- Create Python CI equivalents (no bash/ripgrep dependency)
- Implement SM-2 spaced repetition for flashcard runner
- Generate SVG level completion badges
- Create badge generator tool

778 files changed across the entire curriculum.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: travisjneuman

.github/workflows/curriculum-checks.yml

@@ -1,6 +1,10 @@
 name: Curriculum Checks
 
 on:
+  pull_request:
+    branches: [main]
+  push:
+    branches: [main]
   workflow_dispatch:
     inputs:
       full_smoke:
@@ -23,6 +27,21 @@ jobs:
         with:
           python-version: '3.12'
 
+      - name: Install uv
+        run: pip install uv
+
+      - name: Install ruff
+        run: uv pip install ruff --system
+
+      - name: Ruff lint check
+        run: ruff check .
+
+      - name: Python syntax check (py_compile)
+        run: |
+          find . -name "*.py" -not -path "./.venv/*" | while read f; do
+            python -c "import py_compile; py_compile.compile('$f', doraise=True)" || exit 1
+          done
+
       - name: Markdown link checks
         run: ./tools/check_markdown_links.sh
 
@@ -62,5 +81,8 @@ jobs:
         with:
           python-version: '3.12'
 
+      - name: Install uv
+        run: pip install uv
+
       - name: Full curriculum checks
         run: ./tools/run_all_curriculum_checks.sh --full

.github/workflows/deploy-docs.yml

@@ -0,0 +1,58 @@
+name: Deploy Documentation
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - "**.md"
+      - "mkdocs.yml"
+      - ".github/workflows/deploy-docs.yml"
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install dependencies
+        run: |
+          pip install \
+            mkdocs-material \
+            "mkdocs-material[imaging]" \
+            pymdown-extensions
+
+      - name: Build site
+        run: mkdocs build --strict
+        env:
+          ENABLE_PDF_EXPORT: 0
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: site
+
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.gitignore

@@ -11,3 +11,6 @@ practice/flashcards/.review-state.json
 
 # Personal learning workspace
 learning/
+
+# MkDocs build output
+site/

03_SETUP_ALL_PLATFORMS.md

@@ -143,14 +143,41 @@ mkdir -p "$HOME/python_sme/projects" "$HOME/python_sme/templates" "$HOME/python_
 - Create a `python_sme` folder in your Python app workspace.
 - Create subfolders: `projects`, `templates`, `notes`.
 
+### Step 3.5 - Install uv (recommended package manager)
+
+**uv** is a modern, fast replacement for pip and venv. It is used throughout this curriculum.
+
+#### Windows PowerShell
+```powershell
+powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
+uv --version
+```
+
+#### macOS/Linux
+```bash
+curl -LsSf https://astral.sh/uv/install.sh | sh
+uv --version
+```
+
+#### Android (Termux)
+```bash
+pip install uv
+uv --version
+```
+
+Expected output:
+- `uv x.x.x` (version number)
+
+> **If you prefer pip:** All `uv` commands in this curriculum have pip equivalents. Replace `uv venv` with `python -m venv .venv` and `uv pip install` with `pip install`. Everything else stays the same.
+
 ### Step 4 - Create first project and virtual environment
 
 #### Windows PowerShell
 ```powershell
 cd $HOME\Documents\python_sme\projects
 mkdir hello_sme
 cd hello_sme
-python -m venv .venv
+uv venv
 .\.venv\Scripts\Activate.ps1
 python --version
 ```
@@ -159,12 +186,14 @@ Expected output:
 - Prompt starts with `(.venv)`.
 - Python version prints.
 
+> **pip fallback:** Replace `uv venv` with `python -m venv .venv`.
+
 #### macOS/Linux
 ```bash
 cd "$HOME/python_sme/projects"
 mkdir -p hello_sme
 cd hello_sme
-python3 -m venv .venv
+uv venv
 source .venv/bin/activate
 python --version
 ```
@@ -173,12 +202,14 @@ Expected output:
 - Prompt starts with `(.venv)`.
 - Python version prints.
 
+> **pip fallback:** Replace `uv venv` with `python3 -m venv .venv`.
+
 #### Android (Termux)
 ```bash
 cd "$HOME/python_sme/projects"
 mkdir -p hello_sme
 cd hello_sme
-python -m venv .venv
+uv venv
 source .venv/bin/activate
 python --version
 ```
@@ -187,6 +218,8 @@ Expected output:
 - Prompt starts with `(.venv)` if your shell prompt supports it.
 - Python version prints.
 
+> **pip fallback:** Replace `uv venv` with `python -m venv .venv`.
+
 #### iOS
 - Some iOS Python apps do not support full `venv` behavior.
 - Use a project folder and keep dependencies minimal in early labs.
@@ -196,15 +229,15 @@ Expected output:
 
 Desktop and Android:
 ```bash
-python -m pip install --upgrade pip
-python -m pip install pytest
+uv pip install pytest
 pytest --version
 ```
 
 Windows note: same commands work inside activated PowerShell venv.
 
+> **pip fallback:** Replace `uv pip install pytest` with `python -m pip install pytest`.
+
 Expected output:
-- pip upgrade completes.
 - pytest version is displayed.
 
 ### Step 6 - Create first script and first test
@@ -280,9 +313,12 @@ Secret handling rules:
   ```powershell
   Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
   ```
+- `uv` not found:
+  - Re-run the install command from Step 3.5.
+  - Or fall back to pip: replace `uv pip install` with `pip install` and `uv venv` with `python -m venv .venv`.
 - `pytest` not found:
   - Confirm venv is active.
-  - Run `python -m pip install pytest`.
+  - Run `uv pip install pytest` (or `pip install pytest`).
 - macOS shows old system Python:
   - Use `python3` for install and venv creation.
 - Linux missing `venv` module:

14_NAVIGATION_AND_STUDY_WORKFLOW.md

@@ -20,23 +20,23 @@ Use this file to keep study flow clean and avoid navigation friction.
 14. [14_NAVIGATION_AND_STUDY_WORKFLOW.md](./14_NAVIGATION_AND_STUDY_WORKFLOW.md)
 
 ## Elite extension sequence (after baseline completion)
-1. [36_ELITE_ENGINEERING_TRACK.md](./36_ELITE_ENGINEERING_TRACK.md)
-2. [37_QUARTERLY_EXAMS_AND_DEFENSES.md](./37_QUARTERLY_EXAMS_AND_DEFENSES.md)
-3. [38_SYSTEM_DESIGN_AND_RFCS.md](./38_SYSTEM_DESIGN_AND_RFCS.md)
-4. [39_PRODUCTION_PLATFORM_LAB.md](./39_PRODUCTION_PLATFORM_LAB.md)
-5. [40_SECURITY_COMPLIANCE_HARDENING.md](./40_SECURITY_COMPLIANCE_HARDENING.md)
-6. [41_PERFORMANCE_ENGINEERING_LAB.md](./41_PERFORMANCE_ENGINEERING_LAB.md)
-7. [42_OPEN_SOURCE_CONTRIBUTION_LANE.md](./42_OPEN_SOURCE_CONTRIBUTION_LANE.md)
-8. [43_PUBLIC_PROOF_OF_WORK_PORTFOLIO.md](./43_PUBLIC_PROOF_OF_WORK_PORTFOLIO.md)
-9. [44_SME_INTERVIEW_AND_DEBATE_BANK.md](./44_SME_INTERVIEW_AND_DEBATE_BANK.md)
-10. [45_MASTERY_TELEMETRY_AND_REMEDIATION.md](./45_MASTERY_TELEMETRY_AND_REMEDIATION.md)
+1. [36_ELITE_ENGINEERING_TRACK.md](./curriculum/36_ELITE_ENGINEERING_TRACK.md)
+2. [37_QUARTERLY_EXAMS_AND_DEFENSES.md](./curriculum/37_QUARTERLY_EXAMS_AND_DEFENSES.md)
+3. [38_SYSTEM_DESIGN_AND_RFCS.md](./curriculum/38_SYSTEM_DESIGN_AND_RFCS.md)
+4. [39_PRODUCTION_PLATFORM_LAB.md](./curriculum/39_PRODUCTION_PLATFORM_LAB.md)
+5. [40_SECURITY_COMPLIANCE_HARDENING.md](./curriculum/40_SECURITY_COMPLIANCE_HARDENING.md)
+6. [41_PERFORMANCE_ENGINEERING_LAB.md](./curriculum/41_PERFORMANCE_ENGINEERING_LAB.md)
+7. [42_OPEN_SOURCE_CONTRIBUTION_LANE.md](./curriculum/42_OPEN_SOURCE_CONTRIBUTION_LANE.md)
+8. [43_PUBLIC_PROOF_OF_WORK_PORTFOLIO.md](./curriculum/43_PUBLIC_PROOF_OF_WORK_PORTFOLIO.md)
+9. [44_SME_INTERVIEW_AND_DEBATE_BANK.md](./curriculum/44_SME_INTERVIEW_AND_DEBATE_BANK.md)
+10. [45_MASTERY_TELEMETRY_AND_REMEDIATION.md](./curriculum/45_MASTERY_TELEMETRY_AND_REMEDIATION.md)
 
 ## Universal learner-adaptive sequence (final assurance layer)
-1. [46_ACCESSIBILITY_AND_LEARNING_PROFILE_PLAYBOOK.md](./46_ACCESSIBILITY_AND_LEARNING_PROFILE_PLAYBOOK.md)
-2. [47_DIAGNOSTIC_AND_PERSONALIZED_STUDY_ENGINE.md](./47_DIAGNOSTIC_AND_PERSONALIZED_STUDY_ENGINE.md)
-3. [48_MISCONCEPTION_AND_FAILURE_ATLAS_EXPANDED.md](./48_MISCONCEPTION_AND_FAILURE_ATLAS_EXPANDED.md)
-4. [49_COMPETENCY_COVERAGE_AND_GAP_CLOSURE_MATRIX.md](./49_COMPETENCY_COVERAGE_AND_GAP_CLOSURE_MATRIX.md)
-5. [50_CERTIFICATION_GRADE_COMPLETION_PROTOCOL.md](./50_CERTIFICATION_GRADE_COMPLETION_PROTOCOL.md)
+1. [46_ACCESSIBILITY_AND_LEARNING_PROFILE_PLAYBOOK.md](./curriculum/46_ACCESSIBILITY_AND_LEARNING_PROFILE_PLAYBOOK.md)
+2. [47_DIAGNOSTIC_AND_PERSONALIZED_STUDY_ENGINE.md](./curriculum/47_DIAGNOSTIC_AND_PERSONALIZED_STUDY_ENGINE.md)
+3. [48_MISCONCEPTION_AND_FAILURE_ATLAS_EXPANDED.md](./curriculum/48_MISCONCEPTION_AND_FAILURE_ATLAS_EXPANDED.md)
+4. [49_COMPETENCY_COVERAGE_AND_GAP_CLOSURE_MATRIX.md](./curriculum/49_COMPETENCY_COVERAGE_AND_GAP_CLOSURE_MATRIX.md)
+5. [50_CERTIFICATION_GRADE_COMPLETION_PROTOCOL.md](./curriculum/50_CERTIFICATION_GRADE_COMPLETION_PROTOCOL.md)
 
 ## Recommended weekly loop
 1. Read one section.

AI_USAGE_GUIDE.md

@@ -0,0 +1,100 @@
+# AI Usage Guide
+
+How and when to use AI tools (ChatGPT, Claude, Copilot, etc.) at each level of the curriculum. The goal is to build real skill, not just get answers.
+
+## The Golden Rule
+
+**Understand before you copy.** If you cannot explain what a piece of code does line by line, you do not understand it yet. Using AI to skip understanding is borrowing from your future self.
+
+## Guidelines by Level
+
+### Level 00 -- No AI
+
+Type everything yourself. Every character. This builds the muscle memory and mental model that everything else depends on.
+
+- Do not use AI to write code
+- Do not use AI to explain error messages
+- Do not use AI to check your work
+- **Why:** You need to feel the keyboard, make typos, fix them yourself. This is how your brain builds the connection between intent and code.
+
+### Levels 0-2 -- AI for Error Messages Only
+
+You may ask AI to explain an error message *after* you have tried to understand it yourself.
+
+- Read the error message yourself first (see [Reading Error Messages](concepts/reading-error-messages.md))
+- Try to fix it based on the line number and error type
+- If stuck after 2-3 attempts, paste the error into an AI and ask "what does this error mean?"
+- **Do not** paste your code and ask "fix this"
+- **Do not** ask AI to write code for you
+- **Why:** Error messages are a language. You need to learn to read them, but it is okay to get translation help while learning.
+
+### Levels 3-4 -- AI for Debugging Hints
+
+You have the fundamentals. Now AI can help you debug, but you still write all the code.
+
+- Write your code first, always
+- When stuck on a bug, describe the problem to the AI in words before sharing code
+- Ask "what could cause this behavior?" rather than "fix my code"
+- Use AI to explain library documentation you find confusing
+- **Do not** ask AI to generate functions or modules
+- **Why:** Describing a problem clearly is a skill. If you can explain what is wrong, you are halfway to fixing it.
+
+### Levels 5-6 -- AI for Code Review
+
+You write it, AI reviews it. This is how you level up from working code to good code.
+
+- Write your solution completely before asking AI for feedback
+- Ask: "What could I improve in this code?" or "Are there edge cases I missed?"
+- Use AI to learn about design patterns relevant to your project
+- AI can explain new concepts (SQL, scheduling, templates) that the curriculum introduces
+- **Do not** ask AI to write the initial implementation
+- **Why:** Code review is how professionals grow. Getting feedback on *your* code teaches you patterns that stick.
+
+### Levels 7-8 -- AI Pair Programming
+
+You drive, AI assists. Think of it like pair programming where you are the driver.
+
+- You decide the architecture and approach
+- AI can help implement specific functions after you describe what they should do
+- AI can suggest test cases you might have missed
+- Discuss trade-offs with AI: "Should I use caching here? What are the pros and cons?"
+- **Always** understand what the AI-generated code does before using it
+- **Why:** At this level you are learning to evaluate and direct, not just write. Working with AI is a professional skill.
+
+### Levels 9-10 -- Full AI Collaboration
+
+You focus on architecture, design, and decisions. AI handles routine implementation.
+
+- Use AI for boilerplate, scaffolding, and repetitive patterns
+- Focus your energy on system design, trade-offs, and architecture decisions
+- Use AI to explore approaches: "Give me three ways to implement event sourcing in Python"
+- Review all AI-generated code critically -- AI makes mistakes too
+- **Why:** Senior engineers spend most of their time on design and review, not typing code. This mirrors real-world practice.
+
+## General Principles
+
+**Build muscle memory first.** Levels 00-2 exist to wire your brain for Python. Skipping this with AI is like using a calculator before learning multiplication -- you will be permanently dependent.
+
+**Test AI suggestions.** AI confidently generates wrong code. Always run it, test it, and verify it works. If you cannot tell whether AI code is correct, you are not ready to use it.
+
+**Describe before you paste.** Before sharing code with AI, try to describe your problem in words. This forces you to think about what you know and what you do not. Often, the act of describing it reveals the answer.
+
+**AI is a tool, not a teacher.** AI can explain and generate, but it cannot assess your understanding. Only you know whether you truly get it or are just copying patterns.
+
+**Never submit AI-generated work as your own understanding.** If a project asks you to explain your approach in `notes.md`, write it in your own words. The notes are for you, not for a grade.
+
+## Quick Reference
+
+| Level | AI Allowed For | AI Not Allowed For |
+|-------|---------------|-------------------|
+| 00 | Nothing | Everything |
+| 0-2 | Explaining error messages | Writing code, fixing bugs |
+| 3-4 | Debugging hints, explaining docs | Writing code, generating functions |
+| 5-6 | Code review, explaining concepts | Initial implementation |
+| 7-8 | Pair programming (you drive) | Unsupervised code generation |
+| 9-10 | Full collaboration | Skipping architecture thinking |
+
+---
+
+| [Home](README.md) |
+|:---:|