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/step8_verify.py

@@ -1,4 +1,4 @@
-# Step 8 — Jane creates the invoice for the completed SO and posts it.
+# Step 8 - Jane creates the invoice for the completed SO and posts it.
 # Test:
 #   A) SO has invoice_status = 'to invoice' after delivery
 #   B) Jane creates the invoice
@@ -40,7 +40,7 @@ if so.invoice_status == 'to invoice':
     except Exception as e:
         print(f'  ❌ {e}')
 else:
-    print(f'  Skipped — invoice_status={so.invoice_status} (nothing to invoice)')
+    print(f'  Skipped - invoice_status={so.invoice_status} (nothing to invoice)')
     new_invs = env['account.move'].browse()
 
 # Path B: post.