Phase 2: phase-pr describes itself #481
No reviewers
Labels
No labels
agent-ready
bug
contract
documentation
duplicate
enhancement
good first issue
help wanted
invalid
needs-human
needs-input
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
iterative-works/iw-cli!481
Loading…
Reference in a new issue
No description provided.
Delete branch "IW-463-phase-02"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Phase 02 implementation for IW-463.
Files
Browse changed files: https://code.iterative.works/iterative-works/iw-cli/-/blob/IW-463-phase-02/
Rescued from a commit the batch run left unreachable. The entry diagnoses why phase 2's gate never converged: each exit-3 resume commits and pushes a review-state update, which cancels the CI run it is waiting for. 🤖 Generated with Claude CodeA wait that uses up its whole budget leaves through exit 1, but every poll that reached that point had read Running, so nothing failed. Exit 1 named only red CI, an unreadable forge and a bad argument, and told the caller to fix it and run again — which times out again on the same budget. Found by re-running the agent-legibility gate with an isolated agent, which answered both required questions correctly and then reported that the help never says what happens when the budget runs out. - exit 1 names the spent budget and says to raise --timeout - CommandDeclarationTest gains a content rule over the subject list, so phase-merge and ci-gate are covered when they declare in phase 4 - PhasePrHarnessTest pins the in-loop routing, which no test covered; the existing budget test exercises only the pre-poll path - Builder.register refuses a duplicate flag name, which otherwise loses the caller's value silently - CommandHelpTest guards the blank line before every section header 🤖 Generated with Claude Code