Compose Multiplatform

Step 1: Define the shared UI contract

1. DEFINE new app/screen | target addition | shared UI migration | state/recomposition | resources/localization | lifecycle/ViewModel | navigation | native interop | accessibility | UI test | preview/hot reload | packaging | platform bug.
2. IDENTIFY products/modules, Android/iOS/desktop/JS/Wasm targets, minimum OS/browser/JDK, shared versus native UI, platform entry points, window/safe-area/input behavior, state owner, navigation owner, resources, accessibility contract, host matrix, and distribution artifacts.
3. READ the current Compose Multiplatform overview, compatibility table, and destination release notes before setup or upgrade.
4. PRESERVE existing module/source-set boundaries, design system, state/event contract, navigation routes, resource IDs, platform shells, and distribution identifiers unless the request changes them.
5. ROUTE Android BLE inspector/diagnostic surfaces to android-ble-inspector, generic KMP targets/hierarchy/publication to kotlin-multiplatform, compiler/toolchain/cache mechanics to kotlin-gradle, Kotlin behavior to kotlin-development, and Swift framework/device deployment to kotlin-native-apple-interop/xtool.

Completion: target/host matrix, shared UI boundary, platform shells, state/navigation ownership, accessibility behavior, and proof surfaces are explicit.

Step 2: Inspect the project and version tuple

RUN from the target repository root:

python3 scripts/inspect-project.py --root . --json