{"version":"2.1.233","anchor":"slack-verified-human-turns-carried-through-the-print-path","canonical_anchor":"slack-verified-human-turns-carried-through-the-print-path","heading":"Slack-verified human turns carried through the print path","tier":"notice","area":"Relay","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/slack-verified-human-turns-carried-through-the-print-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Slack-verified human turns carried through the print path\n\nIn print mode, turns verified as coming from a human on Slack keep that marker.\n\n**What**\n\nIn non-interactive print mode, the marker saying a turn came from a verified human on Slack is now copied onto the message record. The queue side already used that marker to decide prompt priority and whether to fold turns together; the print path did not. Slack and relay-connected sessions only.\n\n**Details**\n\n- Shared state also gained a map recording, per session, where a reply came from and which tool-use id it expects, marked consumed once matched.\n\n**Evidence**\n\n`pipelineReplyOrigins`\n\n- Area: Relay\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 3\/5"}