Decide Odoo image repo retention and runner-health ownership

[shiny-code-bot]

Intent

Decide and implement the right ownership boundary for Odoo image-repo GHCR retention and runner health checks.

Finish Line

Image repos retain build/smoke ownership; retention and runner-health ownership is explicit

Current Status

State: Waiting on owner matrix classification.
Next action: Compare current image-repo ghcr-retention and runner-health workflows against Launchplane runner-host hygiene and package/provider policy surfaces.
Blocked by: No native issue blocker.
Waiting for: Owner matrix classification.
Last verified: 2026-05-25 platform audit identified these as central-policy candidates, not automatic moves.

Acceptance Criteria

• A decision records which repo owns GHCR retention and why.
• A decision records whether runner health remains image-repo telemetry or moves under Launchplane shared runner hygiene.
• If moved, Launchplane has records/evidence/workflows before deleting repo workflows.
• If retained, docs label the workflows as package/build hygiene rather than runtime/provider mutation.