Say Which Merge-Bot Proofs Are Tracked Rather Than an Audit Report Recording Them

[ptr727]

Summary

• CodeRabbit found on promotion PR Promote develop to main: details Markup Pairing, Handoff Read Path, and STANDUP Deploy Sources #2411 that TODO.md and docs/reusable-workflows.md said "the hub's audit report on the pilot records" what the hub cannot prove about the merge-bot task. reports/photocleaner/audit.md records none of it. That wording came from Say the Hub Commits the Audit Report Wherever Done-Means-Audited Is Stated #2408.
• Of the four things the hub cannot prove, only two are tracked: the pin's cross-repository resolution and its first Dependabot bump, each a Stage 1 proof item. The rules input and merge-app have no tracker item, and PhotoCleaner, the pilot, can produce neither. Add Proof Items for the Merge-Bot rules Input and merge-app Job #2412 now tracks those two.
• Each statement now says which two are proof items and points at Add Proof Items for the Merge-Bot rules Input and merge-app Job #2412 for the rest. Stage 1's pilot sentence no longer gives the pilot a three-item list. "What a Pilot Proves" gives the four to downstream adopters rather than the first one.

Verification

• The prose gate on the diff, the eol gate, and markdownlint are clean. The two remaining --check sentence-length hits are sentences this change leaves unchanged.
• local-strict-review ran twice. The first pass found the first rewrite assigned the rules and merge-app proofs to a pilot that cannot produce them. The second pass found nothing, and its receipt is recorded at the pushed head.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Clarified which behaviors the merge-bot pilot does not verify and which downstream adopters need to validate, including cross-repository pin resolution, the first Dependabot bump, end-to-end rules use, and merge-app.
  • Updated the adoption notes and added a reference to issue #2412.

[Copilot]

Copilot review overview

🟢 Approval recommended

No unresolved review issues remain.

Review effort: Lite
Findings: None

What changed in this PR

Clarifies which merge-bot proofs are tracked and which require downstream follow-up.

Changes:

• Updates proof-tracking language in TODO.md.
• Corrects pilot and adopter guidance.
• Links untracked proofs to issue #2412.

File	Description
TODO.md	Identifies tracked and untracked proofs.
docs/​reusable-workflows.md	Clarifies pilot and downstream proof responsibilities.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

🧰 Additional context used

📚 Code guidelines (2)

CODESTYLE.md — auto-discovered
RESYNC.md — auto-discovered

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: ptr727/ProjectTemplate/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: e603c301-7590-4fe7-801b-fc6e666bc338

📥 Commits

Reviewing files that changed from the base of the PR and between 73c9031 and 0b37123.

📒 Files selected for processing (2)

• TODO.md
• docs/reusable-workflows.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The Merge-Bot adoption notes distinguish pilot proof items from behaviors downstream adopters must prove. The notes include merge-app and end-to-end rules behavior among the downstream proof items and link to issue #2412.

Changes

Merge-Bot adoption documentation

Layer / File(s)	Summary
Update Merge-Bot proof scope docs/reusable-workflows.md, TODO.md	The notes list cross-repository pin resolution and the first Dependabot bump as pilot proof items. They assign four behaviors, including end-to-end rules behavior and merge-app, to downstream adopters and reference issue #2412.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to 0b371

The proof responsibilities are consistent, and the follow-up link points to the relevant issue. No merge-blocking documentation risk remains.

Architecture Summary

Architecture risk: 🔵 Low · up to 0b371

The change affects 2 systems.

Changed systems: docs, TODO.md

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — docs (service) was modified; 1 changed file maps to changed impact.
• observed — TODO.md (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in TODO.md: The merge-bot detail now includes merge-app among the items the hub cannot prove and links the rules input and merge-app proof items to issue #2412.
• observed — Modified behavior in TODO.md: Added the issue #2412 reference used by the merge-bot detail.
• observed — Modified behavior in docs/reusable-workflows.md: The adoption description no longer lists rules support and the first Dependabot bump among the pilot’s proof items; it now identifies only cross-repository pin resolution and the first bump as proof items.
• observed — Modified behavior in docs/reusable-workflows.md: The text now says downstream adopters must prove cross-repository pin resolution, Dependabot pin bumps, end-to-end rules behavior, and merge-app; it removes the statement that the pilot audit recorded these as observed and adds a reference to issue #2412.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: clarifying which merge-bot proofs are tracked rather than claiming the pilot audit report recorded them.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 58.34%. Comparing base (73c9031) to head (0b37123).

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #2413   +/-   ##
========================================
  Coverage    58.34%   58.34%           
========================================
  Files           16       16           
  Lines         8036     8036           
========================================
  Hits          4689     4689           
  Misses        3347     3347           

Flag	Coverage Δ
python-3.13	58.34% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ptr727]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.