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_quality/scripts/bt_s13_verify.py

@@ -32,9 +32,9 @@ if not plating:
     plating = job.step_ids.sorted('sequence')[3:4]
 plating.instructions = (
     '<p><b>Plating bath checklist:</b></p><ul>'
-    '<li>Verify nickel concentration is 4.0–5.5 g/L (Fischerscope reading)</li>'
-    '<li>pH must be 4.4–4.8 — adjust with ammonium hydroxide if needed</li>'
-    '<li>Bath temp 88–93°C, agitation ON</li>'
+    '<li>Verify nickel concentration is 4.0-5.5 g/L (Fischerscope reading)</li>'
+    '<li>pH must be 4.4-4.8 - adjust with ammonium hydroxide if needed</li>'
+    '<li>Bath temp 88-93°C, agitation ON</li>'
     '<li>Dwell 45 minutes for 25 µm coating; longer for thicker</li>'
     '<li>Rinse for 60s before next station</li></ul>'
 )
@@ -57,7 +57,7 @@ from odoo.http import request as _req
 # Find code prefix used
 print(f'  Step code: {plating.id}, name: {plating.name}')
 
-# Direct call to the scan response builder (no http) — easier approach:
+# Direct call to the scan response builder (no http) - easier approach:
 # The scan endpoint builds the dict inline. Verify by replicating its code path.
 step = plating
 payload = {