feat(deps): preserve agent repairs through promoted dependency PRs

[stranske]

Workflow Source

Started from:

• GitHub issue: #
• Direct PR / remote GitHub work
• Local Codex/user request
• Automation run
• Review follow-up from PR chore(deps): update actions/setup-python action to v7 #2795
• Sync / maintenance campaign
• Dependabot or dependency update
• Do not automate

Automation intent:

• Verifier should review this
• Keepalive may manage this PR
• Human-only unless checks fail

Notes:
Implements the dependency-repair ownership model prompted by the mixed-provenance history on #2795. The already-open bounded salvage PR #2851 remains separate.

Summary

• Keeps clean Renovate/Dependabot PRs bot-owned while allowing strict generated lockfile maintenance.
• Adds a machine-enforced promotion contract: an agent-owned agent/deps-repair-* PR must reproduce the selected bot delta in its first commit; later commits remain available to local coding agents for the actual repair.
• Documents and automates the companion-PR lane for dependency-independent fixes, the promotion lane for coupled fixes, the Workflows-first lane for shared templates, and the narrow owner-decision boundary.
• Syncs the thin PR check and label documentation to consumers.
• Updates the recurring sync/dependency campaign instructions so future runs classify and preserve useful non-bot work before closing a bot PR.

Costs and benefits

The cost is one extra PR for a coupled repair plus a provenance check. The benefit is that bot deltas, generated maintenance, and coding-agent repairs are reviewable as distinct work. This does not disable local agents: later promotion commits are deliberately unrestricted by this provenance check and continue through normal CI/review controls.

Testing

• node --check .github/scripts/dependency-repair-contract.js
• node --test .github/scripts/__tests__/dependency-repair-contract.test.js (5 passed)
• focused workflow/template + docs pytest sets (53 passed total)
• python scripts/validate_workflow_yaml.py ... (3 workflow files valid)
• actionlint on the three workflow files
• python scripts/check_api_wrapper_guard.py --base-ref main
• python scripts/validate_template_completeness.py --source sync-manifest
• python scripts/validate_template_sync.py
• git diff --check

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 32 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 180197da-f9c0-4843-ae83-5ae74423d6b8

📥 Commits

Reviewing files that changed from the base of the PR and between fa2253e and 026a6b2.

📒 Files selected for processing (15)

• .github/labels-core.yml
• .github/scripts/__tests__/dependency-repair-contract.test.js
• .github/scripts/dependency-repair-contract.js
• .github/sync-manifest.yml
• .github/workflows/pr-46-dependency-repair-contract.yml
• .github/workflows/reusable-19-dependency-repair-contract.yml
• docs/LABELS.md
• docs/WORKFLOW_GUIDE.md
• docs/ci/WORKFLOWS.md
• docs/ci/WORKFLOW_OUTPUTS.md
• docs/ci/WORKFLOW_SYSTEM.md
• docs/ops/DEPENDENCY_REPAIR_PROMOTION.md
• templates/consumer-repo/.github/workflows/pr-46-dependency-repair-contract.yml
• templates/consumer-repo/docs/LABELS.md
• tests/workflows/test_workflow_naming.py

---

_{Comment @coderabbitai help to get the list of available commands.}

[stranske-keepalive]

Workflow source needed

PR #2853 needs either a linked GitHub issue or one valid non-issue Workflow Source before PR metadata automation can manage it safely.

Please do one of:

• Add <!-- meta:issue:123 --> or a normal Closes #123 / Related to #123 line.
• Check one Workflow Source option in the PR body.
• Add a hidden marker such as <!-- workflow-source:local_request -->, <!-- workflow-source:manual_remote -->, <!-- workflow-source:review_followup -->, <!-- workflow-source:sync_campaign -->, or <!-- workflow-source:dependabot -->.
• Add a workflow source label such as workflow:source-direct-pr, workflow:source-local-request, workflow:source-review-followup, workflow:source-sync, or workflow:no-automation.

Once a valid source is present, this warning will not be reposted.

[stranske-keepalive]

Automated Status Summary

Head SHA: e2718d2
Latest Runs: ⏳ pending — Gate
Required contexts: Gate / gate, Health 45 Agents Guard / guard
Required: core tests (3.12): ⏳ pending, core tests (3.13): ⏳ pending, docker smoke: ⏳ pending, gate: ⏳ pending

Workflow / Job	Result	Logs
(no jobs reported)	⏳ pending	—

Coverage Overview

• Coverage history entries: 1

Coverage Trend

Metric	Value
Current	75.90%
Baseline	85.00%
Delta	-9.10%
Minimum	70.00%
Status	✅ Pass

Top Coverage Hotspots (lowest coverage)

File	Coverage	Missing
scripts/issue_dedup_smoke.py	0.0%	4
scripts/runner_lib/__main__.py	0.0%	3
scripts/validate_template_sync.py	0.0%	81
scripts/langchain/topic_splitter.py	19.1%	57
tools/codex_log_analyzer.py	19.6%	140
scripts/repo_review_round2_runner.py	25.1%	344
scripts/prune_agent_stubs.py	39.7%	26
scripts/repo_review_round1_runner.py	40.7%	133
tools/ensure_workflow_timeout_variables.py	42.1%	74
scripts/sync_label_docs.py	42.9%	64
tools/discover_model_catalog.py	44.8%	55
scripts/repo_review_backlog_scan.py	45.3%	116
scripts/repo_review_body_writer.py	46.5%	86
tools/codex_session_analyzer.py	47.9%	59
scripts/create_verifier_labels.py	48.3%	58

Low Coverage Files (<50.0%)

File	Coverage	Missing
scripts/issue_dedup_smoke.py	0.0%	4
scripts/runner_lib/__main__.py	0.0%	3
scripts/validate_template_sync.py	0.0%	81
scripts/langchain/topic_splitter.py	19.1%	57
tools/codex_log_analyzer.py	19.6%	140
scripts/repo_review_round2_runner.py	25.1%	344
scripts/prune_agent_stubs.py	39.7%	26
scripts/repo_review_round1_runner.py	40.7%	133
tools/ensure_workflow_timeout_variables.py	42.1%	74
scripts/sync_label_docs.py	42.9%	64
tools/discover_model_catalog.py	44.8%	55
scripts/repo_review_backlog_scan.py	45.3%	116
scripts/repo_review_body_writer.py	46.5%	86
tools/codex_session_analyzer.py	47.9%	59
scripts/create_verifier_labels.py	48.3%	58

Updated automatically; will refresh on subsequent CI/Docker completions.

---

Keepalive checklist

Scope

No scope information available

Tasks

• No tasks defined

Acceptance criteria

• No acceptance criteria defined

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 026a6b2c55

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".