odoo-code-tracerlisted

# Odoo Code Tracer Use this skill to map how Odoo code actually executes. Trace only what you can verify in code. If a path is uncertain, mark it as uncertain and explain what evidence is missing. ## First Move Identify the starting point: - HTTP route or controller - form/list button action - server action or automated action - cron job - ORM method called by another addon - compute, onchange, constraint, inverse, or create/write/unlink hook - report render - OWL/web client action calling backend code - external webhook or integration callback Detect the target Odoo version. If a version-specific reference exists, consult it before tracing version-sensitive behavior: - Odoo 17: `odoo-17.0` - Odoo 18: `odoo-18.0` - Odoo 19: `odoo-19.0` If `$ODOO_SOURCE` is set, inspect local framework code for controller dispatch, ORM behavior, decorators, web client actions, assets, tests, and version-specific execution details. ## Tracing Process 1. Locate the entry point with file and line reference. 2. Follow the direct method call chain. 3. Follow inheritance and `super()` calls through parent implementations. 4. Check decorators and implicit triggers: `@api.depends`, `@api.constrains`, `@api.onchange`, inverse methods, `@api.ondelete`, create/write/unlink overrides. 5. Follow XML wiring: buttons, actions, menus, reports, cron records, server actions, and external IDs. 6. Follow frontend wiring when relevant: asset bundle, JS module, registry entry, service call, RPC/ORM call, t