Cobra · Doc/code consistency audit
Cobra UI audit + odoo18_design_reference update
Context
odoo18_design_reference.md existed as a theoretical reference derived from the Odoo 18 source code, but had never been compared against the real code in Cobra's modules. Without that comparison, the doc risked being misleading when simulating screens or generating specs.
What was built
- Reading and analysis of 35 XML files across 9
cobra_*modules - Inventory: button classes, widgets, statusbars, notebooks, visibility patterns
- 5 discrepancies/technical debts identified (residual
oe_highlight, deprecatedattrs=…) - ~60 custom fields across 17 models inventoried, section 17 added to the
.md(11 subsections)
What was hard
- The OWL purchases dashboard lives in
static/src/views/and notviews/— invisible in a naive search - The typo
hepldesk_center_partner_idonres.company: a field in production with the wrong name — absolutely not to "fix" without a migration
Stack
XML (Odoo views), OWL/QWeb, Bootstrap 5, modules cobra_base, cobra_helpdesk, cobra_product, cobra_purchase, cobra_shopify, cobra_field_security, cobra_export_ftp, cobra_product_guarantee, cobra_stock.
What this illustrates
Claude as a consistency auditor between documentation and real code. In a single session, 35 files read, cross-referenced, and synthesized into an actionable document — half a day's work manually, and probably less thorough.