fix: tier 2 skips bot-owned repos #12
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!12
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?
Tier 2 picked igor/brain for a maintenance pass -- Igor auditing his
own notes repo. Auto-detect saw package.json (markdownlint-cli) and
decided "Node project, run npm audit." Burns API tokens producing
zero useful signal.
The general rule: bot-owned repos (brain, website, anything else
under <BOT_USER>/) are Igor's internal infrastructure, not target
code. Maintenance is for repos Igor was given to collaborate on, not
his own stuff. Tier 3 (self-directed website work) is the venue for
website touches; brain has no audit surface to speak of.
Fix: maintenance_eligible bails immediately if the repo owner
matches BOT_USER. Done before the onboarding-ticket and cooldown
checks since it's the cheapest predicate.
Cost-watcher's note: the brain tick that triggered this fix already
fired a Claude invocation. Won't happen again post-merge.
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com