survey-flow-auditlisted

# Survey Flow Audit Audit a survey the way it will actually run, not the way its build files say it should. Everything here reads the LIVE definition over the API and, optionally, walks the respondent path in a real browser. The audit is **read-only on the survey definition**: it produces findings, never fixes. The optional browser walk (Phase H) does generate test *responses* — data-plane writes with their own cleanup obligations, and possibly test hits on a vendor dashboard — so it is opt-in and announced, never silent. Repairs are a separate, explicitly authorized step (see the `qualtrics-ops` skill for how to make them without new damage). Fielding now happens in an environment where AI agents complete surveys at scale and pass conventional attention checks (documented since 2025 in peer-reviewed and platform validations), panel vendors bill on redirect passbacks, and platforms silently stage rather than publish edits. Each of those failure classes is invisible in a casual preview and cheap to catch here. ## When to use Immediately before a soft launch or full launch; after any live patch to a fielding instrument; when a vendor reports a broken redirect or "different content"; when handed an unfamiliar survey to take over. Inputs: API credentials and the survey id; ideally also the pre-registration or PAP (for the report-only-vs-terminating posture), the vendor's integration sheet (redirect URLs, ID parameter name), and the quota targets. A browser MCP (claude-in-chro