Every recording and every signed PDF below came from a real run of the actual VUMI, IMG, and Best Doctors sign-up flows — with and without a spouse — captured start to finish against the live app, with no synthetic data beyond a test identity.
All 5 scenarios below are fully verified end-to-end, including real captured signed PDFs for both spouse scenarios. That wasn't true a short while ago: the recorder only ever observed the primary applicant's completion event, and never saw the spouse's separately-hosted signing session finish, so the merged signed PDF was never actually captured for spouse scenarios. It's fixed now — see the mechanism below. Two other fixes are reflected in these runs as well: IMG's asthma/allergies and COVID/SARS medical-history sub-questions are now correctly gated behind their parent yes/no answers (previously they always showed), and IMG's application form now includes the “Renewal Contact Information” section it was previously missing entirely, with its conditional address/fax/email field. Both of those are already merged.
Technical detail: The recorder captures the completion request body when the primary applicant finishes signing, then replays it against the app's /api/docuseal/complete endpoint after the spouse also finishes signing in their own session. This fix shipped in PR #57 on incrhst/BudgetSmart — it's open, mergeable, and checks are passing, but it is not yet merged as of this report. The IMG medical-history gating fix (PR #55) and the IMG Renewal Contact Information section (PR #56) are both already merged.
The primary applicant finishes signing in the app's own embedded DocuSeal form. The completion request fires, but DocuSeal can't return a merged PDF yet — the spouse hasn't signed.
The spouse signs in their own DocuSeal-hosted URL — genuinely separate, never touching the app's pages. That's normal for multi-signer e-signature flows. Once they finish, the recorder replays the applicant's completion request, and DocuSeal returns the fully merged signed PDF.
Each row is one test, each column a step in the process. A dash means that step doesn’t apply to that scenario — it’s not a failure.
| Scenario | Eligibility Check | Plan Selected | Application Details | Health Questions | Applicant Signed | Spouse Signed | Application Finalized |
|---|---|---|---|---|---|---|---|
| VUMI · No spouse | ✓ | ✓ | ✓ | ✓ | ✓ | — | ✓ |
| VUMI · With spouse | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| IMG · No spouse | ✓ | ✓ | ✓ | ✓ | ✓ | — | ✓ |
| IMG · With spouse | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Best Doctors | ✓ | ✓ | ✓ | ✓ | ✓ | — | ✓ |
Jordan Rivera · age 35 · Jamaica · budget $500/mo · spouseIncluded = No
| Role | Name | Slug | Note | |
|---|---|---|---|---|
| Applicant | Jordan Rivera | david.bain+e2e-test@incrementic.com | — | Signed once, no co-signer |
VUMI Application (Full) — no spouse signer
Jordan Rivera · age 35 · Jamaica · budget $500/mo · spouseIncluded = Yes · spouse Casey Rivera, age 35
The applicant and spouse sign in two separate DocuSeal sessions. The recorder captured the applicant's completion event, then replayed it against the app's completion endpoint once the spouse finished signing in their own session — that's what produced the merged PDF below.
Spouse signing session: https://docuseal.com/s/5Hd217QFxd9Yn4 (slug 5Hd217QFxd9Yn4), reached via a separate DocuSeal-hosted embed, never touching the app's own pages. Recorder log: “Replayed /api/docuseal/complete after spouse signed — signedDocuments: ["vumi-optimum_vip-application.pdf"]”.
| Role | Name | Slug | Note | |
|---|---|---|---|---|
| Applicant | Jordan Rivera | david.bain+e2e-test@incrementic.com | 3yeBR3tmAnd49y | Signed first, in the app's embed |
| Spouse | Casey Rivera | david.bain+e2e-test-spouse@incrementic.com | 5Hd217QFxd9Yn4 | Signed second, in their own separate DocuSeal session |
VUMI Application (Full) — merged applicant + spouse signatures
Jordan Rivera · age 35 · Jamaica · budget $500/mo · spouseIncluded = No
| Role | Name | Slug | Note | |
|---|---|---|---|---|
| Applicant | Jordan Rivera | david.bain+e2e-test@incrementic.com | — | Signed once, no co-signer |
IMG Application (Full) — no spouse signer
Jordan Rivera · age 35 · Jamaica · budget $500/mo · spouseIncluded = Yes · spouse Casey Rivera, age 35
Same mechanism as the VUMI spouse scenario: the applicant and spouse sign in two separate DocuSeal sessions, and the recorder replays the applicant's completion event against the app's completion endpoint once the spouse's separate session finishes.
Spouse signing session: slug 7ZKcap7X8EsxrM, reached via a separate DocuSeal-hosted embed. Recorder log: “Replayed /api/docuseal/complete after spouse signed — signedDocuments: ["img-gmi_bronze_excluding-application.pdf"]”.
| Role | Name | Slug | Note | |
|---|---|---|---|---|
| Applicant | Jordan Rivera | david.bain+e2e-test@incrementic.com | RHbasUr53YwATW | Signed first, in the app's embed |
| Spouse | Casey Rivera | david.bain+e2e-test-spouse@incrementic.com | 7ZKcap7X8EsxrM | Signed second, in their own separate DocuSeal session |
IMG Application (Full) — merged applicant + spouse signatures
Jordan Rivera · age 35 · Jamaica · budget $500/mo · spouseIncluded = No
Best Doctors has the applicant sign twice on the same form — not a separate co-signer — so there's no spouse scenario for this provider. The Status Matrix's Spouse Signed column is marked N/A here for that reason, not because anything failed.
| Role | Name | Slug | Note | |
|---|---|---|---|---|
| Applicant | Jordan Rivera | david.bain+e2e-test@incrementic.com | — | Signs the form twice (two signature blocks, one signer) |
Best Doctors Application (Full) — applicant signs twice, same form
