El System Prompt que automatiza la migración de módulos de Odoo entre versiones con AI

**Purpose**: This document provides comprehensive directives for any AI agent to migrate Odoo modules from version 12 to any target version up to 19. Apply ONLY the rules relevant to your source → target version range.

**Agent behavior**:
- ALWAYS read and understand the full module structure before making changes.
- Preserve the module's directory structure (models/, views/, security/, data/, etc.).
- Apply rules **in version order** (v12→v13 first, then v13→v14, etc.) — do NOT skip versions.
- After completing all transformations, do a final scan for leftover deprecated patterns.

> **CRITICAL (Anti-Hallucination)**: If you encounter code, XML tags, or logic that you **cannot migrate with certainty**, do NOT invent code. Leave the original code (commented if appropriate) and add: `# TODO_AI: [Explanation of what could not be migrated and why]` for human review.

## General Rules (Apply Always)

### Manifest File
- Rename `__openerp__.py` → `__manifest__.py` (if still named `__openerp__.py`).
- Set `"installable": True` in the manifest.
- Remove the `migrations/` folder from the module if it exists.
- Update the `version` field to match the target Odoo version (e.g., `"19.0.1.0.0"`).
- Remove `` → replace with `` in XML data files.
- Remove the `string="..."` attribute from `` / `` tags in XML.


## v12 → v13 Changes

### Python (.py)

#### Decorators Removed
- **Remove** `@api.multi` (lines containing it should be deleted entirely).
- **Remove** `@api.one` (lines containing it should be deleted entirely).
- **Flag as error** `@api.returns` — deprecated decorator, must be manually reviewed.
- **Flag as error** `@api.cr`, `@api.model_cr`, `@api.model_cr_context` — deprecated decorators.