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

@@ -49,9 +49,9 @@ class ResPartner(models.Model):
'for commercial customers.',
)
# Aerospace / Defence cert toggles (2026-05-27 sub
# Aerospace / Defence cert toggles (2026-05-27 - sub
# docs/superpowers/specs/2026-05-27-recipe-cert-toggles-design.md).
# Default False opt-in for aerospace/defence customers only.
# Default False - opt-in for aerospace/defence customers only.
# Resolver _resolve_required_cert_types reads these alongside the
# existing x_fc_send_coc / x_fc_send_thickness_report. The three
# cert types (nadcap_cert / mill_test / customer_specific) are
@@ -61,7 +61,7 @@ class ResPartner(models.Model):
default=False, tracking=True,
help='Auto-spawn a Nadcap-type fp.certificate when a job for '
'this customer reaches awaiting_cert. Operator attaches '
'the supplier/PRI-issued PDF before clicking Issue '
'the supplier/PRI-issued PDF before clicking Issue - '
'there is no QWeb auto-render for this type.',
)
x_fc_send_mill_test = fields.Boolean(
@@ -78,10 +78,10 @@ class ResPartner(models.Model):
'issuing.',
)
# ---- Sub 6 Per-contact communication routing -----------------------
# ---- Sub 6 - Per-contact communication routing -----------------------
# These five flags live on CHILD contacts under a company partner.
# When every contact under a company leaves them blank, the resolver
# falls back to the company's own `email` matching the pre-Sub-6
# falls back to the company's own `email` - matching the pre-Sub-6
# behaviour exactly. Admins opt in to per-contact routing by ticking
# the relevant flag on each contact row.
x_fc_receives_certs = fields.Boolean(
@@ -117,7 +117,7 @@ class ResPartner(models.Model):
'visibility into everything the shop sends out.',
)
# ---- Sub 12c+ Per-customer cert statement override ----------------
# ---- Sub 12c+ - Per-customer cert statement override ----------------
x_fc_cert_statement = fields.Text(
string='Cert Statement Override',
help='Override boilerplate text printed in the Certificate of '
@@ -134,7 +134,7 @@ class ResPartner(models.Model):
# when a job ships); the rest are CC'd when the CoC is emailed. Sales
# sets the list once per customer. Falls back to manual selection at
# action_issue time if blank. Self-referential M2m (renamed from the old
# single Many2one x_fc_default_coc_contact_id see migration 19.0.10.2.0).
# single Many2one x_fc_default_coc_contact_id - see migration 19.0.10.2.0).
x_fc_default_coc_contact_ids = fields.Many2many(
'res.partner',
relation='fp_default_coc_contact_rel',