discoverlisted

# /requivo:discover Start a new Requivo session from a client request. **You** do the reasoning here — this Claude Code session, no Anthropic API key. First read `${CLAUDE_PLUGIN_ROOT}/REASONING.md` (the shared rules: the preflight, the trust boundary, honesty per slot, the validate→apply loop). Then: ## 1. Preflight, then check the install Start with the **preflight** in REASONING.md: run `requivo doctor --json` and check first whether the command ran *at all*. If it did not — no JSON, and a message from the shell about a command it could not find — the CLI is not installed. Say the four things REASONING.md lists and stop; nothing has been created yet, so there is nothing to clean up. If it ran, read the report. Confirm **both** `schema.ok` and `context.ok` are true. A missing Anthropic SDK / API key is **fine** — this mode does not use it. `context.ok` is not decoration. The slot schema and the product context cards ship in different directories, so an install can lose the cards while `schema.ok` stays true — and the cards are what impact is estimated against, which is the whole of `information_value = uncertainty × impact`. The session would still run and would still produce a model; it would just ask duller questions, for a reason nothing on screen would name. `context.status` says which case you are in: `ok`, `empty` (the install has no cards) or `unreadable` (they could not be read at all). On anything but `ok`, tell the user what `context.error` or the card count s