joshtronic/igor
joshtronic/igor
Watch
2
Code Issues 3 Pull requests 2 Activity Actions

feat: maintenance findings get severity-derived Priority/* label #11

Merged
joshtronic merged 1 commit from devel into master 2026-05-16 22:21:55 +00:00
Conversation 0 Commits 1 Files changed 2 +32
joshtronic commented 2026-05-16 22:21:09 +00:00
Owner
Copy link

Tier 2's "Status/Needs More Info"-labeled findings issues now also
get a Priority/* label derived from Claude's own severity assessment
of what he found. The human's attention follows severity rather than
treating all maintenance findings as equal-priority.

Claude writes a single-word severity to .igor/IGOR_MAINTENANCE_PRIORITY
(one of: critical, high, medium, low). The harness reads it, maps
to the corresponding Priority/* label, applies it alongside
Status/Needs More Info.

AGENTS.md gains the contract + guidelines for each level:
critical -- actively-exploited, stop-other-work
high -- unfixed CVEs, security patches available
medium -- outdated-but-functional, low-severity
low -- nice-to-have, nothing security-relevant

If the priority file is missing or unparseable, no Priority/* label
is applied -- just Status/Needs More Info. Won't crash the tick.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

Tier 2's "Status/Needs More Info"-labeled findings issues now also get a Priority/* label derived from Claude's own severity assessment of what he found. The human's attention follows severity rather than treating all maintenance findings as equal-priority. Claude writes a single-word severity to .igor/IGOR_MAINTENANCE_PRIORITY (one of: critical, high, medium, low). The harness reads it, maps to the corresponding Priority/* label, applies it alongside Status/Needs More Info. AGENTS.md gains the contract + guidelines for each level: critical -- actively-exploited, stop-other-work high -- unfixed CVEs, security patches available medium -- outdated-but-functional, low-severity low -- nice-to-have, nothing security-relevant If the priority file is missing or unparseable, no Priority/* label is applied -- just Status/Needs More Info. Won't crash the tick. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
feat: maintenance findings get severity-derived Priority/* label
All checks were successful
Lint / check-sync (push) Successful in 4s
Details
Lint / check-sync (pull_request) Successful in 4s
Details
5abbce1f61
 
Tier 2's "Status/Needs More Info"-labeled findings issues now also
get a Priority/* label derived from Claude's own severity assessment
of what he found. The human's attention follows severity rather than
treating all maintenance findings as equal-priority.

Claude writes a single-word severity to .igor/IGOR_MAINTENANCE_PRIORITY
(one of: critical, high, medium, low). The harness reads it, maps
to the corresponding Priority/* label, applies it alongside
Status/Needs More Info.

AGENTS.md gains the contract + guidelines for each level:
  critical -- actively-exploited, stop-other-work
  high     -- unfixed CVEs, security patches available
  medium   -- outdated-but-functional, low-severity
  low      -- nice-to-have, nothing security-relevant

If the priority file is missing or unparseable, no Priority/* label
is applied -- just Status/Needs More Info. Won't crash the tick.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
joshtronic scheduled this pull request to auto merge when all checks succeed 2026-05-16 22:21:48 +00:00
joshtronic deleted branch devel 2026-05-16 22:21:55 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
Agent

   
Compat/Breaking
Breaking change that won't be backward compatible

  
Kind/Bug
Something is not working

  
Kind/Documentation
Documentation changes

  
Kind/Enhancement
Improve existing functionality

  
Kind/Feature
New functionality

  
Kind/Security
This is security issue

  
Kind/Testing
Issue or pull request related to testing

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Reviewed
Confirmed
 Issue has been confirmed

  
Reviewed
Duplicate
 This issue or pull request already exists

  
Reviewed
Invalid
 Invalid issue

  
Reviewed
Won't Fix
 This issue won't be fixed

  
Status
Abandoned
 Somebody has started to work on this but abandoned work

  
Status
Blocked
 Something is blocking this issue or pull request

  
Status
Need More Info
 Feedback is required to reproduce issue or to continue work

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
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
joshtronic/igor!11
No description provided.