dguiducci 046f060fcd 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

2026-07-28 21:59:37 +01:00

..

api

rename the TIC system agent to event triage

2026-07-28 21:59:37 +01:00

config.rs

feat(mcp): connector marketplace + split the Connectors surface (§7/§14/§15)

2026-07-16 18:52:59 +01:00

mod.rs

feat(mcp): connector marketplace + split the Connectors surface (§7/§14/§15)

2026-07-16 18:52:59 +01:00

server.rs

uploads: centralise via ChatHubApi::save_upload, refactor handlers

2026-07-22 19:19:29 +01:00