rename the TIC system agent to event triage

TIC said nothing about what the agent does, and named the wrong thing: the
tick belongs to the scheduler, which is generic and lives outside it. The
agent's only decision is whether an incoming event deserves an interruption
— it sorts, it never acts — so it is now event-triage, matching the
functional naming of the two memory lints.

- agents/tic/ -> agents/event-triage/, module tic/ -> event_triage/,
  TicManager -> EventTriageManager, TicConfig -> EventTriageConfig
- agent id and chat source: "tic" -> "event-triage"
- config keys: tic.* -> event_triage.*, and the config.yml section tic: ->
  event_triage: (greenfield: previously set values fall back to defaults)
- i18n en/it/fr: Event triage / Triage eventi / Tri des evenements; dropped
  the stale "TIC sessions" mention from the debug-pages description
- docs/system-agents.md, docs/index.md, docs/settings.md, CLAUDE.md, SKALD.md

crates/core-api/src/bus.rs

@@ -78,12 +78,12 @@ pub struct ChatEvent {
     pub role:           ChatEventRole,
     pub content:        String,
     /// True for system-generated messages that look like user turns
-    /// (TicManager ticks, notification briefings).
+    /// (EventTriageManager passes, notification briefings).
     pub is_synthetic:   bool,
     /// True when a real user is actively participating in the session
-    /// (web, telegram). False for automated sessions (cron, tic).
+    /// (web, telegram). False for automated sessions (cron, event-triage).
     pub is_interactive: bool,
-    /// True for short-lived task sessions (cron, tic) that have no
+    /// True for short-lived task sessions (cron, event-triage) that have no
     /// long-term conversational value (e.g. skip Honcho memory sink).
     pub is_ephemeral:   bool,
     /// Non-empty only for assistant messages that triggered tool calls.