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_jobs/models/account_move.py

@@ -5,7 +5,7 @@
 
 1. Block direct creation of out_invoice / out_refund for ALL users
    including administrators. The only legal entry points are:
-     * sale.order._create_invoices()  — sets context fp_from_so_invoice=True
+     * sale.order._create_invoices()  - sets context fp_from_so_invoice=True
      * manual create() with invoice_origin matching an existing sale.order.name
 
 2. Once a customer move is created via a legitimate path, derive its
@@ -98,7 +98,7 @@ class AccountMove(models.Model):
         # it doesn't survive the copy. Allow reversals through as long
         # as the reversed entry is itself a customer-facing move (which
         # means it already went through this validator at original
-        # creation time — the audit trail is intact).
+        # creation time - the audit trail is intact).
         reversed_id = vals.get('reversed_entry_id')
         if reversed_id:
             parent = self.env['account.move'].sudo().browse(reversed_id)
@@ -139,7 +139,7 @@ class AccountMove(models.Model):
         portal = job.portal_job_id
         if 'invoice_ref' in portal._fields:
             portal.invoice_ref = self.name
-        # Recompute state via the central helper — it'll only land on
+        # Recompute state via the central helper - it'll only land on
         # 'complete' if the WO is actually done AND the shipment is
         # delivered. Posting an invoice early no longer skips the floor.
         if hasattr(portal, '_fp_recompute_portal_state'):