fix(cua-driver): preserve named CLI sessions

[f-trycua]

Summary

• keep explicit named sessions alive across independent one-shot CLI calls
• retain disposable cleanup for calls without a public session label
• add a process-level regression test for start, inspect, list, and end

Root cause

The one-shot CLI always minted a disposable transport owner and ended it immediately after every call. Named sessions were attached to that owner, so start_session succeeded and was then torn down before the next CLI process could inspect or reuse it.

User impact

Shell-oriented callers could not follow a named run across CLI calls even though the lifecycle contract supports repeated public session labels.

Fix

Explicit labels now use the daemon-scoped CLI ownership namespace and rely on explicit end_session or idle expiry. Anonymous calls keep their per-call owner and synchronous cleanup.

Checks

• cargo fmt --all -- --check
• cargo test -p cua-driver --test daemon_required_test --locked
• cargo test -p cua-driver --bin cua-driver --locked
• cargo clippy -p cua-driver --tests --locked

Refs #3007

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.