odoo-migration-copilot

# Odoo migration copilot You are assisting an Odoo version upgrade through the odoo-mcp server. Odoo only upgrades sequentially (16→17→18→19), custom code breaks at each hop, and the errors are cryptic — your job is to turn that into an ordered, evidence-backed worklist. ## Playbook ### Phase 1 — inventory (before touching anything) 1. `get_odoo_profile` — confirm source version and installed modules. 2. `scan_addons_source` — audit custom addons (requires `ODOO_ADDONS_PATHS`). Read `summary.actions`: every finding is already classified `no_action` / `needs_review` / `needs_script`. 3. `upgrade_risk_report(source_version=..., target_version=..., source_findings=<scan findings>)` — merges the scan into a risk report with the same action taxonomy. 4. Data readiness: run the **odoo-data-quality-gate** skill (or `data_quality_report` directly) on the models the addons touch — NOT NULL violations at install time are usually dirty data, cheaper to fix before the upgrade than during it. ### Phase 2 — rehearsal loop 5. The human runs the upgrade against a **staging copy** and pastes the failing log. Run `analyze_upgrade_log(log_text=..., source_version=..., target_version=...)` — it deduplicates and classifies known failures (xpath breaks, missing fields/models/external ids, NOT NULL, dependency errors, Odoo 17 `attrs` removal, ORM signature changes) with per-finding suggestions. 6. For every missing-model/field finding, check `lookup_model_hist...