Thread transcripts are threaded through every auto-reply post, but the supplier returns an empty array in every case.
What
The loop that auto-reacts to comments on an artifact now passes a thread transcript into every post it makes: the fast acknowledgement, the patch-failed or timed-out notice, the substantive reply and the edit path. The supplier that produces it returns an empty array in every case in this build, so no transcript actually reaches those posts. This is plumbing landed ahead of the data.
Details
- The supplier reads the dropped-threads flag and then unconditionally returns an empty list; the consumer reads it back as the thread transcript.
- The edit path is handed the supplier itself rather than its result, so it would pick up any future data lazily.
Evidence
threadTranscript
Strings lifted out of the shipped bundle, so the claim above can be checked against them.