Skip to content

fix: post transcript quote-reply before in-process fan-out - #33

Merged
daopunk merged 1 commit into
mainfrom
fix/patch-quote-reply-bug
Aug 14, 2026
Merged

fix: post transcript quote-reply before in-process fan-out#33
daopunk merged 1 commit into
mainfrom
fix/patch-quote-reply-bug

Conversation

@daopunk

@daopunk daopunk commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

Summary

Voice notes could show a translation or Language Threads relay in the group before 📝 Transcript:. After the one-phone collapse, fan-out no longer waits for Signal to deliver the bot's own transcript, and it was spawned before that quote-reply was sent.

The transcript quote-reply is now sent first; in-chat auto-translate and sidecar relays follow for the original speaker (quote author on !transcribe). A failed send does not fan out. Bot translation replies are still not re-translated.

Fixes #30

Test plan

  • Auto voice: 📝 Transcript: appears in the source chat before any in-chat translation or sidecar relay for the same utterance
  • Quote !transcribe: same ordering; fan-out attributed to the quoted voice author, not the command sender
  • Failed transcript send does not produce a translation or sidecar relay
  • Bot translation replies are not re-translated

Local npm run ci passed (fmt, Clippy, 93.08% line coverage). Unit tests record /v2/send then the fan-out hook and assert ["send", "fanout"].

After the one-phone collapse, translation could land in the group before
the transcript quote-reply. Await that send, then spawn fan-out so
in-chat and Language Threads follow the original speaker.
@daopunk
daopunk merged commit 3639308 into main Aug 14, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: post transcript quote-reply before in-process fan-out

1 participant