paper-to-doclisted

The note a later self opens. Reading leaves scaffolding — `— confirm?` markers, `## Stuck`, triage rows — earning its place while you read and nothing a year on. A write-up keeps what still pays. ## Ground rules - **Notes or stop.** A write-up is made from a finished note. Where none exists, say so and offer the `three-pass-read` skill first. - **Carry the source tag forward.** Each factual line keeps the note's own tag: `§4.2`, `Fig. 3`, `Table 1`. - **Follow the user's language.** Write prose in the language the user is writing in. Keep technical terms, quoted phrases, and source tags in their original form. ## Steps 1. **Take the shape from the template.** `note-template.md` in the working directory decides it; without one, use the default below. **Its headings are the anchors**: fill under every heading it carries, in its order, and add no section it lacks. Where a heading has nothing worth putting under it, write `—`. 2. **Read the working note** `papers/<key>.md`. 3. **Keep only what pays.** Every line either carries a source tag or is marked as the reader's judgement; a line that is neither is exposition, and exposition stays out. Concretely: - A `— confirm?` candidate the user answered: the answer stays, the marker goes. - One never answered: the candidate stays, and the front matter's `unconfirmed` field names its question. - A `## Stuck` entry pass 3 resolved: the resolution stays, the entry goes. - Restatements of the abstract, and the triage row: o