Observed
The deploy-phase Full-stack E2E job (apps/web-e2e/stack/signup-journey.spec.ts) has failed on every main push since the nav-rail rebuild. The signup journey asserts toHaveURL(/\/respite$/) after onboarding but the run lands on /avatars, and the logout test clicks a Menu button the rail no longer renders.
Expected
The full-stack signup journey drives the current shell — onboarding to the avatar roster, create an avatar, into the game — and passes, so Deploy runs and Verify fleet clears.
Repro
Any main push. The stack journey predates two shell changes it was never updated for: the roster gate now sends a fresh account to /avatars (it must create an avatar before entering), and the always-on nav rail dropped the Menu toggle in favour of direct links.
Notes
Deploy is gated on Full-stack E2E, so it has been skipped every merge since the regression landed — the Fly fleet is stale and Verify fleet fails against images that were never deployed. Fixing the one stack spec unblocks the deploy pipeline. Same migration already applied to the mock-backed specs in #682; this is the deploy-only stack spec left behind.
Observed
The deploy-phase
Full-stack E2Ejob (apps/web-e2e/stack/signup-journey.spec.ts) has failed on everymainpush since the nav-rail rebuild. The signup journey assertstoHaveURL(/\/respite$/)after onboarding but the run lands on/avatars, and the logout test clicks aMenubutton the rail no longer renders.Expected
The full-stack signup journey drives the current shell — onboarding to the avatar roster, create an avatar, into the game — and passes, so
Deployruns andVerify fleetclears.Repro
Any
mainpush. The stack journey predates two shell changes it was never updated for: the roster gate now sends a fresh account to/avatars(it must create an avatar before entering), and the always-on nav rail dropped theMenutoggle in favour of direct links.Notes
Deployis gated onFull-stack E2E, so it has been skipped every merge since the regression landed — the Fly fleet is stale andVerify fleetfails against images that were never deployed. Fixing the one stack spec unblocks the deploy pipeline. Same migration already applied to the mock-backed specs in #682; this is the deploy-only stack spec left behind.