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

@@ -1,6 +1,6 @@
-# Step 7 — Tom (Shipper) walks the delivery from draft to delivered.
+# Step 7 - Tom (Shipper) walks the delivery from draft to delivered.
 # Test:
-#   A) Delivery exists post-job-done — what fields visible? what state?
+#   A) Delivery exists post-job-done - what fields visible? what state?
 #   B) Try action_start_route without driver → must block
 #   C) Assign driver + vehicle + box count, schedule
 #   D) Try action_mark_delivered without POD → must block