@thehammer/danx-dashboard-mcp 0.1.290 → 0.1.291

package/dist/session-stats.js

@@ -87,6 +87,7 @@ export class OperatorSessionStats {
         }
         let carried = false;
         let landed = true;
+        let planless = false;
         await this.usage.flush({
             applyStats: async (_dispatchId, payload) => {
                 carried = true;
@@ -95,12 +96,24 @@ export class OperatorSessionStats {
                     landed = false;
                     throw new Error("stats heartbeat did not reach the dashboard");
                 }
+                if (answer.statsNotStored === "no_plan") {
+                    planless = true;
+                    throw new Error("stats heartbeat refused: the session is on no plan, so the dashboard stores no stats for it");
+                }
                 if (answer.stats === null) {
                     throw new Error(`stats heartbeat answered HTTP ${answer.status} without stats`);
                 }
                 return answer.stats;
             },
         }, OPERATOR_DISPATCH_REF);
+        if (planless) {
+            // DX-4892: re-queueing would resend this batch on every tick for as long as the session stays planless. Drop the collector instead:
+            // the plain heartbeats that follow start collection again from the stored cursors once an answer carries stats (the session is bound).
+            this.watcher?.stop();
+            this.watcher = null;
+            this.usage = newCollector();
+            return landed;
+        }
         if (carried)
             return landed;
         return (await send(undefined)).landed;

package/dist/session-stream.js

@@ -296,7 +296,7 @@ title) {
     // request never landed at all, which is exactly the signal the silent-
     // failure counter in the relay below needs. Still never throws.
     if (outcome.kind !== "answer")
-        return { landed: false, status: null, stats: null, revocation: null, title: null };
+        return { landed: false, status: null, stats: null, statsNotStored: null, revocation: null, title: null };
     // DX-2954 — the answer's `stats` (the operator dispatch's stored or
     // just-written totals and cursors) feed the session's stats collector.
     const ok = outcome.status >= 200 && outcome.status < 300;
@@ -321,6 +321,8 @@ title) {
         landed: true,
         status: outcome.status,
         stats: answered,
+        // DX-4892: the dashboard says why carried stats were not stored (a session on no plan), instead of the relay inferring it from a missing `stats`.
+        statsNotStored: ok && isRecord(outcome.body) && isRecord(outcome.body.statsError) && outcome.body.statsError.kind === "no_plan" ? "no_plan" : null,
         revocation: keyRevocationOf({ ok: false, status: outcome.status, body: outcome.body }),
         title: storedTitle,
     };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thehammer/danx-dashboard-mcp",
-  "version": "0.1.290",
+  "version": "0.1.291",
   "description": "Stdio MCP server fronting danxbot's dashboard API for agents (operator sessions and dispatched workers alike): the generic danxbot_api/danxbot_api_list/danxbot_api_spec tools reach any route the caller's credential may call, plus dedicated agent-specific tools (plan_connect, request_permission, attach_file, and danxbot_slack_reply) (DX-3465, PLN-11 R-25).",
   "license": "MIT",
   "type": "module",