pub fn mint_exec_id() -> StringExpand description
A fresh exec id: x- plus 16 hex characters, the Python client’s shape.
Here rather than in each binding, because both bindings carried a byte-identical copy of this function — and the id’s shape is part of the session story (“the exec id is caller-minted”), so the crate that tells that story is the crate that mints.
Not a crate: the id needs to be distinct rather than unguessable — it is an idempotency key, not a credential, and the daemon rejects an unknown one — so the nanosecond clock mixed with a counter is enough, and a CSPRNG dependency for it would not be.