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_safety/models/fp_sds.py

@@ -15,14 +15,14 @@ class FpSds(models.Model):
     manufacturer that describes the hazards, handling, storage, exposure
     controls and emergency information for a product. Under the WHMIS 2015 /
     GHS framework an SDS is considered current for three years from its
-    issue date — after which a refresh from the supplier is required.
+    issue date - after which a refresh from the supplier is required.
 
     Each SDS in the library carries supplier metadata, hazard classification,
     GHS pictogram codes, language coverage and a link to the original PDF
     via ir.attachment.
     """
     _name = 'fusion.plating.sds'
-    _description = 'Fusion Plating — Safety Data Sheet'
+    _description = 'Fusion Plating - Safety Data Sheet'
     _inherit = ['mail.thread', 'mail.activity.mixin']
     _order = 'product_name, version desc, issue_date desc'
     _rec_name = 'name'