groove-dev 0.27.45 → 0.27.48

package/CLAUDE.md

@@ -263,3 +263,10 @@ 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:** GROOVE manages project memory automatically. Do not read or write MEMORY.md or .groove/memory/ files directly.
+<!-- GROOVE:END -->

package/default/fix-beta-endpoint-deployment.md

@@ -0,0 +1,68 @@
+# BUG: POST /api/beta/validate returns 404 — not deployed
+
+From: Groove UI Team
+To: groovedev.ai Team
+Date: 2026-04-18
+Priority: BLOCKING
+
+## The Problem
+
+The beta invite code validation endpoint is returning 404 from nginx. The route handler was built (routes/beta.js, mounted in server.js) but it's not reachable in production.
+
+```bash
+curl -s https://groovedev.ai/api/beta/validate \
+  -H 'Content-Type: application/json' \
+  -d '{"code":"GROOVE-NET-ALPHA-001","machineId":"test"}'
+```
+
+Returns:
+```html
+<center>nginx/1.24.0 (Ubuntu)</center>
+404
+```
+
+This is an nginx 404, not an app-level 404. The request never reaches the Node.js server.
+
+## What Should Happen
+
+The endpoint should return:
+```json
+{"valid": true, "expiresAt": "2026-07-18T00:00:00Z", "features": ["network-node", "network-consumer"], "message": "Welcome to the Groove Network beta"}
+```
+
+Or for invalid codes:
+```json
+{"valid": false, "message": "Invalid invite code"}
+```
+
+## Likely Causes
+
+1. Nginx isn't proxying /api/beta/* to the Node.js app — needs a location block or the existing proxy_pass doesn't cover this path
+2. The Node.js server isn't running or was restarted without the new routes
+3. The route is mounted at a different path than /api/beta/validate
+
+## What to Check
+
+1. Nginx config — does it proxy /api/* to the Node.js backend? If routes are whitelisted individually, add /api/beta/*
+2. Is the Node.js server running? Check with: `pm2 status` or `systemctl status groovedev` (whatever process manager is used)
+3. Did server.js get deployed with the beta route mount? Verify the deployed code includes: `app.use('/api/beta', betaRoutes)` or equivalent
+4. Test locally on the server: `curl http://localhost:<app-port>/api/beta/validate -H 'Content-Type: application/json' -d '{"code":"test","machineId":"test"}'` — if this works, it's purely an nginx issue
+
+## Impact
+
+Every Groove app trying to activate a beta invite code fails. We have a hardcoded fallback for 5 ALPHA codes, but any codes generated through the admin portal (like GROOVE-NET-SWIFT-899) are completely broken until this is fixed. Beta testers cannot activate.
+
+## Expected Nginx Config
+
+Something like this should work (adjust upstream port):
+```nginx
+location /api/beta/ {
+    proxy_pass http://127.0.0.1:3000;
+    proxy_set_header Host $host;
+    proxy_set_header X-Real-IP $remote_addr;
+    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+    proxy_set_header X-Forwarded-Proto $scheme;
+}
+```
+
+Or if there's already a catch-all /api/ proxy, make sure it's not being overridden by a more specific location block.

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

@@ -1,6 +1,6 @@
 {
   "name": "@groove-dev/cli",
-  "version": "0.27.45",
+  "version": "0.27.48",
   "description": "GROOVE CLI — 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.45",
+  "version": "0.27.48",
   "description": "GROOVE daemon — agent orchestration engine",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",

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

@@ -4002,7 +4002,7 @@ Keep responses concise. Help them think, don't lecture them about the system the
 
     let proc;
     try {
-      proc = spawn('python', args, {
+      proc = spawn('python3.12', args, {
         cwd: deployPath,
         env: { ...process.env, PYTHONUNBUFFERED: '1' },
         stdio: ['ignore', 'pipe', 'pipe'],

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

@@ -128,7 +128,7 @@ export class IntegrationStore {
 
     if (entry.npmPackage) {
       try {
-        execFileSync('npm', ['install', entry.npmPackage], {
+        execFileSync('npm', ['install', '--legacy-peer-deps', entry.npmPackage], {
           cwd: this.integrationsDir,
           stdio: 'pipe',
           timeout: 120_000,
@@ -165,7 +165,7 @@ export class IntegrationStore {
     const entry = this.registry.find((s) => s.id === integrationId);
     if (entry?.npmPackage) {
       try {
-        execFileSync('npm', ['uninstall', entry.npmPackage], {
+        execFileSync('npm', ['uninstall', '--legacy-peer-deps', entry.npmPackage], {
           cwd: this.integrationsDir,
           stdio: 'pipe',
           timeout: 60_000,

package/node_modules/@groove-dev/daemon/src/providers/groove-network.js

@@ -26,7 +26,7 @@ function getConfig() {
 export class GrooveNetworkProvider extends Provider {
   static name = 'groove-network';
   static displayName = 'Groove Network';
-  static command = 'python';
+  static command = 'python3.12';
   static authType = 'none';
 
   static models = [
@@ -60,7 +60,7 @@ export class GrooveNetworkProvider extends Provider {
     ];
 
     return {
-      command: 'python',
+      command: 'python3.12',
       args,
       env: { PYTHONUNBUFFERED: '1' },
       cwd: deployPath,
@@ -73,7 +73,7 @@ export class GrooveNetworkProvider extends Provider {
     const m = model || GrooveNetworkProvider.models[0].id;
     const deployPath = expandHome(cfg.deployPath) || resolve(homedir(), 'Desktop/groove-deploy');
     return {
-      command: 'python',
+      command: 'python3.12',
       args: [
         '-m', 'src.consumer.client',
         '--relay', relay,