# Success Criteria

## Project Success

- Visitors can obtain and privately track valid tickets without duplicate or privacy regressions.
- Staff can call the correct contiguous FIFO batch by ticket count or people count.
- Administrators can configure projects and inspect operational/history data.
- Browser and Android public displays show current batches and forecasts without exposing personal data.
- The dedicated Android project screen announces each new number or range three times without relying on WebView or system TTS; the overview remains silent.

## Task Completion Standard

- Requested behavior is implemented at the correct authority boundary and regression-tested.
- Relevant server, web, Android, packaging, and documentation checks pass.
- User-visible binaries and their documented checksums match the verified build.
- An independent read-only review reports no unresolved P0/P1 finding.
- The task record and project documentation gate are complete before handoff.

## Quality Checks

- Server: `cd server && go test ./...` and, for database behavior, `scripts/test-postgres.sh` or `make smoke-real`.
- Web: `pnpm --dir web test:run`, `pnpm --dir web typecheck`, and `pnpm --dir web build`.
- Android: `android\\gradlew.bat clean testDebugUnitTest lintDebug assembleDebug` with `ANDROID_HOME` configured.
- APK: verify version metadata, v1/v2 signature, embedded resources, and SHA-256 against `deliverables/android/SHA256SUMS.txt`.
- Hardware-dependent display and audio changes require acceptance on the target television; host tests are necessary but not sufficient.

## Last Reviewed

2026-08-12