assess-react-native-migration

1# Assess React Native Migration
2 
3Produce a read-only migration decision. Diagnose the product and delivery system; do not execute the migration.
4 
5## Establish Product Scope
6 
7Run the assessment from a workspace that exposes as many production client codebases as possible. The current checkout is not evidence that it contains the whole product.
8 
9Before assessing readiness:
10 
111. Inspect the current repository and every workspace root available to the agent.
122. Infer supported client platforms from product documentation, CI, release configuration, workspace manifests, submodules, and references to sibling repositories.
133. Locate each production client codebase, including separate native iOS and Android repositories, app variants, and any web client relevant to staffing or proposed code sharing.
144. Record a platform inventory with the client, repository or path, evidence of product membership, and access status.
15 
16When iOS and Android are both supported, inspect both native codebases before recommending a path. If a codebase remains unavailable, mark its evidence `unknown`, state that the assessment covers only the accessible platforms, and lower confidence accordingly. Do not infer that a platform is unsupported merely because its project is absent from the current repository.
17 
18**Scope gate:** every supported production client is listed, and each codebase is accessible, explicitly unavailable, or confirmed not to exist.
19 
20## First Response Gate
21…