D7 · Discord and triage domain: listeners as thin adapters, triage queue API, thread replies via outbox

Notes from the PAR-415 merge (#54):

• Remove these grandfathered ArchUnit entries: TriageService (applyCreate, applyUpdate, search, task → IssueError, TaskModels.Task) and TaskInstructionListener (the TaskSystem field and constructor, contextFor → TaskSystem.defaultWorkspaceId).
• Use the existing seams: triage already calls IssuesFacade, and issues/event/IssueEvents records an event together with its outbox message.

Plan (branch par-420-discord-triage from rebuild). Scope is large, so it ships as two PRs, the second rebased on the first.

PR 1: triage domain + API + web

• triage/TriageFacade is the only entry. It holds two things: (a) the assistant, i.e. the existing @mention//task decide + apply flow, now ai/DecideInstruction (LLM through a new platform/ai/AiGateway port, model from config, rule 23) and usecase/ApplyDecision, with no TaskSystem; (b) the new queue: ListTriageQueue, AcceptTriage, MergeIntoIssue, DeclineTriage(reason), SnoozeTriage(until).
• The queue is the issues in a status of type triage, enriched by a new tenant-scoped triage_item table (V43: Discord source message, bot summary, suggested labels/priority/project, snooze, decision). Possible duplicates come from the existing SemanticIssueSearch / IssuesFacade.rankedSearch. Issue changes go through IssuesFacade, comments through ActivityFacade.addComment (Discord provenance). "Merge" = move to Canceled, comment on both issues, record merged_into; no relation table exists yet.
• REST: /api/public/w/{slug}/triage (GET @MembersOnly; writes need issue.update; added to GuestReadPathTest). No MCP triage tools exist today, so none are added.
• Decisions to Discord threads are enqueued on the outbox as discord.thread_reply (JSON contract; the handler is PR 2).
• Web: domains/triage (data + the PAR-403 two-pane page), sidebar triage count from the API.
• Removes the grandfathered TriageService entries (applyCreate, applyUpdate, search, task, constructor).

PR 2: Discord adapters + outbox

• discord/DiscordFacade: guild to workspace resolution, channel routes and role allow-list (replaces GuildConfigService + the Discord half of IntegrationApiController). It lives in discord, not workspaces: the data is Discord-only and the delivery code needs it.
• Listeners become thin adapters: they build RequestContext.discord(...) from the guild and user (workspace by guild, never TaskSystem.defaultWorkspaceId), validate, call one facade method, reply. No ThreadLocals.
• Outbound messages are outbox handlers with idempotency keys (discord.thread_reply, discord.activity_flush). DiscordDeliveryQueue is replaced by a digest buffer in discord/persistence plus the flush handler.
• REST /api/public/w/{slug}/discord… (settings.manage); web integrations page reads and writes through the API, and the Discord half of lib/sql/integrations.ts is removed.

PR 1 of 2 (triage domain, queue API, triage screen): https://github.com/ParadauxIO/taskl.ie/pull/62 (against rebuild). Part 2 (Discord domain, outbox, integrations settings) is stacked on it and follows.

PR 2 of 2 (Discord domain, thin listeners, outbox delivery, integrations settings): https://github.com/ParadauxIO/taskl.ie/pull/65, stacked on #62. Includes the bridge so the deployment's configured server keeps filing into its workspace.

Both parts are merged into rebuild: #62 (triage) and #65 (Discord).

What changed

• The listeners are now thin adapters. Each one resolves the workspace from the Discord server, then makes one facade call.
• Thread replies and activity flushes go through the outbox, with idempotency keys.
• An unlinked Discord server is told to link itself in Settings. The exception is the deployment's configured server (tasklie.discord.guild-id → tasklie.tasks.tenant-slug), which keeps filing as before. A test covers this.

Ratchet

• ArchUnit store: 564 → 308 distinct entries (normalised), with nothing added.
• ESLint suppressions: 23 → 19.

Follow-ups

• PAR-424: API keys, dropping discord_delivery, and deleting TaskSystem/TenantContext.
• PAR-403: a "Wake now" action, a duplicate match percentage, and a "reply in thread" toggle on screen.
• PAR-404: expose the Discord source on the issue read model, and record it for slash-command issues too.