Auto-mode classifier learns about relayed messages in shared projects

What

In auto mode, a classifier (a check that decides whether an action can go ahead without asking you) reads the conversation to judge approvals. Its instructions for shared Claude Code Projects gained new rules.

• A new section covers a project member's own session, where the coordinator session relays messages into it. Relayed messages count as user turns when the server attributes them to a member.
• A new rule covers marked messages whose lead says "in another thread of this project": they count as the user speaking, but a bare yes approves nothing here. Before, the instructions covered only timeline and in-thread messages.
• The selection of relayed rows now takes a memberSession option.
• The member-session path is controlled first by the environment variable CLAUDE_CODE_AUTO_MODE_HEARTH_MEMBER_RELAY_ROWS, and when that is unset by the flag tengu_hearth_member_relay_rows_enabled, which falls back to off. Without the variable or a value from the server, this path is not reached.
• A killswitch, tengu_projects_other_thread_rows_killswitch, governs the other-thread rows. They are allowed unless the served value is false.

Why

This changes how the classifier treats approvals that arrive from somewhere other than your own thread. A plain "yes" relayed from another thread does not approve an action.