Validate HealthBridge on devices

Play Mode mocks prove integration logic. Release confidence requires a fresh build and physical-device evidence for every supported platform.

Record the artifact

• Source commit or release identifier.
• HealthBridge and Unity versions.
• Artifact checksum.
• Package or bundle identifier and version.
• Signing identity when available.
• Device model and OS version.

Do not substitute a cached, preinstalled, or unknown artifact.

Base acceptance

1. Fresh install with no prior permission state.
2. Product explanation appears before the system prompt.
3. Platform-correct initialization completes.
4. A known typed read succeeds.
5. Successful empty reads render a valid empty state.
6. Workout imports handle optional fields.
7. Deferred heart-rate monitoring handles stale/missing samples.
8. Backgrounding and returning do not duplicate events or requests.
9. Permission revocation produces recoverable UI.
10. No health payloads or identifiers enter general logs or telemetry.

Permission scenarios

Test full grant, optional denial, core denial, revoke-after-grant, return from settings, and the iOS empty-read ambiguity.

Write and delete scenarios

1. Write one clearly labeled synthetic record or workout.
2. Confirm expected values and source in the platform store.
3. Delete the app-created record by ID.
4. Keep it visible until deletion succeeds.
5. Remove all remaining synthetic records.

Never test deletion against player-owned records.

Route scenarios

Test no route, one point, multiple points, Android consent required, consent denied, and unsupported provider. Keep coordinates out of screenshots and logs.

Report

Mark each lane passed, failed, or not run with artifact identity and observable evidence. A successful Unity build or Play Mode run is not device acceptance.