chore(plating): de-dash shipped code + intake-neutral customer emails

Replace em-dashes and en-dashes with hyphens across 789 shipped source
files (py/xml/js/scss) so the delivered module reads as human-written;
em-dashes had become a recognizable AI-generated tell. Internal .md dev
notes are excluded. The WO-sticker mojibake strippers keep their dash
search targets (now written — / –). No logic changes: comments
and display strings only; validated with py_compile + lxml parse.

Rewrite the 7 customer notification emails to be intake-neutral
(ship-in / drop-off / pickup) and repair-aware, and fix the Shipped
email documents line (packing slip vs bill of lading; certificate only
when issued). Subjects use a hyphen separator.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

fusion_plating/fusion_plating_invoicing/security/fp_invoicing_security.xml

@@ -17,7 +17,7 @@
     <!-- Backward-compat: new Manager role implies old Accounting group.
          2026-05-29: Manager (+ QM + Owner via implication) also gets Odoo's
          Billing group so they can create customer invoices from a Sale
-         Order. Billing only — not Accountant. The SO-origin workflow gate
+         Order. Billing only - not Accountant. The SO-origin workflow gate
          in fusion_plating_jobs is unchanged (off-SO invoices still blocked).
          Spec: docs/superpowers/specs/2026-05-29-manager-invoice-permission-design.md -->
     <record id="fusion_plating.group_fp_manager" model="res.groups">