fix: persist OpenCLI carrier handle before peer readback

[James3014]

#117 formal G2 exposed a transport/lifecycle seam after the first worker parked successfully: slot 2 timed out during OpenCLI provisioning before the runtime durably recorded its exact conversation handle. The current OpenCLI driver sends the peer-status probe with --wait false, but it waits for the conversation to become idle and for peer identity readback before returning any evidence to the registry. A later timeout therefore collapses an already-created carrier into a headless outcome_unknown.

This change separates handle acquisition from peer identity resolution. The exact conversation URL/fingerprint is persisted first, peer identity is then resolved read-only from that same conversation, and bootstrap still requires the authenticated peer fingerprint. A restart between those phases resumes identity readback from the saved handle without reprovisioning. The OpenCLI provision lease is extended to cover the additional bounded identity phase; CDP behavior keeps its existing phase count.

Regression coverage checks that the handle is available before detail/readback, malformed or timed-out peer identity fails closed while preserving the handle, deferred identity still binds bootstrap authority to the authenticated peer, and a cold resume does not create another conversation. Local executable tests were not run because the current DevSpace dependency-sync gate requires a paired carrier and this isolated worktree has no node_modules; git diff --check passed. GitHub CI is the executable verifier for this exact Candidate dac2bd023cbc40f09a9224a0b892dd89b4db06ec.