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_bridge_sign/__manifest__.py

@@ -4,14 +4,14 @@
 # Part of the Fusion Plating product family.
 
 {
-    'name': 'Fusion Plating — E-Sign Bridge (EE)',
+    'name': 'Fusion Plating - E-Sign Bridge (EE)',
     'version': '19.0.1.0.1',
     'category': 'Manufacturing/Plating',
     'summary': 'Enterprise bridge: wires Fusion Plating FAIR into Odoo EE Sign for '
                'legally-binding customer CoC acceptance. Auto-installs when Sign '
                'and fusion_plating_quality are both present.',
     'description': """
-Fusion Plating — E-Sign Bridge
+Fusion Plating - E-Sign Bridge
 ==============================
 
 Enterprise bridge module.
@@ -23,7 +23,7 @@ this bridge installs automatically and adds:
 * Linked ``sign.request`` state displayed on the FAIR form
 * Signed PDF attachment preservation and quick-view action
 
-This module never installs on Community Edition — it depends on the EE
+This module never installs on Community Edition - it depends on the EE
 ``sign`` module. Safe to ship in the product bundle; simply won't activate
 where ``sign`` is unavailable.
     """,