[Fix] Automations repeat events when no report qualifies

[roomote-roomote]

​Opened on behalf of @mrubens. View the task or mention @roomote-roomote for follow-up asks.

What changed

• Allow custom automation trigger events to use the existing silent ignore_event path when their prompt says no report qualifies.
• Keep visibility mandatory for pull-request feedback and conflicts, web task settlements, and wakeups configured to always report.
• Cover both the parent-event classification and the no-reply settlement path with focused regressions.

Why this change was made

Custom automations can explicitly require silence when a run finds no qualifying result. Their trigger events were nevertheless classified as requiring a user-visible closeout, so the runtime rejected ignore_event; if destination delivery also failed, the same completed occurrence could be redelivered instead of settling silently.

Impact

Automations with strict report gates can now complete a no-op without posting or entering a redelivery loop. Automations that produce a result still report normally, and platform events that inherently require user visibility remain enforced.

[roomote-community]

1 issue outstanding. See task

• Discord and Teams no-op automations leave their pre-posted “running” placeholder visible. packages/sdk/src/server/lib/fast-agent-parent-event.ts:2945

_{Reviewed d58a2c9}

[roomote-community]

Making automation_triggered optional lets the turn settle through ignore_event, but it does not make destination-backed runs silent. buildFastAutomationConversation posts ${automation.name} is running. before this event is enqueued for Discord and Teams (and creates a Discord channel thread); an ignored turn never calls postReply, so that placeholder is left visible and permanently appears to be running. Defer that root until a report is produced, or explicitly remove/update it when the event is ignored.