Inventory Odoo repo operational ownership matrix

[shiny-code-bot]

Intent

Produce the repo-by-repo Odoo ownership matrix that decides what Launchplane must own, what each repo should retain, and what can be deleted without creating churn later.

Finish Line

Repo-by-repo matrix classifies Odoo operational surfaces and cleanup candidates

Current Status

State: Active. Initial matrix drafted from Launchplane source/docs and three read-only agent audits.
Next action: Verify each cleanup candidate in the target repo before opening repo-specific cleanup PRs, starting with the tenant request-wrapper duplication.
Blocked by: No native issue blocker.
Waiting for: None.
Last verified: 2026-05-25.

Initial Matrix

Repo	Keep repo-owned	Launchplane-owned / cleanup target	Current classification
odoo-tenant-cm	Tenant addons, tenant docs, CI/security, product smoke/browser checks, workspace.toml, artifact source declarations, thin Launchplane workflow triggers	Duplicated scripts/ops/request-launchplane-* clients; preview refresh/destroy/apply orchestration details; prod promotion/rollback/post-deploy request plumbing	Transitional thin repo; cleanup unlocked by #900
odoo-tenant-opw	Tenant addons, tenant docs/cutover notes, CI/security, product smoke/browser checks, workspace.toml, artifact source declarations, thin Launchplane workflow triggers	Duplicated scripts/ops/request-launchplane-* clients; prod promotion/rollback/post-deploy request plumbing; preview apply request plumbing	Transitional thin repo; cleanup unlocked by #900
disable_odoo_online	Addon source, manifest, tests, security access, packaging	No Launchplane operational cleanup target found	Repo-owned product/addon code
odoo-shared-addons	Reusable Odoo addons and addon tests	No broad provider/runtime mutation found in quick audit	Repo-owned shared source
odoo-docker	Base runtime image Dockerfile/build workflow, runtime/devtools smoke scripts, downstream helper tests, image provenance	ghcr-retention.yml and runner-health.yml are candidates for explicit central policy or documented repo-local package hygiene	Mostly correct; decision tracked by #903
odoo-enterprise-docker	Private enterprise image build workflow, runtime/devtools smoke scripts, enterprise source protection	ghcr-retention.yml is candidate for explicit central policy or documented repo-local package hygiene	Mostly correct; decision tracked by #903
odoo-devkit	Workspace assembly, local compose/runtime ergonomics, generated workspace docs, PyCharm/run configuration helpers, local-only platform config	Any non-local bootstrap/restore/runtime data mutation guidance or commands should move behind Launchplane service routes or be retired	Needs separation; tracked by #901
odoo-ai	Archival reference only if still useful	Active-looking platform/*, compose, Dokploy, secrets, runner, deploy, and roadmap material should be quarantined or clearly marked obsolete	Retired repo; tracked by #902

Cleanup Gates

• Do not remove a repo-owned operational surface until the matching Launchplane route/workflow/record is verified or an explicit exception is documented.
• Keep product smoke and browser checks close to product source; Launchplane should receive/write evidence rather than own product test implementation.
• Treat tenant workflows as acceptable only when they are thin OIDC calls, not durable state authority or provider mutation.
• Use Add Odoo ownership regression checks #904 to encode the final forbidden/allowed patterns once the first cleanup PR validates them.

Acceptance Criteria

• Matrix includes tenant repos, shared addons, Odoo image repos, odoo-devkit, disable_odoo_online, and retired odoo-ai.
• Each repo has cleanup candidates tied to a Launchplane capability or a named exception.
• The matrix distinguishes source/build/test/local DX from durable operational authority.
• Follow-up implementation issues are updated if the matrix discovers missing Launchplane features.