groove-dev 0.27.2 → 0.27.4

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # Changelog
 
+## v0.27.4 — Fix rotated agents abandoning mid-task work (2026-04-12)
+
+**The bug I introduced in v0.27.1.** The rotation handoff brief told agents: *"Wait for the user's next message, then answer it directly."* That instruction was intended to prevent "Resuming after rotation" announcements — but for an agent that was mid-task when rotation fired (e.g., a planner planning, a backend writing code), it said: *stop the work, wait for the user.* The user gave a direct feature request, the planner burned 3M tokens exploring before rotation, the new planner read "wait for next message" and delivered nothing.
+
+**Fix**
+- Rewritten handoff brief flips the instruction: *"Finish what you were doing. The user is waiting for YOUR output. Produce it. No preamble, no announcement."*
+- Explicitly calls out common mid-task states: "If you were a planner about to output a plan, output the plan now. If you were a builder about to make edits, make the edits."
+- Recent User Messages section is now labeled "what they've been asking for — deliver this."
+- Memory API contribution note de-emphasized (no longer prompts agents to proactively POST to `/api/memory/*` — it's opt-in, not a requirement).
+
+**Regression test added** to lock the fix: any brief containing "wait for the user's next message" now fails CI.
+
+## v0.27.3 — Planner sees ready-to-resume teammates (2026-04-12)
+
+Fixes a Mode 1 / Mode 2 detection bug where a planner spawned duplicate agents instead of routing work to existing teammates.
+
+**The bug**
+When a team is created with empty prompts (the "spawn the team first, then assign tasks" pattern), the builders complete in a few seconds (no task to do → return). Their status flips to `completed`. Later, when the planner spawns and looks at its intro context, the team section only listed `running`/`starting` agents — so the planner saw "you are the only agent on this project right now" and went Mode 1, spawning duplicates instead of routing to the existing ready-to-resume team.
+
+Not a regression from v0.27.x — this has been brittle for any empty-prompt team flow. Surfaced now.
+
+**Fix**
+- Introducer's team section now includes **recent completed teammates** alongside active ones, scoped to the same `teamId` with a 1-hour freshness window. Shown as "ready to resume" with an explicit note: *"Teammates marked 'ready' are part of your team. They finished their last task and will resume their session when assigned new work. If you're a planner, route new tasks to them by role — do NOT spawn duplicates."*
+- Planner role prompt (`process.js`) updated: Mode 2 detection now references the intro context's Team section directly, not just `AGENTS_REGISTRY.md`. Explicitly instructs: *"Teammates listed as 'ready to resume' are REAL agents. They WILL pick up new work when routed. NEVER spawn a new agent of a role that already exists."*
+
+**What this means for you**
+The flow that felt perfect — spawn the team, then iterate with the planner task-by-task — now works regardless of whether the builders are actively running or resting between tasks.
+
 ## v0.27.2 — Drop velocity trigger (2026-04-12)
 
 Following up on v0.27.1: the role-multiplier fix addressed the planner but left the same false-positive class live for any agent doing heavy exploration on a large codebase. Dropping velocity-based rotation entirely rather than papering over it further.

package/CLAUDE.md

@@ -263,10 +263,3 @@ Audit-driven release. Multi-agent orchestration system with 7 coordination layer
 - Dashboard: routing donut, cache panel, context health gauges
 - Monitor/QC agent mode (stay active, loop)
 - Distribution: demo video, HN launch, Twitter content
-
-<!-- GROOVE:START -->
-## GROOVE Orchestration (auto-injected)
-Active agents: 0
-See AGENTS_REGISTRY.md for full agent state.
-**Memory policy:** Ignore auto-memory. Do not read or write MEMORY.md. GROOVE manages all context.
-<!-- GROOVE:END -->

package/node_modules/@groove-dev/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groove-dev/cli",
-  "version": "0.27.2",
+  "version": "0.27.4",
   "description": "GROOVE CLI \u2014 manage AI coding agents from your terminal",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",

package/node_modules/@groove-dev/daemon/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groove-dev/daemon",
-  "version": "0.27.2",
+  "version": "0.27.4",
   "description": "GROOVE daemon — agent orchestration engine",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",

package/node_modules/@groove-dev/daemon/src/introducer.js

@@ -16,10 +16,30 @@ export class Introducer {
   generateContext(newAgent, options = {}) {
     const { taskNegotiation } = options;
     const agents = this.daemon.registry.getAll();
-    // Only include ACTIVE agents — not completed/killed ones from previous sessions
-    // Completed agents' work is captured in the journalist's project map, not here
-    const others = agents.filter((a) => a.id !== newAgent.id &&
-      (a.status === 'running' || a.status === 'starting'));
+
+    // Team awareness must include completed teammates, not just running ones.
+    // Agents that finished an empty-prompt standup (common pattern: spawn the
+    // team upfront, then direct them task-by-task) sit in `completed` status
+    // until resumed. Hiding them from the new agent's context makes planners
+    // falsely conclude "I'm alone" and spawn duplicate roles.
+    //
+    // Scope to the same team so one team's agents don't leak into another's
+    // context. Completed teammates get a 1-hour freshness cutoff so truly
+    // stale ones don't clutter the intro.
+    const COMPLETED_WINDOW_MS = 60 * 60 * 1000;
+    const sameTeam = (a) =>
+      a.id !== newAgent.id &&
+      (!newAgent.teamId || a.teamId === newAgent.teamId);
+    const activeOthers = agents.filter((a) =>
+      sameTeam(a) && (a.status === 'running' || a.status === 'starting')
+    );
+    const recentCompleted = agents.filter((a) => {
+      if (!sameTeam(a)) return false;
+      if (a.status !== 'completed') return false;
+      const ts = a.lastActivity ? new Date(a.lastActivity).getTime() : 0;
+      return Date.now() - ts < COMPLETED_WINDOW_MS;
+    });
+    const others = [...activeOthers, ...recentCompleted];
 
     const lines = [
       `# GROOVE Agent Context`,
@@ -42,8 +62,17 @@ export class Introducer {
     if (others.length === 0) {
       lines.push('You are the only agent on this project right now.');
     } else {
-      lines.push(`## Team (${others.length} other agent${others.length > 1 ? 's' : ''})`);
+      const activeCount = activeOthers.length;
+      const readyCount = recentCompleted.length;
+      const parts = [];
+      if (activeCount > 0) parts.push(`${activeCount} active`);
+      if (readyCount > 0) parts.push(`${readyCount} ready to resume`);
+      lines.push(`## Team (${others.length} teammate${others.length > 1 ? 's' : ''} — ${parts.join(', ')})`);
       lines.push('');
+      if (readyCount > 0) {
+        lines.push(`**Teammates marked "ready" are part of your team.** They finished their last task and will resume their session when assigned new work. If you're a planner, route new tasks to them by role — do NOT spawn duplicates.`);
+        lines.push('');
+      }
 
       // Collect all files created by teammates for the project files section
       const allTeamFiles = [];
@@ -51,7 +80,8 @@ export class Introducer {
       for (const other of others) {
         const scope = other.scope?.length > 0 ? other.scope.join(', ') : 'unrestricted';
         const dir = other.workingDir ? ` — dir: ${other.workingDir}` : '';
-        lines.push(`- **${other.name}** (${other.role}) — scope: ${scope}${dir} — ${other.status}`);
+        const statusLabel = other.status === 'completed' ? 'ready to resume' : other.status;
+        lines.push(`- **${other.name}** (${other.role}) — scope: ${scope}${dir} — ${statusLabel}`);
 
         // Get files this agent created/modified
         const files = this.daemon.journalist?.getAgentFiles(other) || [];
@@ -141,10 +171,9 @@ export class Introducer {
             lines.push(discoveries);
           }
 
-          lines.push('');
-          lines.push(`You can contribute to this memory via:`);
-          lines.push(`- \`POST /api/memory/discoveries\` — share an error→fix you found`);
-          lines.push(`- \`POST /api/memory/constraints\` — declare a project rule you discovered`);
+          // Contributing to memory is opt-in. Only mention if the agent
+          // explicitly needs to record something — no proactive prompting.
+          // (Optional: `POST /api/memory/discoveries` or `POST /api/memory/constraints`)
         }
       }
 

package/node_modules/@groove-dev/daemon/src/journalist.js

@@ -706,14 +706,23 @@ export class Journalist {
       `You are **${agent.name}** (role: ${agent.role}). This is an internal context refresh — `,
       `the conversation with the user is ongoing and must feel seamless to them. They cannot see this brief.`,
       ``,
-      `## CRITICAL: Continue Seamlessly`,
+      `## CRITICAL: Finish What You Were Doing`,
+      ``,
+      `The previous session was mid-work when this refresh happened. YOUR JOB IS TO COMPLETE THAT WORK.`,
+      ``,
+      `- If Recent User Messages show an unanswered request, deliver the answer.`,
+      `- If Recent Tool Calls show exploration/planning/building in progress, finish it and deliver the output.`,
+      `- If you were a planner about to output a plan, output the plan now.`,
+      `- If you were a builder about to make edits, make the edits.`,
       ``,
       `Do NOT announce a restart, rotation, or resumption. Do NOT greet the user. Do NOT say `,
-      `"resuming", "continuing from where I left off", "let me check state again", or anything `,
-      `that signals a break in the conversation. The user's next message should be answered as `,
-      `if the last turn of conversation just happened — because from their side, it did.`,
+      `"resuming", "let me check state again", "here's where I was", or anything that signals a `,
+      `break. Do NOT ask "what would you like me to do" — the user already told you. Do NOT `,
+      `just wait — the user is waiting for YOUR output.`,
+      ``,
+      `From the user's perspective, the conversation never paused. Act accordingly.`,
       ``,
-      conversationSummary ? `## Recent User Messages (what they've been asking for)\n\n${conversationSummary}\n` : '',
+      conversationSummary ? `## Recent User Messages (what they've been asking for — deliver this)\n\n${conversationSummary}\n` : '',
       recentChain ? `## Rotation History (recent)\n\n${recentChain}\n` : '',
       `## Your Identity`,
       `- Role: ${agent.role}`,
@@ -722,21 +731,20 @@ export class Journalist {
       agent.workingDir ? `- Working directory: ${agent.workingDir}` : '',
       ``,
       `## Session State`,
-      `- Tokens used: ${agent.tokensUsed}`,
-      `- Tool calls: ${entries.filter((e) => e.type === 'tool').length}`,
+      `- Tokens used before refresh: ${agent.tokensUsed}`,
+      `- Tool calls completed: ${entries.filter((e) => e.type === 'tool').length}`,
       ``,
-      toolSummary ? `### Recent tool calls\n${toolSummary}\n` : '',
+      toolSummary ? `### Recent tool calls (what you were doing)\n${toolSummary}\n` : '',
       resultSummary ? `### Last results\n${resultSummary}\n` : '',
       errorSummary ? `### Unresolved errors\n${errorSummary}\n` : '',
       `## Current Project State`,
       ``,
       projectMap ? projectMap.slice(0, 10000) : 'No project map available yet.',
       ``,
-      `## How to Respond`,
+      `## Your Next Action`,
       ``,
-      `Wait for the user's next message, then answer it directly. If they asked a question or gave `,
-      `an instruction in the Recent User Messages section above and it's still unanswered, address `,
-      `that naturally. Match the tone and continuity of a conversation that never paused.`,
+      `Look at Recent User Messages and Recent Tool Calls. Decide what output the user is waiting `,
+      `for right now. Produce it. No preamble, no announcement, just the answer or work product.`,
       agent.workingDir ? `Stay within your working directory: ${agent.workingDir}.` : '',
       agent.prompt ? `\nOriginal task context: ${agent.prompt}` : '',
     ].filter(Boolean).join('\n');

package/node_modules/@groove-dev/daemon/src/process.js

@@ -196,8 +196,10 @@ Do NOT re-explore the entire codebase. You already know it from team creation.
 Just read the specific files related to the bug/feature, decide which existing agent should handle it, and write the routing config. This should be FAST — under 5 tool calls.
 
 HOW TO DETECT WHICH MODE:
-- Read AGENTS_REGISTRY.md. If it lists agents with roles matching your team (frontend, backend, fullstack), you are in MODE 2.
-- If no agents exist or only a planner exists, you are in MODE 1.
+- Check the Team section of YOUR intro context (above this prompt). If it lists any teammates — active OR ready-to-resume — you are in MODE 2.
+- If no teammates exist or only a planner exists, you are in MODE 1.
+- Teammates listed as "ready to resume" are REAL agents on your team. They finished their last task and await new instructions. They WILL pick up new work when you route it to them via recommended-team.json. Do NOT treat them as absent.
+- NEVER spawn a new agent of a role that already exists in your team. A second backend when a backend already exists is always a bug.
 
 After completing your plan, you MUST write .groove/recommended-team.json — EVERY TIME, no exceptions.
 

package/node_modules/@groove-dev/daemon/test/journalist.test.js

@@ -201,6 +201,36 @@ describe('Journalist', () => {
       assert.ok(brief.includes('Build the auth API'));
       assert.ok(brief.includes('Write'));
     });
+
+    it('instructs the agent to deliver the output, not passively wait', async () => {
+      // Regression test: v0.27.1 brief told the agent to "wait for the user's
+      // next message" which caused planners to sit idle mid-plan after a
+      // rotation, burning tokens without producing output. Agents must be
+      // told to finish the work in flight, not wait for further prompting.
+      const { daemon, grooveDir } = createMockDaemon();
+      const journalist = new Journalist(daemon);
+      writeFileSync(join(grooveDir, 'logs', 'planner-1.log'), JSON.stringify({
+        type: 'assistant',
+        message: { content: [{ type: 'tool_use', name: 'Read', input: { file_path: 'src/index.js' } }] },
+      }));
+
+      const agent = {
+        id: 'p1', name: 'planner-1', role: 'planner',
+        provider: 'claude-code', scope: [],
+        tokensUsed: 2_000_000, prompt: 'Plan voice integrations',
+      };
+
+      const brief = await journalist.generateHandoffBrief(agent);
+
+      // The brief MUST NOT contain the old passive instruction
+      assert.ok(!/wait for the user's next message/i.test(brief),
+        'brief must not tell agent to wait for next message');
+      // The brief MUST tell the agent to complete/deliver the work
+      assert.ok(/finish|deliver|complete|produce it/i.test(brief),
+        'brief must instruct the agent to finish the work');
+      // Pass-through: planner-specific instruction
+      assert.ok(/output the plan|deliver/i.test(brief));
+    });
   });
 
   describe('status', () => {

package/node_modules/@groove-dev/gui/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groove-dev/gui",
-  "version": "0.27.2",
+  "version": "0.27.4",
   "description": "GROOVE GUI — visual agent control plane",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "groove-dev",
-  "version": "0.27.2",
+  "version": "0.27.4",
   "description": "Open-source agent orchestration layer — the AI company OS. Local model agent engine (GGUF/Ollama/llama-server), HuggingFace model browser, MCP integrations (Slack, Gmail, Stripe, 15+), agent scheduling (cron), business roles (CMO, CFO, EA). GUI dashboard, multi-agent coordination, zero cold-start, infinite sessions. Works with Claude Code, Codex, Gemini CLI, Ollama, any local model.",
   "license": "FSL-1.1-Apache-2.0",
   "author": "Groove Dev <hello@groovedev.ai> (https://groovedev.ai)",

package/packages/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groove-dev/cli",
-  "version": "0.27.2",
+  "version": "0.27.4",
   "description": "GROOVE CLI \u2014 manage AI coding agents from your terminal",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",

package/packages/daemon/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groove-dev/daemon",
-  "version": "0.27.2",
+  "version": "0.27.4",
   "description": "GROOVE daemon — agent orchestration engine",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",

package/packages/daemon/src/introducer.js

@@ -16,10 +16,30 @@ export class Introducer {
   generateContext(newAgent, options = {}) {
     const { taskNegotiation } = options;
     const agents = this.daemon.registry.getAll();
-    // Only include ACTIVE agents — not completed/killed ones from previous sessions
-    // Completed agents' work is captured in the journalist's project map, not here
-    const others = agents.filter((a) => a.id !== newAgent.id &&
-      (a.status === 'running' || a.status === 'starting'));
+
+    // Team awareness must include completed teammates, not just running ones.
+    // Agents that finished an empty-prompt standup (common pattern: spawn the
+    // team upfront, then direct them task-by-task) sit in `completed` status
+    // until resumed. Hiding them from the new agent's context makes planners
+    // falsely conclude "I'm alone" and spawn duplicate roles.
+    //
+    // Scope to the same team so one team's agents don't leak into another's
+    // context. Completed teammates get a 1-hour freshness cutoff so truly
+    // stale ones don't clutter the intro.
+    const COMPLETED_WINDOW_MS = 60 * 60 * 1000;
+    const sameTeam = (a) =>
+      a.id !== newAgent.id &&
+      (!newAgent.teamId || a.teamId === newAgent.teamId);
+    const activeOthers = agents.filter((a) =>
+      sameTeam(a) && (a.status === 'running' || a.status === 'starting')
+    );
+    const recentCompleted = agents.filter((a) => {
+      if (!sameTeam(a)) return false;
+      if (a.status !== 'completed') return false;
+      const ts = a.lastActivity ? new Date(a.lastActivity).getTime() : 0;
+      return Date.now() - ts < COMPLETED_WINDOW_MS;
+    });
+    const others = [...activeOthers, ...recentCompleted];
 
     const lines = [
       `# GROOVE Agent Context`,
@@ -42,8 +62,17 @@ export class Introducer {
     if (others.length === 0) {
       lines.push('You are the only agent on this project right now.');
     } else {
-      lines.push(`## Team (${others.length} other agent${others.length > 1 ? 's' : ''})`);
+      const activeCount = activeOthers.length;
+      const readyCount = recentCompleted.length;
+      const parts = [];
+      if (activeCount > 0) parts.push(`${activeCount} active`);
+      if (readyCount > 0) parts.push(`${readyCount} ready to resume`);
+      lines.push(`## Team (${others.length} teammate${others.length > 1 ? 's' : ''} — ${parts.join(', ')})`);
       lines.push('');
+      if (readyCount > 0) {
+        lines.push(`**Teammates marked "ready" are part of your team.** They finished their last task and will resume their session when assigned new work. If you're a planner, route new tasks to them by role — do NOT spawn duplicates.`);
+        lines.push('');
+      }
 
       // Collect all files created by teammates for the project files section
       const allTeamFiles = [];
@@ -51,7 +80,8 @@ export class Introducer {
       for (const other of others) {
         const scope = other.scope?.length > 0 ? other.scope.join(', ') : 'unrestricted';
         const dir = other.workingDir ? ` — dir: ${other.workingDir}` : '';
-        lines.push(`- **${other.name}** (${other.role}) — scope: ${scope}${dir} — ${other.status}`);
+        const statusLabel = other.status === 'completed' ? 'ready to resume' : other.status;
+        lines.push(`- **${other.name}** (${other.role}) — scope: ${scope}${dir} — ${statusLabel}`);
 
         // Get files this agent created/modified
         const files = this.daemon.journalist?.getAgentFiles(other) || [];
@@ -141,10 +171,9 @@ export class Introducer {
             lines.push(discoveries);
           }
 
-          lines.push('');
-          lines.push(`You can contribute to this memory via:`);
-          lines.push(`- \`POST /api/memory/discoveries\` — share an error→fix you found`);
-          lines.push(`- \`POST /api/memory/constraints\` — declare a project rule you discovered`);
+          // Contributing to memory is opt-in. Only mention if the agent
+          // explicitly needs to record something — no proactive prompting.
+          // (Optional: `POST /api/memory/discoveries` or `POST /api/memory/constraints`)
         }
       }
 

package/packages/daemon/src/journalist.js

@@ -706,14 +706,23 @@ export class Journalist {
       `You are **${agent.name}** (role: ${agent.role}). This is an internal context refresh — `,
       `the conversation with the user is ongoing and must feel seamless to them. They cannot see this brief.`,
       ``,
-      `## CRITICAL: Continue Seamlessly`,
+      `## CRITICAL: Finish What You Were Doing`,
+      ``,
+      `The previous session was mid-work when this refresh happened. YOUR JOB IS TO COMPLETE THAT WORK.`,
+      ``,
+      `- If Recent User Messages show an unanswered request, deliver the answer.`,
+      `- If Recent Tool Calls show exploration/planning/building in progress, finish it and deliver the output.`,
+      `- If you were a planner about to output a plan, output the plan now.`,
+      `- If you were a builder about to make edits, make the edits.`,
       ``,
       `Do NOT announce a restart, rotation, or resumption. Do NOT greet the user. Do NOT say `,
-      `"resuming", "continuing from where I left off", "let me check state again", or anything `,
-      `that signals a break in the conversation. The user's next message should be answered as `,
-      `if the last turn of conversation just happened — because from their side, it did.`,
+      `"resuming", "let me check state again", "here's where I was", or anything that signals a `,
+      `break. Do NOT ask "what would you like me to do" — the user already told you. Do NOT `,
+      `just wait — the user is waiting for YOUR output.`,
+      ``,
+      `From the user's perspective, the conversation never paused. Act accordingly.`,
       ``,
-      conversationSummary ? `## Recent User Messages (what they've been asking for)\n\n${conversationSummary}\n` : '',
+      conversationSummary ? `## Recent User Messages (what they've been asking for — deliver this)\n\n${conversationSummary}\n` : '',
       recentChain ? `## Rotation History (recent)\n\n${recentChain}\n` : '',
       `## Your Identity`,
       `- Role: ${agent.role}`,
@@ -722,21 +731,20 @@ export class Journalist {
       agent.workingDir ? `- Working directory: ${agent.workingDir}` : '',
       ``,
       `## Session State`,
-      `- Tokens used: ${agent.tokensUsed}`,
-      `- Tool calls: ${entries.filter((e) => e.type === 'tool').length}`,
+      `- Tokens used before refresh: ${agent.tokensUsed}`,
+      `- Tool calls completed: ${entries.filter((e) => e.type === 'tool').length}`,
       ``,
-      toolSummary ? `### Recent tool calls\n${toolSummary}\n` : '',
+      toolSummary ? `### Recent tool calls (what you were doing)\n${toolSummary}\n` : '',
       resultSummary ? `### Last results\n${resultSummary}\n` : '',
       errorSummary ? `### Unresolved errors\n${errorSummary}\n` : '',
       `## Current Project State`,
       ``,
       projectMap ? projectMap.slice(0, 10000) : 'No project map available yet.',
       ``,
-      `## How to Respond`,
+      `## Your Next Action`,
       ``,
-      `Wait for the user's next message, then answer it directly. If they asked a question or gave `,
-      `an instruction in the Recent User Messages section above and it's still unanswered, address `,
-      `that naturally. Match the tone and continuity of a conversation that never paused.`,
+      `Look at Recent User Messages and Recent Tool Calls. Decide what output the user is waiting `,
+      `for right now. Produce it. No preamble, no announcement, just the answer or work product.`,
       agent.workingDir ? `Stay within your working directory: ${agent.workingDir}.` : '',
       agent.prompt ? `\nOriginal task context: ${agent.prompt}` : '',
     ].filter(Boolean).join('\n');

package/packages/daemon/src/process.js

@@ -196,8 +196,10 @@ Do NOT re-explore the entire codebase. You already know it from team creation.
 Just read the specific files related to the bug/feature, decide which existing agent should handle it, and write the routing config. This should be FAST — under 5 tool calls.
 
 HOW TO DETECT WHICH MODE:
-- Read AGENTS_REGISTRY.md. If it lists agents with roles matching your team (frontend, backend, fullstack), you are in MODE 2.
-- If no agents exist or only a planner exists, you are in MODE 1.
+- Check the Team section of YOUR intro context (above this prompt). If it lists any teammates — active OR ready-to-resume — you are in MODE 2.
+- If no teammates exist or only a planner exists, you are in MODE 1.
+- Teammates listed as "ready to resume" are REAL agents on your team. They finished their last task and await new instructions. They WILL pick up new work when you route it to them via recommended-team.json. Do NOT treat them as absent.
+- NEVER spawn a new agent of a role that already exists in your team. A second backend when a backend already exists is always a bug.
 
 After completing your plan, you MUST write .groove/recommended-team.json — EVERY TIME, no exceptions.
 

package/packages/gui/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groove-dev/gui",
-  "version": "0.27.2",
+  "version": "0.27.4",
   "description": "GROOVE GUI — visual agent control plane",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",