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

@@ -13,12 +13,12 @@ class FpValueRotation(models.Model):
 
     Used to drive "Fundamental of the Day/Week/Month" programs. The admin
     creates a rotation, picks a set and a period, and enables it. This
-    module does NOT ship an ir.cron — the shop admin wires a cron to call
+    module does NOT ship an ir.cron - the shop admin wires a cron to call
     `_cron_advance_rotation` if they want automatic advancement. Many
     shops prefer to advance the rotation manually at a weekly stand-up.
     """
     _name = 'fusion.plating.value.rotation'
-    _description = 'Fusion Plating — Value Rotation Schedule'
+    _description = 'Fusion Plating - Value Rotation Schedule'
     _inherit = ['mail.thread']
     _order = 'name'
 
@@ -133,7 +133,7 @@ class FpValueRotation(models.Model):
         """Cron entry point.
 
         A shop admin can wire an ir.cron to this method. The module
-        intentionally does not ship one — different shops want different
+        intentionally does not ship one - different shops want different
         cadences. Only advances rotations whose next_rotation_date is
         today or earlier.
         """