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_notifications/models/fp_notification_log.py

@@ -11,7 +11,7 @@ from .fp_notification_template import TRIGGER_EVENTS
 class FpNotificationLog(models.Model):
     """Audit trail for sent notifications."""
     _name = 'fp.notification.log'
-    _description = 'Fusion Plating — Notification Log'
+    _description = 'Fusion Plating - Notification Log'
     _order = 'sent_date desc, id desc'
 
     template_id = fields.Many2one(