#35: keep the redesign's source ASCII

The previous commit put four literal non-ASCII characters into source, which
lang-lint rejects (PLAN.md 21.1: all code in English, ASCII-only, enforced by
CI rather than review). Nine lines failed.

The brand mark in the four rails and sign-in cards was a literal lambda, and
the domains screen's meta line joined DMARC, MTA-STS and DANE with a literal
middot. Both are now \u escapes, so the source is ASCII and the rendered page
is unchanged - the served sign-in page emits ce bb for the mark, and the
domains chunk carries the middot as \xb7.

globals.css goes with them. The linter does not scan .css today, so this was
passing, but the stylesheet was the only file in the tree using box-drawing
section rules and em dashes, and there is no reason for it to be the
exception - ASCII hyphens read the same in a comment.

Verified: lang-lint clean, 98 tests green, tsc clean, production build clean.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

services/webmail/src/app/(admin)/admin/domains/page.tsx

@@ -256,9 +256,9 @@ export default function AdminDomainsPage() {
                     <div className="break-words text-lg font-medium leading-tight text-slate-100">{d.name}</div>
                     <div className="mt-1 text-[12.5px] leading-relaxed text-slate-400">
                       {t("admin.mailboxCount", { count: d.mailbox_count })}
-                      {d.dmarc_policy ? ` · DMARC: ${d.dmarc_policy}` : ""}
-                      {d.mta_sts_mode ? ` · MTA-STS: ${d.mta_sts_mode}` : ""}
-                      {d.dane_enabled ? " · DANE" : ""}
+                      {d.dmarc_policy ? ` \u00b7 DMARC: ${d.dmarc_policy}` : ""}
+                      {d.mta_sts_mode ? ` \u00b7 MTA-STS: ${d.mta_sts_mode}` : ""}
+                      {d.dane_enabled ? " \u00b7 DANE" : ""}
                     </div>
                   </div>
                   <div className="flex flex-none flex-wrap items-center gap-2.5">