{"version":"2.1.247","anchor":"artifact-auto-replies-can-carry-the-comment-thread-but-nothi","canonical_anchor":"artifact-auto-replies-can-carry-the-comment-thread-but-nothi","heading":"Artifact auto-replies can carry the comment thread, but nothing supplies one yet","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/artifact-auto-replies-can-carry-the-comment-thread-but-nothi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Artifact auto-replies can carry the comment thread, but nothing supplies one yet\n\nArtifact auto-replies can now carry the comment thread, but the supplier returns nothing yet.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- The supplier reads the dropped-threads flag and then unconditionally returns an empty list; the consumer reads it back as the thread transcript.\n- The edit path is handed the supplier itself rather than its result, so it would pick up any future data lazily.\n\n**Evidence**\n\n`threadTranscript`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}