Testing artifacts · 2026-08-15
Ledger proof — Cloud guest
Real browser against https://platform.mystflo.com. Auth: GUEST · rail CT-LEDGER-01. mf:qa set, then cleared. Screenshots are the evidence. This file plus the findings MD plus the qa-log.sh row is the proof — a chat scorecard is not.
Verdicts
| Scenario | Verdict | Why |
|---|---|---|
| CT-LEDGER-01 step 1 catalog | PASS | Cards show name + price. Header is Sign in + Get early access. No founder name. PREVIEW badge OK. |
| CT-LEDGER-01 step 2 Waitlist + Launch Overview | PASS | Card (not Activate) opened Overview. $0.20/run. Tabs Overview · Personalize · Connect · Try. |
| CT-LEDGER-01 step 3 Activate → Get early access | PASS | Complete Setup opened Get early access (name / email / WhatsApp), not the Personalize wizard. |
| CT-LEDGER-01 step 4 close | PASS | Modal closed. Form not submitted. Still guest. |
| CT-LEDGER-02 Peyton WP | BLOCKED | Header was guest, not Peyton WP. Did not invent a password. Rail not started. |
What this proves
AC-EXPLORE-01— catalog cards + price/run on the deployed app.AC-EXPLORE-05— guest Activate / Complete Setup opens the waitlist modal, not the wizard.- The persist path: plan → this HTML + findings MD → ledger row.
CT-LEDGER-02 (signed-in Pulse + Retreat Launch Kit) is still owed on an already-open Peyton WP Chrome tab.
Screenshots (375 first, then 1440)
