chore(deps): update pre-commit hook renovatebot/pre-commit-hooks to v44.54.0

[hermes-renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
renovatebot/pre-commit-hooks	repository	minor	44.52.1 → 44.54.0	44.82.0 (+77)

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.

---

Release Notes

renovatebot/pre-commit-hooks (renovatebot/pre-commit-hooks)

v44.54.0

Compare Source

See https://github.com/renovatebot/renovate/releases/tag/44.54.0 for more changes

v44.53.0

Compare Source

See https://github.com/renovatebot/renovate/releases/tag/44.53.0 for more changes

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 66e38e37-c8f1-45ec-96d9-6146c0b48f33

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

[fullsend-ai-retro]

PR #99 (redhat-et/ProtoBot) is a Renovate dependency-bump PR (chore(deps): update pre-commit hook renovatebot/pre-commit-hooks to v44.54.0), not an agent-authored change. Its branch never matched the agent/{issue}-{slug} pattern, so the fullsend triage/code/review/fix stages all correctly reported skipped on both dispatch runs. A human (JohnStrunk) approved and merged it after CI passed once (no flakiness observed, single run). No rework, no iterations, nothing for review-quality/rework-rate/token-cost/time-to-resolution analysis to act on for this PR itself.

The one substantive finding is that the retro stage still ran a full agent session against this zero-agent-involvement PR — wasted token cost. This is not a new problem: it's already tracked upstream in fullsend-ai/fullsend by issue #7197 ("Skip retro dispatch when no agent stages ran on the PR", opened 2026-09-10), which describes the identical failure mode on a Dependabot PR, and by #6297 ("Extend retro skip logic to merged PRs with zero fullsend agent involvement", opened 2026-08-17) which covers the merged-PR variant matching PR #99 exactly. PR #99 is additional corroborating evidence for both: a Renovate (not Dependabot) bot PR, merged, with zero agent stages run, where retro still dispatched.

Notably, fullsend-ai/fullsend#5817 is a meta-issue noting this exact class of proposal has already been filed 22+ times and asking for consolidation rather than more individual issues. In line with that and this project's own duplicate-checking requirement, no new proposal is filed here — filing one would add to the pile #5817 is complaining about. Agents repo discovered from ProtoBot's .fullsend/config.yaml allowlist: fullsend-ai/agents (harness/CLI comes from fullsend-ai/fullsend); redhat-et/.fullsend does not exist as a separate dispatch repo — config is inline in ProtoBot.

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 2:57 PM UTC · Completed 3:04 PM UTC

Commit: dd471a5 · View workflow run →

Runtime: claude · Model: sonnet → claude-sonnet-5 · Effort: high · Cost: $0.88