verify-unattended

# Reticle, unattended Same product, same verdicts, one difference: **nothing here waits for a human.** The normal skill has two places where it hands control back — "restart your client so it picks up the MCP server" and "open the app in a browser". Both are correct when someone is sitting there. In goal mode they are dead ends: the restart ends the context holding these instructions, and there is nobody to open a tab. So this skill takes the route that needs neither, and stops only when it has a verdict or a reason. ## The one rule that makes this work **You cannot add MCP tools to your own running process.** No slash command, no config edit, no re-registration reaches the tool list you already have — your client read it before Reticle existed. Do not try, and do not ask to be restarted. Instead, branch once on what you already have: - **`reticle_*` tools present** → drive with them. Best evidence, source-mapped, full verdicts. - **not present** → use the CLI. `reticle verify` produces a verdict and an exit code with no MCP involvement at all. Both routes end in a verdict. Pick the one your process allows and go. ## Step 1 — wire it, once, quietly ``` npx -y @reticlehq/server@latest init ``` Then read the report rather than assuming it. Two lines matter: - **`⚠` on the app's build config** — the wiring did not land. Apply the printed edit yourself; do not carry on as if it had. - **`ℹ` naming a version fallback** — the pinned SDK was refused and a different one i...