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:
@@ -3,7 +3,7 @@
|
||||
# License OPL-1 (Odoo Proprietary License v1.0)
|
||||
|
||||
{
|
||||
'name': 'Fusion Plating — Delivery Tasks',
|
||||
'name': 'Fusion Plating - Delivery Tasks',
|
||||
'version': '19.0.1.1.0',
|
||||
'category': 'Services/Field Service',
|
||||
'summary': 'Local delivery dispatch with GPS tracking and route planning.',
|
||||
@@ -28,7 +28,7 @@
|
||||
'views/res_config_settings_views.xml',
|
||||
],
|
||||
'post_init_hook': '_fusion_tasks_post_init',
|
||||
# Map view assets temporarily disabled — JS imports may not resolve on
|
||||
# Map view assets temporarily disabled - JS imports may not resolve on
|
||||
# factory enterprise Odoo 19. Needs path verification.
|
||||
# 'assets': {
|
||||
# 'web.assets_backend': [
|
||||
|
||||
@@ -20,7 +20,7 @@
|
||||
<!-- ================================================================== -->
|
||||
<!-- FIELD TECHNICIAN GROUP -->
|
||||
<!-- Standalone group safe for both portal and internal users. -->
|
||||
<!-- Do NOT imply base.group_user — that chain conflicts with portal -->
|
||||
<!-- Do NOT imply base.group_user - that chain conflicts with portal -->
|
||||
<!-- users (share=True). -->
|
||||
<!-- ================================================================== -->
|
||||
<record id="group_field_technician" model="res.groups">
|
||||
|
||||
Reference in New Issue
Block a user