preview-and-provelisted

# Preview and Prove Validate the product through the surface the user actually sees. Source inspection and automated tests support the claim; they do not replace a real browser-visible run. ## Safety - Read the repository's run, test-data, and environment instructions before starting services. - Use local, sandbox, preview, or explicitly authorized test accounts and payment methods. Never create a production charge, send a real campaign, or mutate customer data to prove a flow. - Do not expose credentials, cookies, tokens, personal data, or private screenshots in logs or the final report. - Ask only when a required credential, irreversible action, or product choice cannot be discovered safely. If a surface is unavailable, report it as unverified. ## Workflow 1. Define the exact route, actor, viewport, preconditions, success state, and side effects to verify. For checkout, authentication, onboarding, and other stateful funnels, include at least one safe failure-and-recovery path. 2. Inspect repository instructions and start the real application plus required local dependencies. Record the URL, build identity, seed/test account, and relevant feature flags without revealing secrets. 3. Open the app in a real browser. Reproduce the flow through visible controls rather than bypassing it with direct API calls. 4. Observe the page, accessibility tree, console, failed requests, redirects, cookies/storage, and network responses relevant to the flow. 5. Verify the durable outcome