WIP: issue #439 checkpoint -- Event-driven "needs you" notification so the operator knows the moment he is the blocker #443
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!443
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/439-event-driven-needs-you-notification-so-the"
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?
Work-in-progress checkpoint. The agent hit its per-tick turn limit and snapshotted its progress here; it resumes automatically on the next tick. This PR is a draft (
WIP:) -- the review and merge loops leave it alone until it's finished.Closes #439
Closing. The issue this checkpointed from (#439) had its
Agentlabel removed so it could be worked directly, and the resume path depends on the grind re-claiming the issue -- so nothing was ever coming back for this. It was stranded, not paused.Starting #439 fresh rather than resuming: this snapshot was built against the over-scoped version of the ticket (the one that blocked at 792 lines against the 400 cap), so it is shaped around doing detection and delivery in one pass -- which is the split that needs to happen anyway.
Pull request closed