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_receiving/migrations/19.0.3.9.0/post-migrate.py

@@ -11,7 +11,7 @@ field), leaving every auto-generated receiving line with an empty
 to prefill ``received_qty``.
 
 This migration walks existing receiving records and rebuilds the line
-metadata from the linked SO's order lines via position-based zip — only
+metadata from the linked SO's order lines via position-based zip - only
 when the receiving line count matches the SO line count (otherwise the
 mapping isn't safe and we leave the record alone for manual review).
 """
@@ -52,7 +52,7 @@ def migrate(cr, version):
         """, (so_id,))
         so_lines = cr.fetchall()
         if len(so_lines) != len(recv_line_ids):
-            # Mismatch — don't risk corrupting a non-trivial mapping.
+            # Mismatch - don't risk corrupting a non-trivial mapping.
             skipped += 1
             continue
         # Receiving lines come ordered by id ascending (the create call