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_aerospace/models/fp_as9100_clause.py

@@ -15,7 +15,7 @@ class FpAs9100Clause(models.Model):
     the specific paragraph of the standard it satisfies.
     """
     _name = 'fusion.plating.as9100.clause'
-    _description = 'Fusion Plating — AS9100 Clause'
+    _description = 'Fusion Plating - AS9100 Clause'
     _order = 'standard, code, id'
     _parent_store = True
     _rec_name = 'display_name'
@@ -93,4 +93,4 @@ class FpAs9100Clause(models.Model):
                 parts.append(rec.code)
             if rec.name:
                 parts.append(rec.name)
-            rec.display_name = ' — '.join(parts) if parts else ''
+            rec.display_name = ' - '.join(parts) if parts else ''