journey-deploy

# Journey: Deploy verification Stage 4 of the guided journey. Verify the deployed app actually works end-to-end. ## When to use - Dispatched by `journey` when `current_stage: deploy`. - Directly via `/butterbase-skills:journey-deploy`. ## Preflight If `docs/butterbase/03-preflight.md` is missing, older than 24 hours, or `00-state.md` has `app_id: null`, invoke `butterbase-skills:journey-preflight` first. Wait for it to return successfully before proceeding. ## Inputs - `docs/butterbase/00-state.md` — for `app_id`, `deployed_url`. - `docs/butterbase/02-plan.md` — for the function list to smoke. - `docs/butterbase/04-build-log.md` — to know what shipped. ## Procedure 0. **Refresh docs.** Call `butterbase_docs` with `topic: "frontend"`. For end-to-end smoke patterns, also WebFetch `https://docs.butterbase.ai/deploy`. Skip if cache is fresh. For each check, log a one-line result to `04-build-log.md`. Halt on the first ✗ and ask the user to fix or skip. 1. **Frontend reachable.** If `deployed_url` is set, fetch it via Bash `curl -sS -o /dev/null -w "%{http_code}" <url>`. Expect `200`. Log `<ISO> deploy curl 200 ok` or `... <code> fail`. 2. **Functions respond.** For each function in the plan with HTTP trigger, call `mcp__butterbase__invoke_function` with a representative payload. Expect 2xx. Log per function. 3. **Auth round-trip (if configured).** If the plan included OAuth, prompt the user: `"Open <deployed_url>, click 'Sign in with <provider>', and confirm you...