verifylisted

# verify — Check a Deployed Environment Against the Blueprint Run **after a deploy** (yours or CI's) to answer: does the deployed product still do what the blueprint promises? vwf never deploys — deployment is yours; this command only observes and verifies. Two passes: **health** (is every deployed project up) and **acceptance** (do the blueprint's flow criteria hold against the real environment). A failure here is production feedback — it routes exactly like `/vwf:feedback` input. A clean run against **production** additionally offers to record a **release** (§5) — freezing each deployed service's API contract, the point from which backward compatibility is enforced. ## Halt Conditions - No flow docs with Acceptance blocks under `docs/blueprint/flows/` **and** no deployable project in the registry → nothing to verify; say so and stop. - `$ARGUMENTS` names no environment and more than one is plausible → ask which (staging, production, …) and wait. ## Format Check Run the preflight in `${CLAUDE_PLUGIN_ROOT}/assets/format-check.md`; nudge `/vwf:setup` on drift (proceed unless the needed Acceptance blocks are missing — a pre-format-4 repo has nothing to verify flows against; tell the user to run `/vwf:setup` then stop). ## Pipeline ### 1. Resolve the target Read the registry (`docs/blueprint/registry.yaml`) for the deployed projects (cloud types: `service`, `worker`, `site`, `console`) and the Acceptance blocks of every flow under `docs/blueprint/flows/*/*/index.md`