This repository was archived by the owner on Apr 21, 2026. It is now read-only.
docs: clarify who sets breeze:human (responder-elevated pattern)#13
Open
serenakeyitan wants to merge 1 commit intoagent-team-foundation:mainfrom
Open
docs: clarify who sets breeze:human (responder-elevated pattern)#13serenakeyitan wants to merge 1 commit intoagent-team-foundation:mainfrom
serenakeyitan wants to merge 1 commit intoagent-team-foundation:mainfrom
Conversation
DESIGN.md already specifies the four states (new / wip / human / done) but doesn't say who transitions wip → human. This matters because reviewers and agents may both think it's the other's job, leading to PRs that never escalate. Adds a subsection after the Four States table: - Signal comes from reviewer behavior (repeated CHANGES_REQUESTED etc.) - Action is taken by the agent that tracks attempts across rounds - Suggested threshold: 5 rounds Keeps breeze-runner and gardener-respond consistent. Closes agent-team-foundation#12 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
6 tasks
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
DESIGN.md already specifies the four states (new / wip / human / done) but doesn't say who transitions wip → human. This PR adds that rule.
The rule
Signal comes from reviewer behavior (repeated
CHANGES_REQUESTED, unclear feedback). Action is taken by the agent that tracks attempts across rounds.Why
While wiring this labeling system into repo-gardener (gardener-respond fixes sync PRs after reviewer feedback), I hit the question: after N unsuccessful rounds, who labels
breeze:human?Without this clarification, different agents (breeze-runner, gardener-respond, future agents) may implement different thresholds or each expect the other to do it → PRs never escalate.
Test plan
Closes #12
🤖 Generated with Claude Code