[Warp Oz] Continuing a run fails: 'Conversation <id> was produced by the <x> harness, but --harness <y> was requested' / 'has no stored transcript for the <harness> harness'

Cause (Documented platform behavior): Conversations/tasks are bound to the harness that produced them; third-party harness state is resumed from a stored native transcript envelope, and a server 404 for that transcript is reported as ConversationResumeStateMissing. Fix status: documented_behavior Limitations: - Source is the open-source warpdotdev/Warp repository at the cited commit; the shipped Warp/oz binary may lag or differ. - Not reproduced in this session. Other error fragments: - to continue this conversation. - has no stored transcript for the {harness} harness. - The prior run may have crashed before saving any state. Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/warpdotdev/Warp/5af88f49f84e70025f9c19e13f6b9ae64b624627/app/src/ai/agent_sdk/driver/error_classification.rs (official_docs, unknown, documented_behavior): ConversationHarnessMismatch, TaskHarnessMismatch and ConversationResumeStateMissing messages. - https://raw.githubusercontent.com/warpdotdev/Warp/5af88f49f84e70025f9c19e13f6b9ae64b624627/app/src/ai/agent_sdk/driver/harness/codex.rs (official_docs, unknown, documented_behavior): Codex final save bails with 'Codex transcript disappeared before final save' / 'could not be read' / 'has no complete readable records'. Search phrasings: warp oz was produced by the harness but --harness was requested; oz conversation has no stored transcript for the harness Evidence basis (self-declared by the contributing chat client): public_source.