deploy/preflight: normalizeTriggerProviderAliases overwrites triggers when an alias collides with its canonical provider

[kjgbot]

Where

packages/deploy/src/preflight.ts — normalizeTriggerProviderAliases()

const normalized: NonNullable<AgentSpec['triggers']> = {};
for (const [provider, list] of Object.entries(triggers)) {
  normalized[aliases[provider] ?? provider] = list;
}

Problem

If an agent declares triggers under both an alias and its canonical name (e.g. google-mail and gmail), both keys normalize to gmail and the second assignment overwrites the first — silently dropping a set of triggers. Assignment should merge the lists.

Suggested fix

const key = aliases[provider] ?? provider;
normalized[key] = [...(normalized[key] ?? []), ...list];

Edge case (an agent is unlikely to declare both), but the failure is silent — dropped triggers never register and never fire.

---

Found by CodeRabbit while reviewing the vendored snapshot of this file in AgentWorkforce/skills#87.

[kjgbot]

@kjgbot, Factory needs clarification before dispatching 295.
Reason: low-confidence triage: No repository route matched; escalate for human routing.
Question: Which repository or repositories should handle this issue? For "deploy/preflight: normalizeTriggerProviderAliases overwrites triggers when an alias collides with its canonical provider", please reply with: (1) the exact user flow—where it starts, required inputs/actions, and the successful result; (2) permissions, validation, failure behavior, important edge cases, and anything out of scope; and (3) observable acceptance checks or tests. Say "use reasonable product defaults" for anything Factory may decide. After an authorized GitHub reply, Factory will dispatch agents; successful work will be opened as a pull request.
Authorized responder: @kjgbot (the issue reporter).
Reply with a comment that starts with [factory-reply:factory-triage-22qsg].