fix-what-i-pointed-at

# The human pointed at the bug. Go fix it. "The spacing on that card is wrong" is unactionable in chat and precise in the app. **Reticle**'s running app has a **Flag a bug** control: the human clicks it, points at an element, and types what is wrong. Each flag becomes a mark carrying the element, the note, and the `file:line`, so the round trip that usually costs a screenshot, a description, and two clarifying questions costs one call. Not installed? `RETICLE_INSTALL_SOURCE=npx_skill npx @reticlehq/server@latest init`, then the [`install-and-verify`](https://github.com/reticlehq/reticle/blob/main/skills/install-and-verify/SKILL.md) skill. ## Drain the marks ``` reticle_session({ action: "review", sessionId }) ``` ```json { "marks": [ { "id": "m1", "note": "this button is misaligned", "label": "button \"Pay\"", "source": { "file": "src/Checkout.tsx", "line": 42 }, "fix": "Open src/Checkout.tsx:42 and fix: this button is misaligned." } ], "pendingCount": 1 } ``` **Check this at the start of a session**, and again whenever the human has been in the app. Reading never consumes a mark, so list → fix → verify → resolve is safe to run in any order. ## The loop 1. **Read** the marks. Group them if several point at the same file: one edit often answers three. 2. **Open** `source.file` at `source.line`. This is the whole point: no hunting for which component rendered that button. 3. **Fix** what the `note` asks for. If the note is amb...