From 01aca9d3621ff916432f7679dc919041d84d5fda Mon Sep 17 00:00:00 2001 From: Bryce Date: Thu, 25 Jun 2026 17:17:57 -0700 Subject: [PATCH] =?UTF-8?q?test(ssr):=20Phase=207=20parity=20gate=20?= =?UTF-8?q?=E2=80=94=20characterization=20spec=20for=20the=20Invoice=20Pay?= =?UTF-8?q?=20wizard?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Invoice Pay wizard is the first GENUINE multi-data-step wizard: choose-method (collects bank-account + method) -> payment-details (collects check-number / handwritten-date / amounts), merged only at submit. This gate characterizes that flow before migrating it onto the session-backed engine, so the merge can be proven behavior-preserving. - Seed: make the TEST client's check bank account visible (+ name "Test Checking") so the choose-method step renders a usable method card. The pay flow had no e2e coverage, so the bank account was never visible in tests before. - Spec drives the real 2-step flow against the unmodified wizard: choose-method renders the bank account + its methods (print-check/debit/handwrite-check, in the card tooltip); picking handwrite-check advances to payment-details (check-number + date + Pay); filling the check number and submitting shows the completion modal. The handwrite-check path is used because it transacts a pending check payment directly (no PDF/S3), making the success assertion stable. Notes for the migration: the method controls live in a