You are reading the documentation for Squire 1.0.0-beta.2. Read the latest guide
Guides
Testing and acceptance
Separate code checks from operational and human evidence.
Release status — 22 October 2026: Squire 1.0.0-beta.2 is published for evaluation; the stable 1.0.0 release remains planned. The release package checks passed, but no beta.1-to-beta.2 physical-device upgrade or verification of the uploaded bytes against the published build is claimed. Broader device, accessibility, privacy/security, recovery and institution operations still need review before live athlete data.
Focused checks
Run relevant commands in the application repository; do not run every suite for a documentation-only edit.
npm test
npm run build
npm run backend:typecheck
npm run backend:test
npm run content:check
npm run docs:check
The testing guide supplies service/database/browser prerequisites. Use disposable acceptance databases; never reset or reseed an existing preview.
Recorded checks, 19 October 2026
A fresh production web build passed. Documentation validation passed two isolated checker regression fixtures and checked 313 local links plus 14 heading fragments across 53 maintained documents, including infrastructure. External URLs are outside that local checker.
Six focused mobile request/client/selection cases, 18 queue cases and mobile TypeScript checks passed. The updated signed APK built and passed package/signature checks. These source checks are separate from the founder-reported S20+ phone pass on 20 October; broader native acceptance remains open. See dated evidence and limits.
Human and operational review
Evaluate separate administrator, coach and athlete roles, revoked access, private conversations, first setup and recovery with synthetic identities. Inspect English/Arabic on intended devices. See current canonical verification for the completed focused R0 web browsing/multi-attachment checks. Broader native accessibility, provider validation and institution operations remain separate.
On 20 October 2026, the founder reported that the instructed Galaxy S20+ standalone installation and field/offline-recovery walkthrough worked as intended. This is a successful owner-reported physical-phone check. Android version, the installed APK checksum and per-locale/accessibility results were not supplied; broader device, tablet, accessibility and historical-upgrade coverage remain separate. See the recorded phone result and application PR #136.