fix: working on a few overruns #10
No reviewers
Labels
No labels
Agent
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
joshtronic/igor!10
Loading…
Reference in a new issue
No description provided.
Delete branch "devel"
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?
Observed in dogfood: tier 2 filed findings issue with Agent label, which made tier 1 immediately claim and work it. Igor effectively employed himself with no human in the decision loop. Surprise that broke the user's mental model of "Igor reports, human triages." Fix: tier 2 applies Status/Needs More Info to findings issues, not Agent. Same gate pattern as onboarding tickets. Human reads the findings, decides: - Worth fixing -> remove Status/Needs More Info, add Agent -> next tick claims it as normal tier-1 work - Not worth -> close - Mix -> split into per-finding tickets, label as desired Tier 1 -> tier 2 (file report) -> human triage -> tier 1 (work specific items). Symmetric with the onboarding flow, predictable, keeps the human in the decision. AGENTS.md updated to spell out the new contract to Claude. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>