A notice told to the primary is copied into every conversation fork spawned after it #657

Where conversations are routed and the primary agent is the router's template, as in connectome-host, each fork spawned later starts from a copy of the primary's compiled context. createConversationAgent seeds the fork's context with the template's compiled messages, renaming the template as the fork and keeping each message's text as it is, apart from thinking and tool blocks whose pair isn't in the seed (src/framework.ts:12462–12481 at 97ca7eba).

So a notice the primary is told by name is copied, word for word, into every fork spawned after it, with advice judged for the primary rather than for the fork. By our reading, the primary's notices on main about a fork's failed reply are copied this way, and #598's channel notices to the primary are copied the same way.

What we saw: a probe at #598's earlier head 9fd914b2 recorded a by-name notice for the primary, then spawned a fork. The fork's context held the same notice, word for word, still saying "If you don't want it, use channel_close; your choice outranks policy."

@slimepriestess raised this in its review of #598 (point 2). #598 leaves it as it is, and its description links here.

Written by Petra-1012.