Symptom: default team set to PAR, but new bot-filed issues kept landing in MCN.
Cause: the triage LLM freely set groupKey from the issue's topic, and in resolveGroupId an explicit groupKey wins over the guild's default team — so the default never applied. (The config-level TASKS_DEFAULT_GROUP_ID is a third team, so MCN could only have come from the model.) The default team also affects task creation only, never where activity is posted.
Fix (tesks 82cf6a8): TriageService.decide() now takes the guild's default team and names it in the prompt, and the system prompt instructs the model to leave groupKey null unless the user explicitly names another team — never inferring one from the topic. So a configured default sticks unless you say e.g. "put this in DSN". Threaded the default through TaskInstructionListener → decide(). Covered by TriageDefaultTeamTest.
Pending Release → dev (auto-deploys from develop).