Separate Odoo devkit local DX from non-local data operations

[shiny-code-bot]

Intent

Separate odoo-devkit local DX from any non-local Odoo data/runtime operations so Launchplane remains the durable owner for shared and production mutations.

Finish Line

odoo-devkit keeps local DX while shared/prod mutations route through Launchplane or retire

Current Status

State: Ready after owner matrix starts.
Next action: Audit odoo-devkit command groups, docs, run configurations, and templates for remote data/runtime behavior.
Blocked by: No native issue blocker.
Waiting for: Owner matrix to identify exact files.
Last verified: 2026-05-25 platform audit flagged odoo-devkit as local DX plus possible non-local data workflow owner.

Acceptance Criteria

• Local-only commands remain documented as odoo-devkit ownership.
• Any shared/prod mutation path is routed through Launchplane service API or removed.
• Tenant docs no longer point users to odoo-devkit for Launchplane-owned live mutations except through explicit thin Launchplane calls.
• Tests or docs checks prevent reintroducing arbitrary-checkout remote mutation flows.