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_logistics/views/fp_menu.xml

@@ -8,7 +8,7 @@
 
     <!-- ===== LOGISTICS now lives under "Shipping & Receiving" =====     -->
     <!-- (v19.0.3.2.0) Logistics top-level was retired so the same      -->
-    <!-- dock workflow — receiving in, shipping out — sits under one    -->
+    <!-- dock workflow - receiving in, shipping out - sits under one    -->
     <!-- menu root. The receiving module owns the new combined root.    -->
     <!-- Sequences 40+ keep these BELOW the inbound items (10/20/30).   -->
     <!--                                                                 -->
@@ -51,7 +51,7 @@
               action="action_fp_proof_of_delivery"
               sequence="80"/>
 
-    <!-- Phase 2 — Vehicles under Shop Setup. -->
+    <!-- Phase 2 - Vehicles under Shop Setup. -->
     <menuitem id="menu_fp_vehicles"
               name="Vehicles"
               parent="fusion_plating.menu_fp_config_shop_setup"