paper-review

# paper-review — GDocs-style review of rendered sources, with bots The engine is built and battle-tested. **Canonical engine: `$BOTFERENCE_HOME/frontends/review/`** (ships with botference). Architecture, decision history, and the unbuilt roadmap (CI rounds, cloud version): `design.md` next to this file. This file tells you how to USE the system. ## Setting up a new project ("set up paper review in <dir>") **Preferred: `botference review [dir]`** — one command does all of the below (engine copy, detection via `scripts/review-detect.mjs` with an echoed summary, gitignore, build, serve; `--share`, `--hosted`, `--port N`, `--no-agents`, `--upgrade`). Use the manual steps only when the launcher isn't available: 1. Copy the engine from the reference implementation into `<dir>/review/`: `build.mjs`, `server.mjs`, `chat.mjs`, `apply.mjs`, `submit.mjs`, `init-config.mjs`, `bridge-system-prompt.md`, `SCHEMA.md`, `assets/` (review.js, style.css). Never copy `review.config.json`, `state/`, `suggestions.json`, or `site/` — those are per-project. 2. Run `node review/init-config.mjs` from `<dir>` (it inspects the directory: master file via `\documentclass`, sections via `\input`/`\include` order, bib, abbreviations, todo macros, figures dir, a free port, and the bridge block). **Show the user what was detected and get their confirmation before proceeding** — never guess the master file silently. 3. Add the gitignore block (see reference repo): `review/site/...