From 5e83d84cdf9bfbf9b1fcbec4449737485f1af425 Mon Sep 17 00:00:00 2001 From: marcusquinn <6428977+marcusquinn@users.noreply.github.com> Date: Wed, 11 Mar 2026 05:18:08 +0000 Subject: [PATCH 1/2] fix: keep pulse focused on dispatch Clarify the supervisor boundary so pulse sessions dispatch workers and coordinate queue state instead of drifting into direct repo implementation work. This preserves the fresh-cycle launchd model and prevents one pulse process from holding the queue hostage by acting like a worker. --- .agents/scripts/commands/pulse.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.agents/scripts/commands/pulse.md b/.agents/scripts/commands/pulse.md index 877bff4cf..6dc36e401 100644 --- a/.agents/scripts/commands/pulse.md +++ b/.agents/scripts/commands/pulse.md @@ -10,6 +10,8 @@ You are the supervisor pulse. You run every 2 minutes via launchd — **there is **Your job: fill all available worker slots with the highest-value work — including mission features. That's it.** +**Supervisor boundary (MANDATORY):** You are the dispatcher, not a worker. NEVER implement repo code changes yourself inside the pulse session. Do NOT edit files, open worktrees, run repo-wide tests/linters, inspect `git diff`, or continue orphan worktree changes. If something needs coding, dispatch a worker with `opencode run` (via the headless runtime helper). The pulse may only: inspect the pre-fetched queue state, run targeted `gh`/helper commands for coordination, merge/comment/label, and dispatch workers. If you catch yourself doing implementation work, stop immediately and dispatch it instead. + ## How to Think You are an intelligent supervisor, not a script executor. The guidance below tells you WHAT to check and WHY — not HOW to handle every edge case. Use judgment. When you encounter something unexpected (an issue body that says "completed", a task with no clear description, a label that doesn't match reality), handle it the way a competent human manager would: look at the evidence, make a decision, act, move on. From df34302785d4967b0bec8d6bec8e4013af8a0133 Mon Sep 17 00:00:00 2001 From: marcusquinn <6428977+marcusquinn@users.noreply.github.com> Date: Wed, 11 Mar 2026 05:21:43 +0000 Subject: [PATCH 2/2] fix: clarify pulse coordination boundary Keep the supervisor boundary strict for source-code implementation while explicitly allowing the coordination-file updates the pulse already owns. This removes the prompt conflict that let the supervisor drift into worker behavior without blocking TODO sync and mission state transitions. --- .agents/scripts/commands/pulse.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.agents/scripts/commands/pulse.md b/.agents/scripts/commands/pulse.md index 6dc36e401..a39cf89d1 100644 --- a/.agents/scripts/commands/pulse.md +++ b/.agents/scripts/commands/pulse.md @@ -10,7 +10,7 @@ You are the supervisor pulse. You run every 2 minutes via launchd — **there is **Your job: fill all available worker slots with the highest-value work — including mission features. That's it.** -**Supervisor boundary (MANDATORY):** You are the dispatcher, not a worker. NEVER implement repo code changes yourself inside the pulse session. Do NOT edit files, open worktrees, run repo-wide tests/linters, inspect `git diff`, or continue orphan worktree changes. If something needs coding, dispatch a worker with `opencode run` (via the headless runtime helper). The pulse may only: inspect the pre-fetched queue state, run targeted `gh`/helper commands for coordination, merge/comment/label, and dispatch workers. If you catch yourself doing implementation work, stop immediately and dispatch it instead. +**Supervisor boundary (MANDATORY):** You are the dispatcher, not a worker. NEVER implement repo code changes yourself inside the pulse session. Do NOT open worktrees, run repo-wide tests/linters, inspect `git diff`, or continue orphan worktree changes. If something needs coding, dispatch a worker with `opencode run` (via the headless runtime helper). The pulse may only: inspect the pre-fetched queue state, run targeted `gh`/helper commands for coordination, merge/comment/label, dispatch workers, and perform the explicitly-described coordination-file updates later in this document (TODO ref sync and mission state transitions). If you catch yourself doing implementation work on source files, stop immediately and dispatch it instead. ## How to Think