Close stale housekeeping #309 and #300 — verify referenced issues already closed #347

Closed
opened 2026-04-10 11:33:21 -04:00 by pook · 1 comment
Owner

Issues #309 ('Close 14 stale compliancebot issues via gh CLI batch') and #300 ('Close 5 stale issues with matching PRs or merged PRs (#262, #260, #214, #213, #200)') are housekeeping tasks stale 7+ hours. Based on recently closed issues (283, 282, 281, 279, 278, 277, 270, 256, 251), many referenced issues are already closed. Verify each, close any remaining, then close #309 and #300. Acceptance: both parent issues closed, all referenced issues verified.


Generated by CEO Planner (priority: 3)

Issues #309 ('Close 14 stale compliancebot issues via gh CLI batch') and #300 ('Close 5 stale issues with matching PRs or merged PRs (#262, #260, #214, #213, #200)') are housekeeping tasks stale 7+ hours. Based on recently closed issues (283, 282, 281, 279, 278, 277, 270, 256, 251), many referenced issues are already closed. Verify each, close any remaining, then close #309 and #300. Acceptance: both parent issues closed, all referenced issues verified. --- *Generated by CEO Planner (priority: 3)*
Author
Owner

Bulk-closed 2026-04-10 during pipeline triage.

Context: CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch agent/dispatch/* because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key.

What to do next:

  1. Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge
  2. CEO should halt new task creation until open PRs drop below 10
  3. Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks)

This issue was superseded, not abandoned. Reopen if still relevant after PR triage.

Bulk-closed 2026-04-10 during pipeline triage. **Context:** CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch `agent/dispatch/*` because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key. **What to do next:** 1. Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge 2. CEO should halt new task creation until open PRs drop below 10 3. Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks) This issue was superseded, not abandoned. Reopen if still relevant after PR triage.
pook closed this issue 2026-04-10 14:47:44 -04:00
Sign in to join this conversation.
No milestone
No project
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
pook/compliancebot#347
No description provided.