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_quality/views/fp_fair_views.xml

@@ -38,7 +38,7 @@
         <field name="arch" type="xml">
             <form string="First Article Inspection Report">
                 <header>
-                    <!-- Phase D5 — FAIR Approve/Reject = sign-off equivalent;
+                    <!-- Phase D5 - FAIR Approve/Reject = sign-off equivalent;
                          QM-only per spec section 2.C (FAIR/Nadcap signing is
                          restricted to Quality Manager regardless of who can
                          see / create the FAIR record). Submit-for-review and