provider-runtime-integrationlisted

# Provider Runtime Integration Build a provider as a Cradle-owned projection of a native runtime. Preserve native facts at the transport edge and translate them once into the Chat Runtime contract. Do not advertise a native feature until the matching Cradle contract, lifecycle owner, UI state, and verification path exist. ## Workflow 1. Inspect the existing provider adapters, Chat Runtime contract, runtime installation/configuration, stream transport, and relevant UI slot consumers before designing a new integration. 2. Capture and normalize the executable's live protocol. Generate bindings, then add the host lifecycle and typed transport boundary. 3. Map native capabilities, events, tools, and interactions explicitly into Cradle contracts. 4. Make native session state and Cradle run state converge after reconnects or passive-window joins. 5. Verify the normal path and failure paths against a real local binary. Record native capabilities that cannot be faithfully projected. ## Runtime Ownership - Store runtime-owned state under `CRADLE_DATA_DIR/runtimes/<runtime>`. Never write, migrate, or delete provider-owned user-home state such as `~/.<provider>`. - Treat a configured provider target as the host ownership boundary: `N` compatible targets require `N` hosts; sessions on one target share that target's host. - Fingerprint an owned host with the executable identity, target ID, projected configuration, and irreversible credential fingerprint. Exclude session IDs and tempor