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

@@ -1,4 +1,4 @@
-# Scenario 9 — Carlos starts step, Bob (supervisor) reassigns to Mike.
+# Scenario 9 - Carlos starts step, Bob (supervisor) reassigns to Mike.
 # Verify chatter audit trail.
 
 from odoo import fields
@@ -36,14 +36,14 @@ print(f'  assigned_user_id: {step.assigned_user_id.name}')
 before_count = len(job.message_ids)
 print(f'  Job chatter messages before reassign: {before_count}')
 
-# Bob reassigns to "another user" — for the test we just write to ourselves
+# Bob reassigns to "another user" - for the test we just write to ourselves
 # to simulate, but the field write IS the operation.
 print()
 print('[Bob] Reassigning step to a different operator...')
 # Use a different user if available.
 other = env['res.users'].search([('id', '!=', env.user.id), ('share', '=', False)], limit=1)
 if not other:
-    other = env.user  # fallback — at least the write fires
+    other = env.user  # fallback - at least the write fires
 step.assigned_user_id = other.id
 step.invalidate_recordset()
 job.invalidate_recordset()