canary

zuvo:canary

Monitor production after deployment. Browser-based or HTTP-only health checks with configurable duration.

Argument Parsing

Argument	Effect
<url>	Production URL to monitor (REQUIRED)
--duration <time>	Monitoring duration (default: 10m, range: 1m-30m)
--interval <time>	Check interval (default: 60s)
--quick	Single health check, no loop
--max-errors <n>	Error threshold for FAIL verdict (default: 3)

Mandatory File Loading

Before starting any phase, read these shared includes:

INCLUDES LOADED:
  1. ../../shared/includes/env-compat.md     — READ
  2. ../../shared/includes/run-logger.md     — READ
  3. ../../shared/includes/retrospective.md     — READ

---

Phase 0: Setup

Step 1: Validate URL

If no URL argument is provided, STOP immediately:

URL is required. Usage: zuvo:canary https://myapp.com

Step 2: Detect Browser Capability

Check whether the current environment exposes browser automation tools compatible with Playwright or Chrome DevTools.

• If browser tooling is available: set MODE=full.

• If not: set MODE=degraded and print:

  [DEGRADED: no browser tools] — running HTTP-only checks. Console errors and screenshots unavailable.
  

Step 3: Check Environment (per env-compat.md)

If running in a non-interactive environment (Codex App, Cursor):

• Default to --quick behavior (single check) only if no --duration was explicitly passed.

• If the user explicitly passed --duration: honor it — run the full monitoring loop. Non-interactive environments can execute timed loops; the limitation is user interaction, not execution duration.

• Print:

  [AUTO-DECISION]: defaulting to one-shot mode. Pass --duration to enable monitoring loop.
  

Step 4: Parse Arguments

Parse --duration and --interval. Validate duration range (1m–30m inclusive). If duration is outside this range, stop with:

--duration must be between 1m and 30m. Got: <value>