Add post-refactor live Odoo validation coverage

[cbusillo]

Objective

After the larger Odoo system refactor stabilizes, add deeper live-stack validation coverage to this MCP repo so refactor regressions are caught against the real Odoo workspace instead of only mocked/unit surfaces.

Finish Line

The MCP repo has a documented live refactor-validation lane that exercises representative real Odoo behavior across model discovery, addon paths, field lookup, inheritance, permissions, and selected MCP tool smoke tests.

Current Status

State: Parked until the Odoo system refactor reaches a stable-enough shape for assertions. The validation plumbing split from #12 is complete.
Next action: Define stable live assertions from the refactored Odoo workspace once the tenant/orchestration repos settle.
Blocked by: Odoo refactor stabilization in related tenant/orchestration repos.
Last verified: 2026-05-16 during cross-repo issue audit; completed #12 was clarified as historical validation plumbing, not a current blocker.

Scope

• Capture stable expected live behaviors after the Odoo refactor settles.
• Add or update live-stack tests/smoke commands for representative MCP tools.
• Cover key refactor-sensitive areas: addon paths, module structure, model info, field lookup, inheritance chains, permission checks, and a small performance/query sample.
• Keep this separate from Make Docker/Odoo integration gates explicit and skip-safe #12, which is validation plumbing and command routing.

Acceptance Criteria

• A future agent can run one documented command/checklist against the live Odoo workspace to validate this MCP after the refactor.
• Tests fail clearly when the refactored Odoo behavior is wrong, not merely when Docker/Odoo is absent.
• Stable expected models/modules/fields are documented or encoded in fixtures after the refactor settles.
• The validation lane is referenced from .github/github.json, README.md, and tests/README.md if those files are the durable command sources at the time.

Relationships

• Completed prerequisite: Make Docker/Odoo integration gates explicit and skip-safe #12 for the no-live-stack/live-stack command split.
• Should be blocked by the durable Odoo refactor tracker once the canonical tracker is identified.
• Likely related current trackers:
  • cbusillo/odoo-tenant-cm#20
  • cbusillo/odoo-tenant-cm#21
  • cbusillo/odoo-tenant-opw#30
  • cbusillo/odoo-tenant-opw#31

Validation

Do not implement deep assertions until the Odoo refactor target behavior is stable enough to avoid encoding churn.

[cbusillo]

PR #14 merged on 2026-05-03 and closed #12, so the validation plumbing is now in place:

• uv run mcp-test is the no-live-stack gate and passes with the documented 75% coverage threshold.
• uv run mcp-test-ci backs GitHub Actions.
• uv run mcp-test-live / uv run mcp-test-live-cov are explicit live Docker/Odoo lanes.

Current blocker for this issue is no longer MCP test plumbing; it is the Odoo-system refactor stabilizing enough to encode durable live assertions. The current local live lane fails loudly because the live stack is mid-refactor (odoo-opw-local:latest missing / volume project mismatch), which is expected for now.

[cbusillo]

Metadata filename correction: .github/github.json is the current repo workflow metadata filename. Any older mention of .github/github.json in this issue should be read as .github/github.json.