signup-doors-walk: every door, including the moment after submit

Signup Doors Walk: Every Door, Including the Moment After Submit

The "signup-doors-walk" skill is an essential runbook for FortListOS, designed to walk through every signup door as a customer would experience it. This process involves 23 doors, as specified in scripts/signup-doors/doors.json, ensuring a thorough test of multi-step and two-form flows. Notably, the skill excludes the founder console or any attempt to prove a single feature is wired. The incident necessitating the required submit step is detailed in docs/forms/FORM-FRICTION-CHERRY-ON-TOP-2026-10-07.md, specifically fix 8.

Hard Rules

Running this skill on production targets the URL https://www.thefortlist.com. It utilizes synthetic data, with unique naming conventions like UXWALK_<run>_<width>, and the SES simulator email success@simulator.amazonses.com. No real owner links or personal data are used, maintaining everything on a synthetic test/suppression rail. Cleanup is mandatory, ensuring all synthetic rows, including dependent gifts and queued notices, are deleted post-run. Any cleanup error is marked as a failure. Screenshots are captured using Playwright, while no real-person emails or metered APIs are allowed.

The Runbook

The process begins with executing python skills/signup-doors-walk/scripts/check_after_submit_step.py from the central .claude repo. This ensures no required step is missing, and that any multi-step door has after_submit: true. Following this, node scripts/signup-doors/walk-doors.mjs is run in FortListOS. This script captures entry sections at 390 and 1365 pixels, comparing the local roster to the central one to ensure completeness. Any omitted doors require a manual walkthrough.

After capturing first-screen screenshots, the checklist is filled for each section. The "Required after-submit step" is crucial here: it demands fresh submissions for every multi_step: true or two_form: true door. Each step uses separate sessions/leads for 390 px and 1365 px widths, ensuring no state carryover. For example, the business-halloween door requires capturing the success of the first form before proceeding.

Downstream rows, attribution, confirmation message bodies, and link destinations must be asserted. The synthetic readback and cleanup procedure are preserved, and any blockage in fixtures is marked as a BLOCKER. The checker is run with --evidence <absolute-path-to-after-submit.json> to verify the collected evidence, with failures noted if evidence is incomplete or misaligned.

Required After-Submit Step

In particular, doors like business-halloween and halloween-contribution have specific requirements. The former involves capturing the first form's success and proceeding through the gift form. The latter, being the FortList Halloween gift form, mandates its evidence row. For claim, a synthetic unclaimed listing is used, ensuring a robust check of the submission path.

In summary, the "signup-doors-walk" skill is a rigorous process that ensures each signup door, including the moments post-submit, functions correctly. By meticulously following the outlined steps, engineers and founders can confidently validate the user experience on FortListOS.