odoo-upgradelisted

# Odoo Upgrade (18 → 19) Migrate custom modules AND their data to a new Odoo major version with runtime verification. This skill orchestrates existing tools first (official `upgrade_code`, OCA `odoo-module-migrate`, vendored MIT pattern references) and adds what none of them have: a **generated breaking-change manifest**, a **semantic per-module brief**, a **runtime verify loop**, and **data-migration script templates** built on `odoo/upgrade-util`. ## Honesty contract (read first, applies to every phase) 1. Never claim a module is "migrated" or "compatible" until `upgrade_verify.py` returns verdict `ok` AND its tests pass. Static analysis verdicts are always phrased as "no known breakage detected", never "safe". 2. Manifest entries under `*_candidates` keys are HEURISTIC (similarity-scored). Present them as candidates with their score; confirm via git history or the target runtime before renaming anything. 3. When unsure how to fix a finding, insert `# TODO(migration): <why>` and list it in the final report instead of guessing silently. 4. `upgrade_brief.py` findings tagged `word-boundary text match` can be false positives — say so when reporting them. 5. Distinguish clearly in all reports: what a script measured vs. what you inferred. ## Outputs All machine outputs go to `/tmp/odoo-ai/upgrade/<module>/`: `precheck.txt`, `upgrade_code.txt`, `module_migrate.txt`, `brief.json`, `source_sweep.json`, `verify.json`, `verify.log`, `report.html`. Fleet run