Skip to content

fix(#4060): reduce sub-agent dispatch for mechanical dep bumps - #4061

Closed
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/4060-reduce-dispatch-dep-bumps
Closed

fix(#4060): reduce sub-agent dispatch for mechanical dep bumps#4061
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/4060-reduce-dispatch-dep-bumps

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

Add a dispatch examples table row for dependency version bumps (lockfile + manifest only) that dispatches only the always-included sub-agents (correctness + style-conventions).

Add a cross-reference from section 3c (dispatch) to section 3e (scope constraints) so that when triage classifies a change as "mechanical/value-only", the orchestrator suppresses conditional triggers (security, intent-coherence, docs-currency, cross-repo-contracts) and dispatches only the always-included sub-agents.


Closes #4060

Post-script verification

  • Branch is not main/master (agent/4060-reduce-dispatch-dep-bumps)
  • Secret scan passed (gitleaks — 4cb864299807fde398b226a0f21819d942fb9415..HEAD)
  • Pre-commit hooks passed (authoritative run on runner)
  • Tests ran inside sandbox

Add a dispatch examples table row for dependency version bumps
(lockfile + manifest only) that dispatches only the always-included
sub-agents (correctness + style-conventions).

Add a cross-reference from section 3c (dispatch) to section 3e
(scope constraints) so that when triage classifies a change as
"mechanical/value-only", the orchestrator suppresses conditional
triggers (security, intent-coherence, docs-currency,
cross-repo-contracts) and dispatches only the always-included
sub-agents.

Closes #4060
@fullsend-ai-coder
fullsend-ai-coder Bot requested a review from a team as a code owner July 10, 2026 15:44
@fullsend-ai-coder fullsend-ai-coder Bot added the ready-for-review Triggers review agent dispatch label Jul 10, 2026
@codecov

codecov Bot commented Jul 10, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@ralphbean

Copy link
Copy Markdown
Member

/fs-fix no, coupling review and triage this way is an architectural violation. The review agent should never suppress security analysis (or do anything really) because of something that it appears the triage agent decided. That's a recipe for future cascading attack vectors. This could be revised to provide the same logic on different conditions: look at the files changed, or by a cursory scan of the diff - if it appears to really be a mechanical change, then perhaps. If in question, err on the safe side and launch deeper review.

@ralphbean

Copy link
Copy Markdown
Member

Oh, and, in any case - we don't want to accept new changes to internal/scaffold/fullsend-repo/ agent definitions in this repo. We have moved them to the fullsend-ai/agents repo.

Closing this.

@ralphbean ralphbean closed this Jul 10, 2026
@fullsend-ai-coder

fullsend-ai-coder Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Finished Fix · ✅ Success · Started 7:09 PM UTC · Completed 7:17 PM UTC
Commit: b8a817e · View workflow run →

@fullsend-ai-retro

fullsend-ai-retro Bot commented Jul 10, 2026

Copy link
Copy Markdown

🤖 Finished Retro · ✅ Success · Started 7:11 PM UTC · Completed 7:21 PM UTC
Commit: 16201c8 · View workflow run →

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor Author

🔧 Fix agent — iteration 1 (human-triggered)

Addressed 1 human review finding: decoupled mechanical-change dispatch reduction from triage-agent classification. The review orchestrator now makes its own independent assessment based on file list and diff inspection, with a conservative default (full dispatch including security when uncertain).

Fixed (1):

  1. triage-coupled dispatch is an architectural violation (internal/scaffold/fullsend-repo/skills/pr-review/SKILL.md): Replaced the 'Mechanical/value-only override' paragraph in section 3c that coupled dispatch decisions to triage-agent classification. The new text has the review orchestrator perform its own lightweight mechanical-change assessment by inspecting the changed file list and diff. A three-condition test determines mechanicality: (1) all changed files are lockfiles/manifests/digests, (2) diff contains only value substitutions, (3) no security-sensitive files touched. When uncertain, the orchestrator errs on the safe side and dispatches the full agent roster including security. The text explicitly states that the assessment must not be derived from triage-agent classification.

Tests: passed

Updated by fullsend fix agent

fullsend-ai-coder Bot added a commit that referenced this pull request Jul 10, 2026
Replace triage-coupled dispatch override in section 3c with independent
mechanical-change assessment. The review orchestrator now inspects the
changed file list and diff directly, rather than relying on triage-agent
classification, to determine if a change is purely mechanical.

Key changes:
- Remove reference to triage classification from dispatch logic
- Add explicit three-condition test for mechanical changes
- Require conservative dispatch (including security) when uncertain
- Preserve dispatch reduction as an option only when all conditions hold

Addresses review feedback on #4061
@fullsend-ai-retro

Copy link
Copy Markdown

PR #4061 was a code-agent PR that modified internal/scaffold/fullsend-repo/skills/pr-review/SKILL.md to reduce sub-agent dispatch for mechanical dependency bumps. It was closed without merge after human review (ralphbean) identified two fundamental issues: (1) the proposed change couples the review agent's dispatch to the triage agent's classification — an architectural violation that could suppress security review based on external classification, and (2) the change targets stale scaffold files in fullsend-ai/fullsend instead of the canonical copies in fullsend-ai/agents.

This is the 4th documented occurrence of agents editing scaffold files that have migrated to fullsend-ai/agents (following PRs #2927, #2417, and #3156). Issue #3157 proposes adding AGENTS.md guidance and deprecation markers to prevent this, but remains open. Each recurrence wastes a full retro→triage→code→human-review cycle. Additionally, the review agent never ran on this PR (known issue #3996), so the entire quality check fell to the human reviewer.

The underlying retro observation (dep bumps dispatch too many sub-agents) is valid. The human's /fs-fix feedback redirected toward a better approach: the review agent should independently assess mechanicality from the diff rather than depending on triage classification. A fix agent was dispatched with this corrective guidance. One new proposal is filed below; the wrong-repo targeting is already covered by #3157.

Proposals filed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-review Triggers review agent dispatch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

pr-review skill: reduce sub-agent dispatch for mechanical/value-only changes like dependency bumps

1 participant