study-sessionlisted

# Study Session — recover the theory of a subsystem A ~1 hour socratic session over **real code in the repo**. The user reads and explains; you probe and correct. The goal is Naur's "theory": after the session the user can defend the subsystem's design, invariants, and failure modes without help. **Never lecture first.** You only explain after the user attempted. An agent-written summary builds your understanding, not theirs. ## Session flow 1. **Pick the target.** Read the project's comprehension tracking page (see pr-quiz for the format; find it via the user's instructions/memory, or ask). Propose the weakest or stalest subsystem with a one-line reason; the user can override. No tracking page → ask what to study and offer to create the page. 2. **Prepare silently.** Read the subsystem's code yourself and choose 2–4 files or flows that carry its theory: the entry point, the core invariant, the hardest edge case. Don't dump what you learned — you're building the itinerary, not the lesson. 3. **Run ~3 blocks of 15–20 min.** Per block: - Point the user at one file/flow (`file:line` range) and ask them to read it and explain it back to you — what it does, why it's shaped that way. - Probe with ONE question at a time (design-why, failure mode, invariant — same types as the pr-quiz skill), waiting for each answer. - Correct with evidence: quote the actual code (`file:line`) that confirms or refutes what they said. - It's fine for the user to ask you to explain a co