Run Sprint 5 assortment, mobile and small-load validation

[linear]

Purpose

Validate the retailer-assortment foundation and mobile QR consumer path before either is presented as delivered.

Required validation

• Signed-in admin/retailer assortment CRUD and stable QR reprint.
• Anonymous scan on a mobile viewport with a non-expert walkthrough.
• Exact quantity enforcement, invalid/expired QR handling and regeneration within the same assortment.
• Confirm PR feat(fir-178): add in-store assortments schema and admin management #349's recorded live migration/adviser result, then exercise signed-in admin CRUD, RLS/RPC role paths and retailer-funded credit behaviour.
• Preview or deployed multi-user check with 5-6 users when the environment is available.
• Record defects, fixes and retest outcomes.
• Record Vercel access failures separately from application failures.

Linked work

• feat(fir-178): add in-store assortments schema and admin management #349, In-store assortments: schema + admin management #348 assortment foundation
• feat(fir-168): add assortment QR consumer flow #350, Implement retailer fixed-assortment consumer flow and assortment deep link #336 QR consumer flow
• Testing and Validation
• Sprint 5 hub

Current status

In progress. PR #349 records live migration application and an adviser check; signed-in admin CRUD, RLS/RPC role paths, mobile non-expert and multi-user validation remain open.

Sprint 5 update, 31 August

The implementation baseline is now merged: assortment foundation PR #349, QR flow PR #355, credit-reservation fix PR #366, public-generation completion PR #369 and My Store console PR #374. Validation remains open and now explicitly includes:

• Scan a printed QR with a real phone and complete the public /a/[token] flow.
• Create/edit an assortment in /my-store, regenerate its stable QR and open the real test-show path.
• Verify mobile recovery, invalid token handling, quantity constraints and cold-analyser completion.
• Distinguish the real assortment/activity data from the dashboard's clearly labelled illustrative credit and usage metrics.

Do not close from merge evidence alone; retain the issue until the manual and role-path evidence is recorded.

[linear]

FIR-171