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_quality/controllers/fp_qc_controller.py

@@ -90,7 +90,7 @@ class FpQcController(http.Controller):
         }
 
     # ------------------------------------------------------------------
-    # GET state — OWL calls this on mount + after every action
+    # GET state - OWL calls this on mount + after every action
     # ------------------------------------------------------------------
     @http.route(
         '/fp/qc/get', type='jsonrpc', auth='user', methods=['POST'],
@@ -135,7 +135,7 @@ class FpQcController(http.Controller):
         if check.state == 'draft':
             check.action_start()
 
-        # Numeric value handling — write before action to let
+        # Numeric value handling - write before action to let
         # _compute_value_in_range update the record.
         vals = {}
         if value is not None and line.requires_value: