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>
This commit is contained in:
gsinghpal
2026-06-05 00:16:19 -04:00
parent c9eb61ee0c
commit 8c76a16366
789 changed files with 4692 additions and 4692 deletions

View File

@@ -7,17 +7,17 @@
<odoo>
<!-- ================================================================== -->
<!-- RECORD RULES Multi-company isolation -->
<!-- RECORD RULES - Multi-company isolation -->
<!-- ================================================================== -->
<record id="fp_kpi_company_rule" model="ir.rule">
<field name="name">Fusion Plating KPI: KPI multi-company</field>
<field name="name">Fusion Plating KPI: KPI - multi-company</field>
<field name="model_id" ref="model_fusion_plating_kpi"/>
<field name="global" eval="True"/>
<field name="domain_force">['|', ('company_id', '=', False), ('company_id', 'in', company_ids)]</field>
</record>
<record id="fp_kpi_value_company_rule" model="ir.rule">
<field name="name">Fusion Plating KPI: KPI Value multi-company</field>
<field name="name">Fusion Plating KPI: KPI Value - multi-company</field>
<field name="model_id" ref="model_fusion_plating_kpi_value"/>
<field name="global" eval="True"/>
<field name="domain_force">['|', ('company_id', '=', False), ('company_id', 'in', company_ids)]</field>