Known limitations

Release status — 20 October 2026: Squire 1.0.0-beta.1, including the coach Android app, is published and accepted for beta evaluation. Packaging/signature checks passed, the founder accepted the Galaxy S20+ standalone field/offline walkthrough, and the uploaded Android bundle's APK checksum matches the recorded build. Broader device, accessibility and historical-upgrade coverage are follow-up work, not unfinished beta.1 release gates. Institutions still approve their own environment and privacy/security arrangements before using real athlete data.

Evaluation scope

Use synthetic data for a supported self-hosted beta. First-user coach feedback, sport-task/content review and optional provider validation remain recorded backlog items; they do not reopen accepted implementation stages or establish comprehensive sport coverage.

Before real athlete data

Institutional privacy/security approval, paired database/file recovery, integrated Unix update/rollback rehearsal and retention alert delivery remain open. Branding persistence after service restart is confirmed; that is separate from database restore acceptance.

Product boundaries

The web app serves administrators, coaches and athletes. The published Android beta serves coaches; its attendance, assessment and completion workflow is implemented, with API/emulator evidence. The founder reports the first S20+ walkthrough passed on 20 October; broader device coverage, accessibility and native recovery remain open. Phone guide.

Only downloaded events work offline. Foreground sync requires connectivity; revocation cannot remotely erase an offline device. Performance observations are not medical diagnoses or injury predictions. Injury participation status is limited information subject to consent and institution review.

Remaining evidence

Focused rendered checks for plan, nutrition and event browsing and for multiple message attachments passed in Chromium desktop and WebKit phone emulation (application PR #130). Physical devices and assistive technology remain unverified; consult the current canonical verification record for exact browser coverage and limits. Cloud starters are not provider-tested. Internal support remains local with no outbound delivery. A nonfatal Vite config-loader warning is recorded; the current production web build passes.

Beta.2 limits

Application PR #135 adds sports, coaching teams, concurrent plans, athlete profiles and coach-recorded sessions. The changes are merged; beta.2 publication is being prepared. Known limits:

• Plan overlap compares date ranges, not individual training days or load.
• Events do not carry a sport yet, so a supporting coach's assessment history is limited to events they staffed.
• Recording a session for an athlete is online only and for the current date.
• Its browser checks used Chromium desktop and WebKit phone emulation, not physical devices.
• Upgrading needs the new forward migrations and a paired backup first.

Canonical record

The known issues and beta decision distinguish verified behavior, backlog and publication actions. Updated guidance accompanies PR #127.

Dependency notice — 19 October 2026

An earlier local zero-advisory result used npm offline mode and is invalid as registry evidence. A real online audit found 27 affected package entries. The Xcode-only UUID 11.1.1 fix in application PR #128 reduces that to 19 high entries tracing to two underlying unpatched Expo-tooling dependencies, braces and node-forge. This is not 19 distinct vulnerabilities or proof of zero runtime exposure. No compatible patched releases were verified; npm's proposed Expo/React Native downgrades are not accepted fixes.

Keep development services private and build inputs trusted. The published beta retains these disclosed tooling advisories; track compatible upstream fixes for subsequent builds. Use npm audit --offline=false with network access and inspect its exit status. See the version-pinned known issues and raw online reports for the current scope. This documentation does not publish a new package or change physical-device acceptance.

Automated check baseline — 19 October 2026

Both GitHub Actions jobs passed for reviewed source 1de3db1: clean Linux installation, web unit/build/onboarding checks and the configured backend API/domain suites. View the completed run. The repair PR #128 is merged.

This is evidence for that source revision, not a security certification, a physical-device check or a claim that the dependency notices above are resolved. Future changes require their own relevant checks; see testing.

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.