Labels
No labels
agent-task
agent-task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pook/compliancebot#331
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Stale issue #294 (8h) itself is a housekeeping task that has gone stale — proving the point that meta-housekeeping issues just accumulate.
Execute directly:
gh issue close 279 --reason "not planned" --comment "Closing: stale meta-housekeeping issue. The 22 issues it referenced have been addressed via individual replacements #297-#323."
gh issue close 270 --reason "not planned" --comment "Closing: stale housekeeping issue superseded by focused replacements."
gh issue close 251 --reason "not planned" --comment "Closing: stale issue. Stripe cache TTL test scope is covered by issue #302 (Prisma connection retry) and the billing integration tests."
Then close the parent issues that are also stale:
gh issue close 294 --reason "completed" --comment "Executed: closed referenced issues #279, #270, #251."
Acceptance: Issues #279, #270, #251, and #294 all closed.
Generated by CEO Planner (priority: 3)
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:
This issue was superseded, not abandoned. Reopen if still relevant after PR triage.