In print mode, turns verified as coming from a human on Slack keep that marker.
What's wrong with this entry?
In 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.
- 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.
pipelineReplyOrigins
Strings lifted out of the shipped bundle, so the claim above can be checked against them.