Post-stabilization Odoo MCP cleanup and target realignment

[cbusillo]

Objective

Track the repo hygiene that should wait until the surrounding Odoo system and runtime-target repos stabilize, so cleanup does not fight active cross-repo movement.

Finish Line

MCP docs/config/env discovery align with the stable Odoo runtime repos

Current Status

State: Waiting.
Next action: Revisit after the Odoo tenant/workflow stabilization issues settle, then inventory stale docs/config/runtime discovery against the stable target repos.
Blocked by: Launchplane/Odoo tenant orchestration and target-shape stabilization.
Last verified: 2026-05-04; issue #8 was reviewed and the remaining cleanup was judged real but premature while dependent repos are changing.

Scope

• Reconcile README.md, AGENTS.md, .github/github.json, and test docs after the target Odoo runtime shape is stable.
• Replace or remove default discovery paths and messages that still point at retired odoo-ai, unless explicitly retained for archival investigation.
• Decide the durable local IDE/config policy and clean .gitignore / tracked .idea leftovers accordingly.
• Remove stale comments, generated artifacts, dead fixtures, and obsolete docs found during a fresh inventory pass.
• Keep behavior changes small and justified by cleanup safety.

Acceptance Criteria

• MCP target discovery and docs point at the current live Odoo workspace/runtime repos, not retired defaults.
• Any retained compatibility path is explicit, tested, and documented as non-default.
• .gitignore, tracked IDE files, generated artifacts, and local-only leftovers have a clear intentional policy.
• README, AGENTS, tests docs, and workflow metadata agree on commands and cleanup expectations.
• Normal repo gates pass after each cleanup PR.

Relationships

• Supersedes Cleanup pass: docs, dead code, dead files, and stale config #8, which was too broad to keep active while dependent repos are still moving.
• Related to Add post-refactor live Odoo validation coverage #13 for post-refactor live Odoo validation coverage.
• Completed historical Launchplane prerequisite: Absorb remaining product-repo orchestration into Launchplane drivers launchplane#164.
• Current stabilization context: cbusillo/odoo-tenant-cm#21 and cbusillo/odoo-tenant-opw#31.
• related: Add post-refactor live Odoo validation coverage #13 - Add post-refactor live Odoo validation coverage #13

Validation

Use .github/github.json as the source for validation commands. At cleanup time, run the documented no-live-stack gate first, then run live-stack validation only when the target Odoo workspace is expected to be available.

Decisions

• Do not clean up default Odoo target discovery while the Odoo system target shape is actively changing.
• Keep future cleanup in focused PRs rather than broad mixed behavior/doc/config churn.

Open Questions

• What is the canonical default target repo or workspace once Launchplane and tenant orchestration settle?
• Should any odoo-ai compatibility remain as explicit archival support, or be fully removed from runtime discovery?

[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.