isConversationalInjection: exempt chat:edited / chat:deleted (and chat:reaction-remove) markers like chat:reaction

[Tengro]

Summary

isConversationalInjection (src/framework.ts, around line 170 on main 8b612f5) treats an injected message as real conversational input unless it is a system marker or carries chat:reaction:

if (m.system === true) return false;
if (Array.isArray(m.tags) && m.tags.includes('chat:reaction')) return false;
return true;

zulip_mcp PR antra-tess/zulip_mcp#23 (issue #22) starts delivering message edits, topic moves and deletions as synthetic incoming messages tagged chat:edited / chat:deleted (RFC-001 core tags, already in mcpl-core 0.3.0's CHAT_TAGS). Those are markers about a message the agent has seen, not something it is replying to — the same category as a reaction. As written they:

• clear explicit-send suppression: an agent that just send_messaged and then sees [edited] … Ann: typo fix on the channel gets its same-round prose auto-routed again;
• count as a "new conversational round" for anything else keyed on this predicate.

chat:reaction-remove has the same gap today (only chat:reaction is listed), so a reaction being removed already behaves differently from one being added.

Proposed fix

const NON_CONVERSATIONAL_TAGS = new Set(['chat:reaction', 'chat:reaction-remove', 'chat:edited', 'chat:deleted']);
…
if (Array.isArray(m.tags) && m.tags.some((t) => NON_CONVERSATIONAL_TAGS.has(t))) return false;

Routing is unaffected on the zulip_mcp side (change lines carry no threadId and are excluded from lastIncoming), so this is only the suppression / round-boundary half.

Raised from the review of antra-tess/zulip_mcp#23 so the rollout chain is visible: zulip_mcp can ship first (the markers are correct without this), but until this lands an edit marker arriving mid-turn can re-open auto-routing.

[Tengro]

Sibling point from the round-2 review of antra-tess/zulip_mcp#23: ChannelRegistry takes every accepted incoming message as defaultPublish* (src/mcpl/channel-registry.ts around line 734 on main), reactions included, so context.incoming / the default publish target can point at a synthetic marker id (reaction:…, edit:…, delete:…) rather than the message the agent is replying to. The zulip_mcp side keeps its own reply routing clean (markers never touch lastIncoming), but the host-side default should skip the same non-conversational tag set proposed above, in the same change.