[shiny-code-app]

Renovate commits currently omit the update metadata Launchplane needs to admit safe dependency changes without a label. The shared preset now emits one JSON commit trailer containing every grouped update's type, versions, branch values and digests. Renovate automerge remains disabled; the train keeps merge authority.

Implements the shared-config slice of cbusillo/launchplane#4889 (Q876). That issue stays open for Launchplane deployment and the two waiting Renovate PRs landing.

Validation: Renovate 44.181.5 config validator passed. The installed Renovate renderer produced grouped digest/minor evidence accepted by the Launchplane classifier. Ruff lint and format passed. Consumer-build checks and CI are recorded below before Ready. Independent review: Anthropic claude-opus-5-5[1m]; the concern about a missing grouped context was refuted by Renovate's branch-worker source and the actual renderer output. Inspection not run under the temporary Director decision: https://github.com/cbusillo/direction/issues/98#issuecomment-6399734189.

Removed: the need to infer Renovate update safety from a PR title or editable body.
Net lines: +7 (one config field and documentation; no new updater or merge path).

Client test notes

Nothing for the Client to test: this adds dependency metadata for the merge train and changes no application or runtime behavior.

[shiny-code-app]

Review result: weighed
Head: 28e6a5e

Anthropic claude-opus-5-5[1m] reviewed this companion preset with Launchplane's consumer. No defect remains in the preset. The grouped-context hypothesis was refuted by the actual Renovate branch-worker source and renderer; grouped digest/minor JSON was consumed successfully. No automerge was enabled. No literal/config text assertion was added.

[shiny-code-app]

Engineering ready; waiting for the CM consumer-build gate replacement

Preset validation, actual Renovate template rendering, Ruff and independent Anthropic review passed. OPW and CM Website consumer builds are running at exact head 28e6a5e. CM's required build-tool-drift.yml dispatch was rejected: Validation failed: Workflow does not have 'workflow_dispatch' trigger. A fresh contents read confirms the file is absent on CM main. Its replacement Build workflow has no manual devkit-commit input. The devkit instruction still requires this proof before Ready. This PR remains held until the supported gate is restored or its replacement is recorded; no missing build is reported passed.

[shiny-code-app]

Consumer builds passed for exact devkit head 28e6a5e:

• OPW: https://github.com/cbusillo/odoo-tenant-opw/actions/runs/40230199447, attempt 1. Downloaded consumer-build-check-1 records runtime_commit matching the candidate, source_commit 994c12fe47302520428f4efd6561b5c78a41e4fb, linux/amd64 and dependency provenance.
• CM Website: https://github.com/cbusillo/odoo-tenant-cm-website/actions/runs/40230199663, attempt 1. Artifact records the same runtime_commit, source_commit d922f8f6a4bdd714db431f4830dbf9151b1d6345, linux/amd64 and dependency provenance.

CM's required route remains unavailable. Canonical repair: #274. This is the remaining preset Ready blocker; no plain Ready is posted before it is resolved. A devkit agent owns the next action on that issue.

[shiny-code-app]

Consumer-gate correction from DEVKIT274-1026 (#274): the CM operations hold in comments6402713421 and6402807537 was based on an incorrect scope interpretation. The approved dispatch record names OPW and CM website only; the current devkit guide delegates scope there. Both live workflows retain their exact-candidate check. No additional operations workflow is required.

I re-read both successful consumer-build jobs and downloaded both consumer-build-check-1 JSON artifacts. OPW40230199447 and website40230199663, attempt1, bind runtime_commit 28e6a5e to tenant commits 994c12fe47302520428f4efd6561b5c78a41e4fb and d922f8f6a4bdd714db431f4830dbf9151b1d6345 respectively, with linux/amd64 and matching dependency-evidence coverage. The current head is unchanged and all five checks are successful with zero unfinished workflows.

#274 is being closed with the scope/proof evidence. Next actor: this PR's existing owner or receiving train session runs the normal gh-pr.py ready 273 handoff for this head; the mistaken third-consumer hold no longer applies. Existing review comment6402712716 remains the weighed review. This correction is not a new Ready marker or a takeover of source/landing custody.