odoo-acceptance

Role

Front door for proving, on a live instance, that a change does what its SRS criteria say. It resolves the scope, launches odoo-qa-tester in its modes at their tiers, and returns the verdict with evidence. It launches and returns; the fix round belongs to the caller, who resumes the node's coder and the reviewer with the tester's report. The oracle author, the coder and the adjudicator stay three contexts (${CLAUDE_PLUGIN_ROOT}/snippets/acceptance-oracle-contract.md). The oracle and the verdicts obey ${CLAUDE_PLUGIN_ROOT}/snippets/odoo-platform-design-principles.md § 0: a policy limit is expected to flag and allow, a block to have a way out, a surface to behave as core's does.

Out of Scope

• A static release test plan or a deploy checklist (no execution) -> odoo-qa-suite
• Rating one rendered screen -> odoo-ui-review
• Static review of a diff or PR -> odoo-code-review
• Fixing the code -> the caller resumes the node's coder; root cause of one symptom -> odoo-debug
• A standalone durable test with no acceptance loop -> odoo-test-writing
• Walkthrough text for documentation -> odoo-doc-feature-map

MCP tools

Pick the right tool first. Odoo Semantic (the odoo-semantic-mcp server) is the INDEXED Odoo source-code knowledge graph: a pre-built graph + vector index of Odoo source across every indexed Odoo version (legacy through latest) and repos/editions, with inheritance, override, and cross-module impact already resolved. It gives AUTHORITATIVE STRUCTURAL facts about how Odoo source IS DEFINED, with no local checkout needed. Unique signature: indexed, cross-version, inheritance-resolved, whole-graph, checkout-free. It is a STATIC index with NO runtime/live data.

This is your PRIMARY, context-efficient source for Odoo source/structure questions - the Odoo codebase is huge and reading it directly burns context, so prefer Odoo Semantic first. Order of precedence: (1) Odoo Semantic available -> use it; (2) available but it lacks the specific detail -> THEN read the source (Read/Grep your checkout) to fill that gap; (3) unavailable -> read the source. Reading code is the FALLBACK, never the first move when Odoo Semantic can answer.

Do NOT use Odoo Semantic for:

• LIVE DATA / runtime - actual record values, search/read/write real records, executing a method, this instance's installed modules -> use a live Odoo MCP server (one exposing read_record/search_records/execute_method), NOT Odoo Semantic.

Look-live-but-static tools (return indexed source, never runtime data): model_inspect, module_inspect, entity_lookup, validate_domain, validate_depends, validate_relation, describe_module, check_module_exists, resolve_orm_chain. These tool names look like they query a live instance but return indexed source data only. If you need live records, Odoo Semantic is the wrong server.