chore(deps): bump astral-sh/setup-uv from d0d8abe699bfb85fec6de9f7adb5ae17292296ff to d0cc045d04ccac9d8b7881df0226f9e82c39688e

[dependabot]

Bumps astral-sh/setup-uv from d0d8abe699bfb85fec6de9f7adb5ae17292296ff to d0cc045d04ccac9d8b7881df0226f9e82c39688e.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 8:51 AM UTC · Completed 8:59 AM UTC
Commit: 27b4123 · View workflow run →

[fullsend-ai-retro]

Retro: PR #25 — Dependabot hash-pin bump (astral-sh/setup-uv)

What happened: Dependabot opened a trivial 1-file, 2-line hash-pin update to .github/workflows/ci.yaml. No review agent was dispatched because dependabot[bot] fails the collaborator permission check in the routing logic (is_event_actor_authorized returns false for GitHub App bot accounts with no explicit collaborator role). A human (csoceanu) approved with no comments ~15 minutes later and merged immediately. The retro agent was dispatched post-merge despite zero agent interaction on the PR.

Workflow quality: Low-value run. The retro agent consumed tokens analyzing a PR with zero agent interaction, no review findings, and a bare human approval. There was nothing meaningful to retrospect on.

No new proposals filed — existing issues already cover both improvement areas:

• Skip review and retro stages for bot-authored dependency update PRs fullsend-ai/fullsend#5360 ("Skip review and retro stages for bot-authored dependency update PRs"): This umbrella issue directly covers both gaps observed here. This PR adds another data point — a retro agent run dispatched on a 2-line Dependabot hash-pin bump with zero prior agent involvement.
• Skip retro dispatch for bot-authored PRs with zero agent involvement fullsend-ai/fullsend#5295 ("Skip retro dispatch for bot-authored PRs with zero agent involvement"): Directly covers the wasted retro run. This PR is a clean example: no review, no code, no triage agent ran, yet retro was dispatched.
• Review agent skipped on bot-authored PRs due to collaborator permission check failing for GitHub App accounts fullsend-ai/fullsend#5188 ("Review agent skipped on bot-authored PRs due to collaborator permission check failing for GitHub App accounts"): Covers the exact authorization mechanism that prevented the review agent from running. The routing log confirms dependabot[bot] returns role_name: "" from the collaborator API.
• Skip retro dispatch on PRs with no agent involvement fullsend-ai/fullsend#939 ("Skip retro dispatch on PRs with no agent involvement"): The oldest open issue covering this pattern, now with 15+ related issues filed across subsequent retro runs.

Contrast with PR #23: The retro on PR #23 (a 34-file infrastructure bootstrapping PR) ran at the same time and produced high-value output — it found a concrete jq formula bug, linked evidence to 4 existing issues, and quantified ~$40 in review cost. This demonstrates the retro agent's value on substantive PRs while highlighting the waste on trivial bot PRs.