prepare-to-reproducelisted

The spec someone opens a terminal with. Its centre is the **gap list**: everything the paper leaves unstated that a reimplementation must decide anyway. Reading has already happened — this turns the reading into a build. ## Ground rules - **Full text or stop.** Obtain the paper's full text (PDF, HTML, or plain text) before starting. When you cannot, ask the user for the file and wait: an abstract plus recall is not a paper. - **Source-tag every claim.** Each statement about the paper carries `§4.2`, `Fig. 3`, or `Table 1`. Where the paper is silent, write `Paper does not state`. - **Follow the user's language.** Write prose in the language the user is writing in. Keep technical terms, quoted phrases, source tags, and the structural headings below in their original form, so files stay mergeable across sessions. ## Steps 1. **Load the reading.** Read `papers/<key>.md` where it exists — whatever it already settled is a head start. Where no note exists, say so and offer the `three-pass-read` skill first; the user may still tell you to go ahead from the paper alone. 2. **Work the checklist item by item.** Each item lands as `§x` or as `Paper does not state`: - Core algorithm, as pseudocode someone could type up - Data — source, size, splits, preprocessing - Model — architecture, initialisation, parameter counts - Training — optimiser, LR schedule, batch size, steps, hardware, wall-clock - Evaluation — metrics, baselines, seeds, error bars 3. **Build the gap list