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_culture/models/fp_value_set.py

@@ -14,10 +14,10 @@ class FpValueSet(models.Model):
     may have several sets (historical, draft, archived) but usually only
     one is marked primary.
 
-    The module ships NO seed data — this is a generic framework.
+    The module ships NO seed data - this is a generic framework.
     """
     _name = 'fusion.plating.value.set'
-    _description = 'Fusion Plating — Value Set'
+    _description = 'Fusion Plating - Value Set'
     _inherit = ['mail.thread', 'mail.activity.mixin']
     _order = 'is_primary desc, name'