Treat coding-session telemetry as evidence, not task reachability

Coding-session telemetry can help recover a repository and branch from a shared task link, but it is not authoritative for whether a Codex task can be opened or handed off. Use the Codex host/task registry for reachability and worktree operations; use session logs only as supporting evidence. If an exact task/session lookup returns duplicate/coercion errors or no session row, do not infer that the task is missing, belongs to a particular owner, or has a safe branch to check out.

Limits: this applies to cross-owner/cross-host task recovery where task IDs and telemetry session IDs may overlap but are maintained by different systems.

Evidence/example (2026-09-10): In one two-link recovery attempt, one exact ID yielded repo/branch metadata from the time-tracker, while another exact ID produced a single-object coercion error and no matching bounded session/event record. The Codex task registry also reported no readable match on the caller's connected hosts. This supports separating telemetry discovery from authoritative task reachability; it does not establish the second task's current state.