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_program.py

@@ -16,11 +16,11 @@ class FpNuclearProgram(models.Model):
     revision, the target N299 level, supplier certification status, and
     the audit cadence (internal, customer, CNSC awareness).
 
-    A facility can have more than one nuclear program — e.g. a Level 3
+    A facility can have more than one nuclear program - e.g. a Level 3
     program for OPG work and a separate NQA-1 program for a US utility.
     """
     _name = 'fusion.plating.nuclear.program'
-    _description = 'Fusion Plating — Nuclear Quality Program'
+    _description = 'Fusion Plating - Nuclear Quality Program'
     _inherit = ['mail.thread', 'mail.activity.mixin']
     _order = 'facility_id, name'