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

@@ -15,7 +15,7 @@ class FpValue(models.Model):
     icon for display in kanban tiles.
     """
     _name = 'fusion.plating.value'
-    _description = 'Fusion Plating — Value'
+    _description = 'Fusion Plating - Value'
     _order = 'set_id, sequence, number, name'
 
     name = fields.Char(
@@ -94,7 +94,7 @@ class FpValue(models.Model):
         result = []
         for rec in self:
             if rec.number:
-                result.append((rec.id, f'#{rec.number} — {rec.name}'))
+                result.append((rec.id, f'#{rec.number} - {rec.name}'))
             else:
                 result.append((rec.id, rec.name))
         return result