agent prompt --wait can resolve before the delayed Enter actually submits the prompt

[elentok]

Is this a reproducible bug?

• I confirm this is a reproducible bug, not a feature request, idea, question, contribution proposal, or direction check.
• I reproduced this bug on the version and environment reported below using the exact steps provided.

Current behavior

herdr agent prompt <target> <text> --wait can return success, and --wait can later report the agent as idle/done, while the pane still shows the submitted text sitting unsubmitted in the composer (e.g. /compact never actually starts). Reading the pane shortly after the call still shows the text as the trailing, un-submitted line.

Expected behavior

By the time agent prompt returns (or --wait resolves), the prompt should be fully submitted, or there should be a way to detect/wait for actual submission.

Reproduction

herdr agent prompt <claude-pane> "/compact" --wait --until working then immediately herdr agent read <claude-pane> — the trailing line can still show /compact unsubmitted rather than a started compaction.

Impact

Callers driving agents via the socket/CLI API can't reliably know when a prompt actually started a turn, forcing manual polling workarounds.

Environment

• Herdr version: 0.8.0
• Update channel (stable or preview): stable
• Operating system: macOS
• Terminal: Ghostty
• Shell, if relevant:
• Relevant config, if any: