build(deps): update pinned uv image to 0.12.24

[shiny-code-app]

The original Dependabot update could not use the canonical qualification refresh route because its author differs from the automation claim author. This replacement carries the same pinned official uv image update, 0.12.22 → 0.12.24, on current main through the configured automation identity.

Refs #112. Supersedes odoo-docker#111 infrastructure dependency update. Only the uv tag and digest change; runtime layout and downstream contracts are preserved.

Local arm64 qualification passed: runtime and runtime-devtools builds and smoke checks, database initialization/health endpoint, downstream helpers, Hadolint, requirements overrides, dependency-health evaluator and Odoo wrapper tests. The runtime reports uv 0.12.24. Local default-input builds do not substitute for frozen-input amd64 CI scans.

PyCharm inspection is UNKNOWN/project_open_blocked: configured preparation succeeded, but the running IDE never exposed the exact worktree before the helper timeout, so no native changed-file inspection ran. Whole-project inspection was stopped before a native run because the same unresolved opening prerequisite forbids another assessment. The exact helper lease remains retained pending supported ownership reconciliation, tracked by codex-skills#1531 stale-lease cleanup and jetbrains-inspection-api#433 project opening. This is an explicit inspection limit, not a clean IDE result. No application launch, profile suppression or gate weakening. Documentation and workflow metadata were checked; dependency values remain owned by the Dockerfile and no behavior/routing documentation changes are needed. The maintained review policy does not require a commissioned model review for this tested dependency-only update. Background review is not yet observable.

Client test notes

Nothing for the Client to test: this changes only the pinned uv image dependency; image builds and smoke checks cover compatibility. Supervisor owns merge-train entry and landing after the current-head checked Ready handoff. This work does not publish images or deploy CM or OPW.

[shiny-code-app]

The replacement is preserved and locally qualified, but remains held: the checked Ready helper refused failing CI and posted no handoff.

Supervisor acts next through the repository-supported train retry route for run 38459513122. Then recheck the current head and call gh-pr.py --repo cbusillo/odoo-docker ready 120 only when checks permit it. Nothing is needed from Chris for that supported routing. odoo-docker#112 qualification remains active.

At ea8dd05f0612a9fe6db2defdf8759d2d458a68ce, source resolution, lint and override checks passed. resolve_inputs was canceled at its configured 20-minute deadline; image-verification failed downstream and image verification builds were skipped. The resolver log's last operation before cancellation is the successful pinned Ubuntu image pull. It provides no fresh HTTP 503 evidence, and the uv image is not consumed by that resolver. No branch regression is demonstrated. The checked Ready response is confirmed write_outcome: not_started, two failing signals, zero pending/unfinished workflows. No direct rerun was attempted: AGENTS.md assigns reruns to the merge train or Chris.

The original odoo-docker#111 dependency PR is closed with the replacement link. Stable patch IDs match exactly. Local qualification and Client test notes are in this PR body; the helper occurrence retains the inspection UNKNOWN and exact lease recovery. No matching background review is observable for this head; no commissioned review is in flight.

The watcher and tests have stopped. Temporary image tags and test containers/networks are removed. Supervisor custody retains the clean pushed work/odock111-2 checkout, ignored IDE/SDK state, exact lease 193872e8-2418-4698-9299-9ebf612c2490 and task qualification receipts until supported ownership recovery and landing/closure; then retire with the host's dev-worktree command. Previous qualification artifacts and the clean but stale primary main remain untouched. No publish, deployment, tag, dispatch, train label or manual merge.

[shiny-code-app]

Current Status

SWEEP-IMG diagnosed current head ea8dd05 with github-ci-diagnose.py: resolve_inputs timed out at 20 minutes; image-verification failed on that cancellation and verify builds were skipped. No uv-related failure is demonstrated. Existing local qualification remains recorded in the PR body.

The train's read-only controller pass is idle because this PR lacks ready-to-merge; gh-pr.py ready correctly refuses failed CI. Owner question on #112 requests one retry of the exact existing PR verification run, per AGENTS.md's rerun restriction. No direct rerun or enqueue label was applied. Controller trace: launchplane_req_21b2a9c2a9e94624b70879d3d8421bbe.

A separate public-base refresh is being validated under #121 for the downstream security blocker. Its source change remains separate from this uv-only PR. PyCharm inspection remains UNKNOWN; the exact worktree is not open and the brief forbids opening the desktop IDE.

[shiny-code-app]

Director question: Q314. May SWEEP-IMG retry this PR's cancelled verification run once?

• What it decides: one rerun of run 38459513122 ("Build And Publish Images"). It was cancelled on October 13 at about 4:01 PM ET, and its verification never finished. On a PR this workflow verifies the images; it doesn't publish them.
• Why it's yours: odoo-docker's AGENTS.md says "reruns go through the merge train or the agent asks Chris." The train can't select this PR because the ready handoff refuses a PR with a failed check.
• On yes: SWEEP-IMG reruns the run once. If it passes, it posts Ready and the PR goes to the train.
• Recommendation: yes. The run was cancelled rather than failing on the code. The base refresh in build(deps): refresh Ubuntu Noble runtime base #122 is running separately.

[shiny-code-app]

Director decision: Q314 = yes, recorded by the Supervisor. In the Supervisor's Claude Code session on October 14 at about 9:15 PM ET, Chris wrote: "Q314 yes". This answers Q314 and SWEEP-IMG's earlier request.

SWEEP-IMG had already closed, so the Supervisor reran run 38459513122 once. This is the single retry approved; any further rerun needs a new question.

[shiny-code-app]

Ready for the merge train

Head: ea8dd05

[shiny-code-app]

Launchplane completed the merge-train step for this pull request.

• Repository: cbusillo/odoo-docker
• Base branch: main
• Pull request: build(deps): update pinned uv image to 0.12.24 #120
• Controller action: land_batch
• Controller record: merge-train-batch-landing-plan-20261015T033436Z-17bc73160db81386

Launchplane finished the merge-train step for this pull request.

Launchplane manages this comment and will update it as the train moves.

[shiny-code-app]

Current Status

SWEEP-D1 verified Q314's single approved rerun: run 38459513122, attempt 2, completed success on unchanged head ea8dd05f0612a9fe6db2defdf8759d2d458a68ce. No further rerun was performed. All 12 current-head check runs are terminal and nonfailing, with no pending signals or unfinished workflows. Existing local image qualification remains recorded in the PR body.

The engineering-only Client notes now use the required colon/reason format. Checked Ready receipt is posted for this exact head. The read-only train pass reports only missing ready-to-merge label; Supervisor owns enqueueing and landing. Trace: launchplane_req_50616e320e9d41ae9f01c60fa812a8e3.

Inspection remains UNKNOWN from the existing qualification and retained lease follow-up; this metadata-only sweep did not open the desktop IDE, alter source or manufacture a clean inspection result. No publication dispatch, tag, deploy or manual merge. The #112 qualification finish line is met by successful exact-head verification plus checked Ready; all retained source worktrees and the original lease remain in Supervisor custody through PR disposition.

[shiny-code-app]

Current Status

SWEEP-D1 confirms #120 landed through the train at f98661003484a9277c3973d99da6d150e9f397f7 (fresh merged-PR readback). The train refreshed the source to a8a5b49cb0833b9144b7a3f4d0fdf8049944e3d0; all 12 checks on that head are terminal/nonfailing. The attempted fresh Ready correctly refused because the PR had already merged; no repeat handoff or merge was sent.

Q314's one approved rerun remains run38459513122 attempt2, success; this sweep made no additional rerun. Qualification issue #112 is closed with plan:done, and its exact SWEEP-D1 claim is released. No Client or production operation occurred.

Post-merge Push on main passed. Normal Build And Publish Images is still in progress at closeout; publication is not claimed complete. The local default checkout is clean but stale and preserved under the brief's primary-checkout boundary; fast-forward it through the supported route before default-branch work or audits. Original source checkout/IDE-lease custody remains with Supervisor; no foreign worktree was removed.