phase 5 dynamic alert registry (bot canonical, settings-site with fallback)

services/patternChecker.js

@@ -7,6 +7,22 @@ const { CONFIG, parseThresholdString } = require('../config');
 const { mongoose } = require('../db-connection');
 const { getAll, get, shouldFireThreshold, onWeeklyReset } = require('./patternStore');
 const { enqueueSend } = require('./channelQueue');
+const { assertKeysRegistered } = require('./notificationRegistry');
+
+// Alert keys this module fires via shouldFire()/standard threshold path.
+// rapid_t2_t3 is intentionally excluded — it uses count-milestone firing below
+// via firedCountMilestones, not the shouldFire() pipeline, so it is not part
+// of the notification registry.
+const PATTERN_ALERT_KEYS = [
+  'user_tickets', 'user_reopen', 'user_crossgame',
+  'game_surge', 'game_backlog', 'game_resolution', 'game_spike',
+  'tag_top', 'tag_escalation', 'untagged_closes', 'tag_game_corr',
+  'user_esc', 'game_esc_rate',
+  'staff_no_close', 'staff_overloaded', 'staff_stale', 'staff_transfer_rate',
+  'staff_esc', 'staff_game_esc',
+  'game_tag_spike', 'overnight_gap', 'staff_always_esc'
+];
+assertKeysRegistered('patternChecker', PATTERN_ALERT_KEYS);
 
 const Ticket = mongoose.model('Ticket');