Fix dormant Claude wake message race

[kjankov]

Description

Fix a race in the dormant local Claude child wake flow where the child could resume before the triggering lead-agent message was readable and surfaced.

This change:

• threads wake-triggering message metadata through the dormant wake path and persists the wake cursor before relaunch
• primes the Claude parent-bridge state before the resumed wake command runs
• retries message hydration during immediate read-after-event lag
• adds focused regression coverage for the wake path and hydrator retries

Linked Issue

N/A

• The linked issue is labeled ready-to-spec or ready-to-implement.
• Where appropriate, screenshots or a short video of the implementation are included below (especially for user-visible or UI changes).

Testing

• cargo fmt -- --check

• cargo clippy --workspace --exclude warp_completer --all-targets --tests -- -D warnings

• cargo clippy -p warp_completer --all-targets --tests -- -D warnings

• cargo nextest run -p warp dormant_claude_wake_consumer_stops_on_first_target_event

• cargo nextest run -p warp persist_event_cursor_keeps_the_max_sequence_and_updates_history_model

• cargo nextest run -p warp handle_event_batch_persists_max_seq_to_history_model

• cargo nextest run -p warp prepare_local_wake_command_rehydrates_transcript_with_self_managed_listener

• cargo nextest run -p warp prime_parent_bridge_state_for_wake_clears_acked_output_and_surfaces_new_message

• cargo nextest run -p warp read_message_with_timeout_

• I have manually tested my changes locally with ./script/run

Agent Mode

• Warp Agent Mode - This PR was created via Warp's AI Agent Mode

Artifacts

• Conversation: https://app.warp.dev/conversation/81704264-2d81-452d-bc61-5616acc4ea39
• Plan: https://app.warp.dev/drive/notebook/xoam9fPJAH9InaGf64EJTm

CHANGELOG-BUG-FIX: Fixed a race where dormant local Claude child sessions could resume before the triggering lead-agent message was surfaced.
Co-Authored-By: Oz oz-agent@warp.dev

[oz-for-oss]

@kjankov

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

Overview

This PR threads wake-message metadata through the dormant Claude wake flow, primes the parent bridge before relaunch, persists wake cursors, and adds retry coverage for immediate message hydration lag.

Concerns

• The new message-read retry classifier treats errors without a typed HttpStatusError as transient, but the public API response helpers often discard HTTP status into ClientError or a generic anyhow error. Permanent read failures such as auth/authorization/validation errors can now retry until the fetch timeout and be reported as timeouts instead of failing immediately.

Verdict

Found: 0 critical, 1 important, 0 suggestions

Request changes

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[cephalonaut]

Review comments from local branch review.