odoo-reviewlisted

# Odoo code review — the second gate `odoo-testing` proves a change does what it claims; **this skill catches what it claims that it shouldn't, and what it silently broke elsewhere.** AI-generated Odoo code is the dangerous case: it's syntactically clean, it "works for admin on my machine", and it fails later — for a non-admin user, on the second company, on a list of records, on `-u`, or on a hot list view. Review against the Odoo-specific contracts a linter can't see. **The rule: every finding is either confirmed against the running instance (via `odoo-introspect`) or written down as an explicit assumption to verify — review never adds new guesses.** **Version floor: Odoo 17/18, through Odoo 19 (current LTS).** Deprecation checks below assume 17/18+; for older targets — and for the v18.1 → 19 renames — see `skills/odoo-introspect/references/version-matrix.md`. ## How to review (in order) 1. **Get the diff and the ground truth.** Read the change; run `odoo-ai all <model>` for every model it touches (fields, MRO, security, depends). Half of "review" is just comparing the patch to what the brief says already exists. 2. **Run the checklist below**, severity-first (security → data loss → silent correctness → performance → style). 3. **Confirm, don't assert.** "This field may not exist" → check the brief. "This override may not run" → read the MRO / trace it. Turn each suspicion into a fact or a flagged assumption. 4. **Hand correctness findings to `odoo-testi