Confirm seam: app.json identity stays in consumer

[chubes4]

Coupling

app.json defines app identity:

{
  "expo": {
    "name": "Extra Chill",
    "slug": "extrachill-app",
    "scheme": "extrachill",
    "ios": { "bundleIdentifier": "com.extrachill.app" },
    "android": { "package": "com.extrachill.app" },
    ...
  }
}

Why this is fine

app.json is already in the consumer's hands — it's how Expo defines an app's identity. There's no decoupling work to do here; it's just confirmation that the package boundary is correct.

When extrachill-app consumes wp-native-shell, the shell will never touch app.json. Bundle IDs, schemes, names, icons all stay in the consumer.

Acceptance

• (no code change) Confirm wp-native-shell exposes no API that would require modifying app.json
• Document this boundary in the shell README so consumers know what's their job

Related

Part of the wp-native extraction effort. See chubes4/wp-native ROADMAP M5/M7.