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.0.0/pre-migrate.py

@@ -9,11 +9,11 @@ Actions:
   1. Rename `fp_direct_order_wizard.notes` → `terms_and_conditions`.
      Existing data preserves its semantic (always was customer-facing because
      the old `action_create_order` wrote it to sale.order.note).
-  2. Add the new Express columns (idempotent — IF NOT EXISTS guards).
+  2. Add the new Express columns (idempotent - IF NOT EXISTS guards).
   3. Backfill `pricelist_id` from the legacy `currency_id` via any active
      pricelist matching the currency. After this, the model's stored-related
      currency_id (related='pricelist_id.currency_id') takes over.
-  4. (No currency_id column drop here — Odoo's schema sync recognises the
+  4. (No currency_id column drop here - Odoo's schema sync recognises the
      related field and keeps the column shape; data refreshes from the
      related lookup on subsequent writes.)
 
@@ -58,7 +58,7 @@ def migrate(cr, version):
         ALTER TABLE fp_direct_order_wizard
         ADD COLUMN IF NOT EXISTS view_source VARCHAR DEFAULT 'legacy'
     """)
-    # Note: view_source defaults to 'legacy' for EXISTING rows — they were
+    # Note: view_source defaults to 'legacy' for EXISTING rows - they were
     # created via the legacy view. New rows default to 'express' via the model.
 
     # 3. Backfill pricelist_id from any active pricelist matching the