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_jobs/models/fp_job_consumption.py

@@ -3,7 +3,7 @@
 # License OPL-1 (Odoo Proprietary License v1.0)
 # Part of the Fusion Plating product family.
 #
-# Phase 1 (Sub 11) — relocated from fusion_plating_bridge_mrp.
+# Phase 1 (Sub 11) - relocated from fusion_plating_bridge_mrp.
 # MRP-flavoured fields (production_id, workorder_id) replaced by their
 # native fp.job / fp.job.step equivalents.
 
@@ -14,14 +14,14 @@ class FpJobConsumption(models.Model):
     """A single consumable drawdown charged to a plating job.
 
     Sources include bath replenishment applied against a job, masking tape
-    rolls, PPE, nickel salts — anything that has a cost and should roll
+    rolls, PPE, nickel salts - anything that has a cost and should roll
     into job costing.
 
     Kept deliberately lightweight: one row per event, cost derived from
     `product.standard_price` at log time (snapshot, not reactive).
     """
     _name = 'fp.job.consumption'
-    _description = 'Fusion Plating — Job Consumption'
+    _description = 'Fusion Plating - Job Consumption'
     _order = 'logged_date desc, id desc'
 
     job_id = fields.Many2one(