fix(taskctl): reduce developer-adversarial cycle waste from workflow errors#320
Merged
fix(taskctl): reduce developer-adversarial cycle waste from workflow errors#320
Conversation
added 4 commits
February 23, 2026 15:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses 4 categories of waste in the developer-adversarial pipeline loop:\n\n- Worktree context: Developer prompt now includes explicit worktree path and branch with mandatory git branch verification before any file operation\n- Empty diff guard: spawnAdversarial checks for empty diff before spawning — if no commits found, adds system comment and respawns developer instead of wasting an adversarial cycle\n- Skill guidance: developer-pipeline.txt now explicitly names bun-file-io as the correct skill and forbids non-TypeScript skills\n- Adversarial scope: adversarial-pipeline.txt adds WORKFLOW_ERROR verdict category for process failures, and clarifies that rebase-artifact commits should be ignored\n\nFixes #315