@ai-matrx/records 0.30.0 → 0.36.0

package/dist/use-cases/index.cjs

@@ -2163,10 +2163,24 @@ var PLACEHOLDER_PATTERNS = [
     instead: "Write the sentence this business would really send."
   },
   {
+    // TWO Zs, NOT THREE (widened 2026-09-21, lane ZZ-SWEEP-2). `ZZ W4-AGG Red`,
+    // `ZZ HQ`, `zz_a_deal` are the same junk as `ZZZ …` and were the larger
+    // half of it: 791 of them across 88 campaign-suite files when this widened.
+    //
+    // BUT A LEADING `zz` ON A DATABASE TRIGGER IS NOT A NAME, IT IS AN ORDERING
+    // DEVICE. PostgreSQL fires triggers in alphabetical order of their name and
+    // gives no other way to say "last", so this platform spells "last" with
+    // z's: 591 live triggers across 79 distinct names — `zz0_table_owner`,
+    // `zz_memo_clear_i`, `zzz_history_capture_s_u`, `zzzz_unique_rule_holds` —
+    // where each extra z buys another rung. A suite that asserts which triggers
+    // fire on `custom.record` MUST quote those names exactly. Reddening on them
+    // would be this file's own "catch the junk, never the vocabulary" rule
+    // broken, so a line that is talking about triggers is exempt.
     id: "zzz-prefix",
-    test: /\bzzz+[\s_-]/gi,
-    why: "A 'ZZZ \u2026' name exists to sort test rows to the bottom and to be deleted; it makes every screen look broken.",
-    instead: "Give it the use case's own name and find it for cleanup by the organization's cleanup tag."
+    test: /\bzz+[\s_-]/gi,
+    unlessLineMatches: /\btriggers?\b|\btgname\b|\btgrelid\b|\btgenabled\b|\bpg_trigger\b/i,
+    why: "A 'ZZ \u2026' / 'ZZZ \u2026' name exists to sort test rows to the bottom and to be deleted; it makes every screen look broken.",
+    instead: "Give it the use case's own name and find it for cleanup by the organization's cleanup tag. (On a TRIGGER the prefix is a firing-order device, not a name \u2014 say 'trigger' on the line and it is exempt.)"
   },
   {
     id: "test-table",