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_batch/models/fp_batch.py

@@ -73,7 +73,7 @@ class FpBatch(models.Model):
         domain="[('state', '!=', 'retired')]",
         tracking=True,
     )
-    # Phase 6 (Sub 11) — workorder_id / production_id retired (MRP gone).
+    # Phase 6 (Sub 11) - workorder_id / production_id retired (MRP gone).
     # Native equivalents: x_fc_step_id (fp.job.step) + x_fc_job_id (fp.job)
     # are added by fusion_plating_jobs and carry the same traceability.
     part_count = fields.Integer(string='Part Count')