54b2c0ea38
`_find_live_session_by_key` matched live runtimes by bare stored session id. Stored ids are timestamp-based and can exist in more than one profile's store, so `session.resume` for profile B (fast path, post-build re-check, and `_claim_or_reuse_live`) could hand back profile A's live runtime — the turn then ran with A's persona/tools and wrote A's memory (#100029). Give the lookup an optional `profile_home` (default: any profile, unchanged for callers that have no profile to scope by) using the same string compare `_find_live_unpersisted` already uses, and pass the resolved home at every resume/claim site. `_claim_parked_runtimes` gets the same scope so a resume under B never finalizes A's parked runtime of the same id. Reimplements the profile-scope half of #100213 by @Finn763; the Group-title capability-sync change from that PR is intentionally not carried. Co-authored-by: Finn763 <165816600+finn763@users.noreply.github.com>