{"version":"2.1.268","anchor":"projectsuserturn-flag-threaded-into-verified-relay-marking","canonical_anchor":"projectsuserturn-flag-threaded-into-verified-relay-marking","heading":"New projectsUserTurn flag threaded through turn-origin tracking","tier":"internal","area":"Projects","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/projectsuserturn-flag-threaded-into-verified-relay-marking","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### New projectsUserTurn flag threaded through turn-origin tracking\n\nA new projectsUserTurn flag is now tracked alongside verifiedSlackHumanTurn wherever verified human turns are processed.\n\n**What**\n\n- A new boolean, `projectsUserTurn`, is now threaded through the same turn-processing code paths as the existing `verifiedSlackHumanTurn` flag: message equality checks, turn serialization\/deserialization, and notification queue restore.\n\n- It's set when `isProjectsUser` is true for a verified relayed human turn, and is passed into the function that marks a verified relayed human turn.\n\n**Why** This lets Claude Code distinguish turns that originated from a verified Projects user the same way it already distinguishes verified Slack human turns, keeping turn provenance accurate across these different relay sources.\n\n- Area: Projects\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}