fix(formatters): localize PR buttons, cap oversized content, dedupe status logic

- PR merge/close button labels now follow the group language (actions.merge/close)
  instead of hardcoded Chinese
- clamp content to Discord embed limits (title 256, description 4096, field value
  1024, 25 fields) in formatters plus a render-layer safety net; Telegram gets a
  tag-safe 4096-char cap (capHtml closes dangling tags)
- raise commit subject truncation from 72 to 200 chars (MAX_COMMIT_SUBJECT)
- extract workflowStatus/workflowRunStatus/statusColorKey helpers shared by
  check_run/check_suite/workflow_run/workflow_job
- dedupe deployment ref/sha fields via addDeploymentRefFields
- commit_comment without a commit id uses title_plain (no dangling ???????)
- tag pushes now report 'Tag created'; zh push title includes the {ref}
- sender profile link derives from the repo's forge origin instead of github.com
- group webhook log emoji injected via emojiPrefix, removed from locale files
- dispatchEvent accepts preloaded groups (single KV read per webhook)
- webhook 401 logs distinguish 'secret not configured' from 'invalid signature'

server/lib/drivers/discord/render.ts

@@ -1,5 +1,14 @@
 import type { FormattedMessage, NeutralActionStyle, NeutralMessage } from "../../types";
-import { repoUrlFromMessage, splitMessageTitle } from "../../formatters/helpers";
+import {
+  cap,
+  MAX_DESCRIPTION,
+  MAX_FIELDS,
+  MAX_FIELD_VALUE,
+  MAX_FOOTER,
+  MAX_TITLE,
+  repoUrlFromMessage,
+  splitMessageTitle,
+} from "../../formatters/helpers";
 
 function toStyle(style: NeutralActionStyle): number {
   switch (style) {
@@ -22,29 +31,37 @@ export function renderNeutralMessage(message: NeutralMessage): FormattedMessage
   // rendered as the first line of the description, unlinked.
   const { head, subject } = splitMessageTitle(message.title);
   const repoUrl = repoUrlFromMessage(message.url);
-  const description = subject
+  const rawDescription = subject
     ? message.description
       ? `${subject}\n${message.description}`
       : subject
-    : message.description;
+    : (message.description ?? "");
 
+  // Safety net: clamp every embed part to the Discord API limits so a single
+  // oversized formatter or custom payload can never hard-fail the request.
   return {
     content,
     embeds: [
       {
-        title: head,
+        title: cap(head, MAX_TITLE),
         url: subject ? repoUrl : message.url,
         color: message.color,
-        description,
+        description: cap(rawDescription, MAX_DESCRIPTION) || undefined,
         author: message.author
           ? {
-              name: message.author.name,
+              name: cap(message.author.name, MAX_TITLE),
               icon_url: message.author.iconUrl,
               url: message.author.url,
             }
           : undefined,
-        fields: message.fields,
-        footer: message.footer ? { text: message.footer } : undefined,
+        fields: message.fields
+          ?.slice(0, MAX_FIELDS)
+          .map((f) => ({
+            name: cap(f.name, MAX_TITLE),
+            value: cap(f.value, MAX_FIELD_VALUE),
+            inline: f.inline,
+          })),
+        footer: message.footer ? { text: cap(message.footer, MAX_FOOTER) } : undefined,
         timestamp: message.timestamp,
       },
     ],