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_configurator/migrations/19.0.22.1.0/pre-migrate.py

@@ -1,5 +1,5 @@
 # -*- coding: utf-8 -*-
-"""Pre-migration for 19.0.22.1.0 — material_process Char → Many2One.
+"""Pre-migration for 19.0.22.1.0 - material_process Char → Many2One.
 
 The material_process field on fp.direct.order.wizard was originally a
 free-text Char tag for shop-level metadata (e.g. "ENP-STEEL-HP-ADVANCED").
@@ -12,7 +12,7 @@ when the new field declaration loads. Per the Express Orders spec
 section 12 (dev-stage, ignore past orders), losing the old Char values
 is acceptable.
 
-Idempotent — IF EXISTS guards mean a re-run is safe.
+Idempotent - IF EXISTS guards mean a re-run is safe.
 """