fix(i18n): drop spaced dashes as separators from every visible string

A dash between two parts of a sentence ("{what} — tomorrow", "Could not
record {name} — try again", "End {name} — …") stands in for a comma, a
colon or a full stop the sentence should say. Every such string in the
seven bundles now says it in plain words. A range keeps its unspaced en
dash ("70–100 mmHg", "{start}–{end}"); that is how a range is written,
not a pause, and the spaced range forms became unspaced ones.

Labels the components put together themselves follow the same rule:
aria-labels read "Move up: Ramipril", a medication and its dose read
"Ramipril 5 mg", page titles use "|", Coach prefills are two sentences,
and the API's user-facing error messages lost their dashes too.

The bundle guard now refuses " — " and " – " beside " · ", with an empty
allowlist, and a sibling guard walks src/components and src/app for a
string or template literal that joins its parts with a spaced dash.

src/app/api/auth/codex/device-poll/route.ts

@@ -47,7 +47,7 @@ export const POST = apiHandler(async (request: NextRequest) => {
     userCode = decoded.userCode;
   } catch {
     cookieStore.delete("codex_device");
-    return apiError("Invalid device-auth state — restart the flow", 400);
+    return apiError("Invalid device-auth state. Restart the flow", 400);
   }
 
   let result;
@@ -56,7 +56,7 @@ export const POST = apiHandler(async (request: NextRequest) => {
   } catch (err) {
     const message = err instanceof Error ? err.message : "unknown";
     annotate({ meta: { codex_device_poll_error: message } });
-    return apiError("Codex device-poll failed — please restart the flow", 502);
+    return apiError("Codex device-poll failed. Please restart the flow", 502);
   }
 
   if (result.status === "pending") {