Browser-agent end-to-end suites run against production https://calendo.dev. The reality gate: a real booking must produce a real calendar event and a real email, confirmed by an agent opening Gmail/Calendar in the browser.
Review surface only. Full operating manual: README.md · setup: 00-setup-preconditions.md · coverage ledger: COVERAGE.md · results: RESULTS-TEMPLATE.md.
Sorted by priority (P0 → P3) then ID. The high-traffic paths most users hit (CU-01, CU-05, CU-08, CU-11, CU-06, CU-02, CU-03) are the deepest runbooks. "Status" defaults to Not run — fill it from each run's results file.
| ID | Title | Pri | Accounts | Lane | Excl. | Est. | L3 | Status |
|---|---|---|---|---|---|---|---|---|
| CU-01 | Core booking lifecycle (book → reschedule → cancel) | P0 | P1 host + anon | B | — | 30m | Yes | Not run |
| CU-02 | Auth lifecycle (register, verify, login, reset, delete) | P0 | fresh +auth | D | — | 22m | Yes | Not run |
| CU-03 | Google Calendar — conflict, buffers, two-way sync | P0 | P1 + GCal | D | — | 40m | Yes | Not run |
| CU-05 | Event-type config → booking-page enforcement | P0 | P1 host | B | — | 85m | Yes | Not run |
| CU-06 | Availability engine — weekly, overrides, holidays, slot-debug | P0 | P1 host | X | YES | 35m | — | Not run |
| CU-07 | Host-side booking management (no-show, notes, guests, on-behalf) | P1 | P1 host | B | — | 40m | Yes | Not run |
| CU-08 | AI booking chatbot (the differentiator) | P1 | anon | B | — | 30m | Yes | Not run |
| CU-09 | AI dashboard assistant (feature parity) | P1 | P1 host | B | — | 45m | Partial | Not run |
| CU-10 | Landing + marketing + static pages + mobile | P1 | none (anon) | A | — | 15m | — | Not run |
| CU-11 | Public booking UX — timezones, nav, empty-state, QR, mobile | P1 | anon | A/B | — | 22m | — | Not run |
| CU-04 | Microsoft / Outlook calendar integration | P2 | Outlook acct | D | — | 35m | Yes | Not run |
| CU-12 | Routing forms — build → submit → route → analytics | P2 | P1 + anon | B | — | 18m | — | Not run |
| CU-13 | Meeting polls — create → vote → tally → finalize | P2 | P1 + anon | B | — | 18m | — | Not run |
| CU-14 | Team / org scheduling — roles, round-robin, collective | P2 | P1 + P3 | D | — | 40m | Yes | Not run |
| CU-15 | Contacts, analytics dashboard, CSV export | P2 | P1 host | A | — | 25m | — | Not run |
| CU-16 | Settings & customization — branding, blocklist, BYOK, pixels | P2 | P1 host | B | — | 30m | — | Not run |
| CU-17 | Slack notifications & outbound webhooks | P2 | P1 host | B | — | 30m | Yes | Not run |
| CU-18 | New-user onboarding wizard (4-step) | P2 | fresh +onb | D | — | 22m | — | Not run |
| CU-19 | Embeddable booking widget (inline/popup/badge) | P3 | P1 + ext page | B | — | 25m | — | Not run |
| CU-20 | Email sequences, reminders, reconfirmation (time-gated) | P3 | P1 host | B | — | 40m | Partial | Not run |
| CU-22 | Chrome extension for Gmail (manual-led) | P3 | P1 (manual) | manual | — | 20m | — | Not run |
Each suite is internally sequential. Across suites, run Wave 1 fully, then Wave 2 alone.
What area each suite owns. Full capability-by-tier traceability is in COVERAGE.md.
Things a browser agent cannot fully verify. After a run these roll up into the results file; this is the standing list to keep in mind.
These are deliberately catalogued, not silently dropped. See COVERAGE.md §2 for the complete ledger.