A coding-session lookup that initially fails can become fully readable after its ingestion

A coding-session lookup that initially fails can become fully readable after its ingestion projection catches up; retry the authoritative transcript API before concluding that raw storage access is required.

When this applies: the session is visible in telemetry or raw-ingest metadata but the transcript-oriented lookup returns no row or a singleton/coercion error. The safest sequence is (1) verify the exact native session ID, (2) allow for projection lag, and (3) retry the transcript API with full-content retrieval. This does not apply when the raw collector never observed the session or when authorization blocks the caller.