Add event-readiness smoke tests for auth, scan, pit, rescue, and admin pause

[neerpatel]

Objective

Add event-readiness smoke tests for the critical end-to-end race flow.

Details

The repo currently lacks explicit coverage for the event path that matters most: auth, routing, scanning, pit-stop behavior, rescue, and admin race control. Add a lightweight but repeatable smoke suite that protects those paths.

Checklist

• Define the minimum critical-path scenarios for event readiness.
• Add automated coverage for the core smoke path where practical.
• Document the required manual checks for device-specific scanning behavior.
• Make the smoke checks part of the repo verification workflow.

Dependencies

Related to #12, #18, #19, #22, #26, and #41.

Notes

This should emphasize confidence for a live event rather than exhaustive test coverage.

[neerpatel]

Backlog review on 2026-04-12.\n\nCurrent status: Partially complete.\n\nImplemented:\n- Browser E2E coverage exists for critical auth/guard/scanner flows in .\n- CI already runs web E2E and fails regressions (, job).\n\nRemaining:\n- A single event-readiness smoke matrix covering pit-stop, rescue, and admin pause paths is not yet codified.\n- Manual device-specific scanning validation steps are not yet documented as a standard runbook.

[neerpatel]

Superseding note (shell interpolation correction) — backlog review on 2026-04-12.

Current status: Partially complete.

Implemented:

• Browser E2E coverage exists for core auth/guard/scanner flows in apps/web/tests/e2e/appFlows.spec.ts.
• CI already runs web E2E and fails regressions via .github/workflows/test.yml (web-e2e job).

Remaining:

• A single event-readiness smoke matrix covering pit-stop, rescue, and admin pause paths is not yet codified.
• Manual device-specific scanning validation steps are not yet documented as a standard runbook.