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_nuclear/models/fp_nuclear_pedigree.py

@@ -14,8 +14,8 @@ class FpNuclearPedigree(models.Model):
     Nuclear pedigree is the unbroken chain of traceability from the raw
     material a plated part was made from, through every processing
     step, to the finished and shipped component. Nuclear operators use
-    pedigree records decades after shipment — long after the original
-    work order has aged out of normal systems — which is why the
+    pedigree records decades after shipment - long after the original
+    work order has aged out of normal systems - which is why the
     retention clock is driven by the N299 level rather than a generic
     document-retention rule.
 
@@ -24,7 +24,7 @@ class FpNuclearPedigree(models.Model):
     the normal change-control process.
     """
     _name = 'fusion.plating.nuclear.pedigree'
-    _description = 'Fusion Plating — Nuclear Pedigree Record'
+    _description = 'Fusion Plating - Nuclear Pedigree Record'
     _inherit = ['mail.thread', 'mail.activity.mixin']
     _order = 'ship_date desc, id desc'