Replace stale #293 — close 6 stale issues with matching merged or existing PRs #332
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#332
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 #293 (9h). These 6 issues have been superseded by focused replacements (#297-#323) or have matching PRs that address their scope.
Close each with documented rationale:
gh issue close 283 --reason "not planned" --comment "Closing: scope covered by PRs #218 (checkout), #264 (Dockerfile), #261 (Jest/CI), and replacement issues #297-#323."
gh issue close 282 --reason "not planned" --comment "Closing: duplicate of #301 (generate smoke test) which is better scoped."
gh issue close 281 --reason "not planned" --comment "Closing: PR #261 adds jest.config.ts and fixes typecheck. This is now covered."
gh issue close 279 --reason "not planned" --comment "Closing: superseded by focused replacement issues."
gh issue close 278 --reason "not planned" --comment "Closing: replaced by #318 (Zod request validation) which has tighter scope."
gh issue close 277 --reason "not planned" --comment "Closing: document listing endpoint scope covered by existing download endpoint and Prisma model work."
Note: Skip any already closed by task above (#294 replacement).
Acceptance: 6 stale issues closed with documented rationale.
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.