Threema UX: static file middleware fix, *AIAGENT display, info banner

src/lib/threema-gateway-config.ts

@@ -13,21 +13,19 @@
  *      env var that lists the active account.
  *   2. Move the QR PNG into a server-rendered route that takes a
  *      gateway ID query param.
- *   3. Update consumers (today only ThreemaSetup) to accept the
- *      gateway info as a prop and pass it from a server component.
- *
- * In display contexts we strip the leading asterisk from the Threema
- * ID — customers don't understand the `*X` prefix convention used for
- * Gateway accounts, and the QR code carries the real value anyway. We
- * keep the asterisk only for places where the technical value matters
- * (server-side message routing, debug logs).
+ *   3. Update consumers to accept the gateway info as a prop and pass
+ *      it from a server component.
  */
 
 export const THREEMA_GATEWAY = {
   /** Technical Threema Gateway ID, with leading asterisk. */
   id: "*AIAGENT",
-  /** Display name shown to customers (no asterisk). */
-  displayName: "AIAGENT",
+  /**
+   * Display name shown to customers. INCLUDES the leading asterisk —
+   * customers need to recognise this exact string in their Threema
+   * contacts after scanning the QR, so we don't strip it.
+   */
+  displayName: "*AIAGENT",
   /** Public path to the QR code PNG served from `public/`. */
   qrCodePath: "/threema/qr_code_AIAGENT.png",
 } as const;