Load the matching OpenUpgrade framework by default for native20 crossings #410

Finish the retained matching Odoo 20 framework default source on existing draft PR 411 and remove the actual draft-child hold on the repaired 403/405/407 train stack by earning readiness. This is milestone source delivery, not a runtime upgrade or migration operation.

Read issue 410 and every comment, PR 411 and every comment, the source handoff on OPW 314 comments 6817852660 and 6818169591, the adopted source instruction on OPW 471 comment 6685404577, and the completed finisher handoff on devkit 404 comment 6829665687. Recheck current heads, source custody, actual train and readiness holds before changing anything. Resume released claim 6721524119 with authored release 6818001816 and the concrete cleared custody evidence. Claim your own issue before using your own configured external task worktree. Do not use the predecessor's tree or revive its session.

The observed draft is PR 411 at 1dd946511dc5c0b67101ebbd69447700134b4c33, branch work/opw314-framework-default-1108, based on work/opw314-actions-1107. The other current heads in the handoff are PR 403 at 0fcf6f0e658f0f7aaee478d789656b2594bc3019, PR 405 at 346328bae8d791f1de714cdd23f7bd0757894c77 and PR 407 at bc3bb0391dcf044bf0bddb99dee55d7ad9fab538. They have checked Ready after 405's Client notes were repaired. The next train pass reports stack_unsupported because draft 411 has no earned readiness. Verify these are still the current facts. Do not mark anything Ready solely to unblock a parent.

Own the remaining exact-head source review, meaningful tests, required local and CI gates, native IDE inspection, tenant consumer-build qualification and accurate Client test notes under repository instructions. Reuse still-valid immutable evidence where the contract permits. The existing consumer evidence is on PR 411 comment 6746550809: OPW Build 42647834936 consumed this exact devkit head and produced the immutable image used in the qualified run030 and testing restore. Build capability is not a new runtime or staff pass. The previous Google review timed out without a verdict; the shared Pydantic inspection was UNKNOWN. Read those exact records and earn or honestly dispose of the remaining proof instead of promoting historical limitations into passes. Fix actual source defects within this existing change if necessary and get a weighed review for the resulting exact head.

Preserve source ancestry and all consumed frozen inputs. No force push, stack collapse, manual merge or retarget is assigned. Update the existing canonical PR through ordinary fast-forward if a source change is required; no duplicate PR. Keep its current parent relationship through normal train delivery. Claim another source group before editing an accompanying parent's source. Once the exact candidate is eligible, add truthful Client test notes, remove draft status and run checked Ready through the GitHub skill. Own train follow-through until the stack lands or a concrete external blocker is handed off. Preserve current-head evidence and reconcile owning issues after actual landing.

This is source and CI only. No migration, restore, data copy or deletion, guest/store/lane/hold/account/release/production operation is authorized. OPW 488 already has the sole host storage owner. Do not touch its folders or the stock worker's trees or retained native-run images. Developer-Artifacts has an urgent low-space condition; use existing caches and the supported heavy-run preflight for synthetic container checks, avoid large duplicate outputs and stop an allocation that cannot be safely admitted. A full real migration is not a validation requirement here. No Client invitation or new Director question is assigned unless an actual reserved decision remains.

Return exact source and current train outcome on issue 410, naming any remaining hold and its owner. Keep original and successor task trees and private evidence accounted for. End through work-closeout with exact claim releases, complete audit, no own background tasks and an unqualified Safe to exit: yes only when earned. Notify the lead through the native route in your header. Rules for this brief: https://github.com/cbusillo/codex-skills/blob/main/skills/supervisor/references/brief-rules.md