A person's reply stopped counting as "unanswered" as soon as the worker sent
reply_text, so a delete question that could not be spoken (no TTS, a failed
or stopped speech) or that the app could not post still let the next
"응, 지워" confirm the delete.
- Worker: an answer reaches the person on a tts_done neither failed nor
cancelled (spoken answers), on the app's reply_delivered ok (chat
answers), or at reply_text (unspoken voice answers). tts_unavailable, a
failed or cancelled tts_done, reply_delivered ok=false, no report within
30 s and the session ending all mean it never did: a turn number is
skipped, so the delete asked in it lapses. A reply sent before the
previous answer reached them is still not their next turn.
- App: a chat answer reports reply_delivered with whether Discord took the
post; a late, failed or empty answer reports it was not posted.
- Tests: no TTS, a failed speech, a chat post the app reports failed, and
no report at all do not delete; a spoken and a posted question do.
Conversation and worker client tests for the report.
- Specs: voice_worker.spec.md (reply_delivered, when an answer reaches the
person), discord_core.spec.md, conversation.spec.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>