Expo Smoke Test

Prove two things on each platform: the current change works, and the app's core loop still works. Static inspection, type checks, unit tests, and a successful bundle support the result but do not replace device verification.

Establish the run

Inspect the request, the current diff, the Expo config, and the package manifest to identify the flow the change affects and its observable result.

Read root PRODUCT.md when it exists and derive one representative journey from its core loop. Read that file only; never create or edit it. When PRODUCT.md or its core loop is absent, verify the change flow alone and report the missing regression coverage.

Use the installed CLI's version-matched guidance instead of remembered command shapes: