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_certificates/views/res_partner_views.xml

@@ -71,7 +71,7 @@
         </field>
     </record>
 
-    <!-- Sub 6 — Per-contact routing flags on the contact's own form
+    <!-- Sub 6 - Per-contact routing flags on the contact's own form
          (opens when editing a child contact row). Applied to every
          res.partner form so delivery-location partners and their child
          contacts both surface the same flags. -->