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_bridge_maintenance/__manifest__.py

@@ -3,13 +3,13 @@
 # License OPL-1 (Odoo Proprietary License v1.0)
 
 {
-    'name': 'Fusion Plating — Maintenance Bridge',
+    'name': 'Fusion Plating - Maintenance Bridge',
     'version': '19.0.1.2.2',
     'category': 'Manufacturing/Plating',
     'summary': 'Bridge standard Odoo Maintenance with Fusion Plating equipment, '
                'plans, checklists, and sensor integration.',
     'description': """
-Fusion Plating — Maintenance Bridge
+Fusion Plating - Maintenance Bridge
 ====================================
 
 Extends Odoo's standard Maintenance module for electroless nickel plating

fusion_plating/fusion_plating_bridge_maintenance/models/fp_maintenance_label.py

@@ -8,7 +8,7 @@ from odoo import fields, models
 class FpMaintenanceLabel(models.Model):
     """Simple tag model for equipment labels."""
     _name = 'fp.maintenance.label'
-    _description = 'Fusion Plating — Equipment Label'
+    _description = 'Fusion Plating - Equipment Label'
     _order = 'name'
 
     name = fields.Char(string='Name', required=True)

fusion_plating/fusion_plating_bridge_maintenance/models/fp_maintenance_node.py

@@ -12,7 +12,7 @@ class FpMaintenanceNode(models.Model):
     Auto-numbered on creation.
     """
     _name = 'fp.maintenance.node'
-    _description = 'Fusion Plating — Maintenance Node'
+    _description = 'Fusion Plating - Maintenance Node'
     _order = 'number desc'
 
     name = fields.Char(

fusion_plating/fusion_plating_bridge_maintenance/models/fp_maintenance_plan.py

@@ -12,7 +12,7 @@ class FpMaintenancePlan(models.Model):
     Plans are selected when creating maintenance events.
     """
     _name = 'fp.maintenance.plan'
-    _description = 'Fusion Plating — Maintenance Plan'
+    _description = 'Fusion Plating - Maintenance Plan'
     _inherit = ['mail.thread']
     _order = 'name'
 
@@ -57,7 +57,7 @@ class FpMaintenancePlan(models.Model):
         self.ensure_one()
         return {
             'type': 'ir.actions.act_window',
-            'name': f'Items — {self.name}',
+            'name': f'Items - {self.name}',
             'res_model': 'fp.maintenance.node',
             'view_mode': 'list,form',
             'domain': [('plan_id', '=', self.id)],

fusion_plating/fusion_plating_bridge_maintenance/views/fp_maintenance_menu.xml

@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="utf-8"?>
 <odoo>
 
-    <!-- Phase 1 — re-parented under Plating → Operations. Maintenance
+    <!-- Phase 1 - re-parented under Plating → Operations. Maintenance
          is an Operations concern, not a separate top-level. -->
-    <!-- Phase D (perms v2) — Shop Manager+ only. Operators don't need
+    <!-- Phase D (perms v2) - Shop Manager+ only. Operators don't need
          to schedule plans or browse the equipment registry. -->
     <menuitem id="menu_fp_maintenance"
               name="Maintenance"