readbacklisted

# readback A terminal is a bad place to read two thousand words and a hopeless place to argue with a specific sentence in them. Hand the reader the actual text on a page; get back their words attached to the passages they picked. `review` blocks until they press **Confirm & send**, then writes exactly the prompt they confirmed to stdout and nothing else. The usual case is one long reply of your own — a draft, a design, an analysis you just wrote — and the reader wants to mark it up rather than answer it in prose. ## Commands ```bash # the reply you just wrote, piped in as its own text (the common case) python3 scripts/readback.py review - --format markdown --title "v4 volume commit design" <<'RB' <the reply, exactly as you sent it> RB # a file that already exists: a plan, a design doc, a PR body python3 scripts/readback.py review PLAN.md --out-dir /tmp/readback-plan # standalone artifact: read, annotate, edit the prompt; cannot send it back python3 scripts/readback.py build session.json -o review.html ``` Shared flags: `--format markdown|transcript` (inferred from `.md`/`.json`, required when `INPUT` is `-`), `--title TEXT`, and `--no-diagrams`. `review` also takes `--no-open` (print the URL, launch no browser); `build` takes `--force`. Without `--out-dir`, `review` creates a fresh private temporary directory and prints it. ## Choosing the input - **One long reply** — the common case, and the reason to reach for this at all. Pipe the reply's text in as Markdown with