Quarantine retired odoo-ai remote-ops authority

[shiny-code-bot]

Intent

Quarantine retired odoo-ai remote-ops docs/config so future Launchplane and Odoo sessions do not treat archival files as active authority.

Finish Line

Retired odoo-ai files cannot be mistaken for current runtime authority

Current Status

State: Ready after owner matrix starts.
Next action: Audit odoo-ai docs, platform config, compose files, secrets examples, and workflow remnants for active-looking deployment or runtime authority.
Blocked by: No native issue blocker.
Waiting for: Owner matrix to confirm whether anything in odoo-ai is still authoritative.
Last verified: 2026-05-25 platform audit found the repo retired but still containing archival remote-ops material.

Acceptance Criteria

• Active docs clearly say Launchplane, tenant repos, image repos, and devkit are current authorities.
• Archival compose/platform/secret config cannot be mistaken for current production guidance.
• Any remaining historical files are deliberately named, documented, or ignored by discovery/checks.