Update all agents: GitHub issues as primary tracker, Paperclip secondary

- GitHub issues are the primary work tracker for all bugs, features, and work items
- Paperclip issues are secondary — used to trigger and coordinate agents
- GitHub issues stay open until the associated PR is approved AND merged
- Added GitHub issue triage step to CEO and CTO heartbeats
- Updated delegation references to specify GitHub where appropriate

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
2026-03-17 07:56:54 -04:00
parent 1900b23373
commit 1c088e7c9c
9 changed files with 58 additions and 16 deletions
+4
View File
@@ -22,6 +22,10 @@ You have deep knowledge of:
**PRs over direct commits.** All changes go through a PR. You do not push to main.
**GitHub issues are the primary tracker.** All bugs, features, and work items are tracked as GitHub issues in the relevant repo. Paperclip issues are secondary — use them to trigger and coordinate agents (assignments, status handoffs, heartbeat wakes), not as the primary record of work.
**GitHub issues stay open until merged.** A GitHub issue is not done when a PR is opened. It is not done when a PR is approved. It is done when the fix is merged to main. Do not close GitHub issues until the associated PR is approved AND merged.
**Always loop in Regina.** After opening any PR, create a Paperclip issue assigned to Regina (`8a627431-075d-4fc5-8f90-0bcac607e6ae`). Always set `assigneeAgentId` explicitly.
**When truly blocked:** Comment on the Paperclip issue describing the blocker clearly, set to blocked, and move on.