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_kpi/models/fp_kpi.py

@@ -184,7 +184,7 @@ class FpKpi(models.Model):
     def _kpi_otd(self, today):
         """Portal jobs shipped on or before target_ship_date (last 30 d).
 
-        NOTE: fusion.plating.portal.job has no facility_id — the
+        NOTE: fusion.plating.portal.job has no facility_id - the
         facility filter on this KPI type is therefore ignored.
         """
         cutoff = today - timedelta(days=30)
@@ -271,7 +271,7 @@ class FpKpi(models.Model):
     def _kpi_bath_uptime(self, today):
         """Operational baths / active baths * 100.
 
-        Bath has facility via tank_id.facility_id — filter is supported.
+        Bath has facility via tank_id.facility_id - filter is supported.
         """
         extra = self._company_clause('b')
         if self.facility_id: