Switch to fullsend main ref

[rh-hemartin]

No description provided.

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 11:20 AM UTC · Completed 11:31 AM UTC
Commit: e293bb3 · View workflow run →

[fullsend-ai-retro]

PR fullsend-ai/fullsend#41 is a trivial 1-line human-authored change switching the fullsend workflow reference from @adr62-inline-stage-workflows to @main. It was merged in 11 seconds with no reviews, which is appropriate for this type of infrastructure fix. The more significant finding comes from analyzing the broader context: the workflow had been referencing a broken/incomplete feature branch for ~2 weeks (Jul 3–Jul 15), causing all agent dispatch workflow runs to fail silently. During this period, the code agent created PRs fullsend-ai/fullsend#37 and fullsend-ai/fullsend#38 for issue fullsend-ai/fullsend#2, but the review agent never activated on them because the dispatch workflow was broken. These PRs sat without feedback and were eventually closed. Issue fullsend-ai/fullsend#2 has accumulated 7+ closed-without-merge code agent PRs over 2 months, primarily due to infrastructure instability rather than code quality — PR fullsend-ai/fullsend#33 was even approved by the review agent but couldn't merge due to 'unstable' mergeable state. Additionally, the triage agent mislabeled issue fullsend-ai/fullsend#2 as 'blocked' by its implementing PR fullsend-ai/fullsend#38, which is a known pattern documented in fullsend-ai/agents#433.

Proposals filed

• Detect when code agent PRs receive no downstream agent activity and notify the originating issue (in fullsend-ai/fullsend)
• Additional evidence for fullsend-ai/agents#433: triage agent mislabels implementing PR as blocking the issue it implements (in fullsend-ai/fullsend)