referee-responselisted

# Referee response letter The editor reads this letter with the manuscript open. A pin that says a change is in Section 4 when it is not gets caught immediately, and the cost of that is much higher than the cost of an honest TODO. So the letter may only say what the manuscript actually says. Step 3 is the point of this skill: a verification pass sitting between classifying the comments and writing any prose. The `--five-q` so-what gate on pushback paragraphs is adapted from [aspi6246/Claude-Code-Presentation](https://github.com/aspi6246/Claude-Code-Presentation). ## Arguments - `continue`: extend a partial `R2R_R<n>.tex` already in the project instead of starting fresh. - `from-email`: input is a pasted decision email (Outlook export, forwarded thread). - `@path/to/letter.pdf`: the decision letter as a file (`.pdf`, `.txt`, `.docx`, `.md`). - `--five-q`: opt-in stress test on pushback paragraphs (see below). Combines with the others. With no argument, the comments are pasted in the message body. ## Finding the project There is no config file and none should be required. Glob `~/Library/CloudStorage/Dropbox*/Apps/Overleaf/*/` (this setup assumes Overleaf projects sync there via Dropbox; adjust to your machine) and match the user's wording against the directory names; ask once if two fit. Then read what is actually there: - manuscript: identified by content, the `.tex` containing `\documentclass` or `\begin{document}` (usually `main*.tex`, or `doc.tex` in older projec