zopkit-bug-resolution-mcp 1.9.0 → 1.9.1

package/bin/zopkit-statusline.js

@@ -35,7 +35,7 @@
 import { readFileSync, writeFileSync, mkdirSync } from 'node:fs';
 import { join } from 'node:path';
 import { homedir, tmpdir } from 'node:os';
-import { loadConfig, post, readStdinJson, readClaudeAccount } from '../lib/zopkit-config.js';
+import { loadConfig, post, readStdinJson, readClaudeAccount, reporterVersion } from '../lib/zopkit-config.js';
 
 // Per-session throttle. The status line fires on every assistant message; a
 // 40-turn session would otherwise be 40 POSTs. 15s keeps the panel's 10s
@@ -94,6 +94,9 @@ function buildHeartbeat(p, cfg, fresh) {
     sessionName: cfg.shareSessionName ? (p.session_name ?? null) : null,
     model: p.model?.id ?? null,
     version: p.version ?? null,
+    // This reporter's version, so the server can tell "old client" apart
+    // from "nothing to report" — they produce identical rows otherwise.
+    reporterVersion: reporterVersion(),
 
     contextTokens: p.context_window?.total_input_tokens ?? null,
     contextLimit: p.context_window?.context_window_size ?? null,

package/index.js

@@ -91,7 +91,7 @@ if (!API_KEY) {
     'Generate one from the company-admin panel (Bug Reports → API Keys) and set it when registering this server.');
 }
 
-const server = new McpServer({ name: 'zopkit-bug-resolution', version: '1.9.0' });
+const server = new McpServer({ name: 'zopkit-bug-resolution', version: '1.9.1' });
 
 const BUG_SEVERITIES = ['low', 'medium', 'high', 'critical'];
 // Keep in sync with BUG_STATUSES in backend/src/db/schema/platform/bug-reports.ts.

package/lib/zopkit-config.js

@@ -16,11 +16,36 @@
 // Create it with:  npx zopkit-bug-resolution-mcp --init-usage-reporting
 
 import { readFileSync } from 'node:fs';
-import { join } from 'node:path';
+import { join, dirname } from 'node:path';
 import { homedir } from 'node:os';
+import { fileURLToPath } from 'node:url';
 
 export const CONFIG_PATH = join(homedir(), '.claude', '.zopkit-usage.json');
 
+/**
+ * This reporter's own version, sent with every heartbeat.
+ *
+ * The server cannot otherwise tell an OLD reporter apart from a machine
+ * with nothing to report: a pre-1.9.0 client sends perfect session rows
+ * and silently omits the account, which looks identical to a machine that
+ * has no signed-in Claude account. Both show up as "not reporting" and
+ * need completely different fixes.
+ *
+ * Read from package.json rather than hardcoded, so it cannot drift from
+ * the published version the way a duplicated constant would.
+ */
+let versionCache;
+export function reporterVersion() {
+  if (versionCache !== undefined) return versionCache;
+  try {
+    const here = dirname(fileURLToPath(import.meta.url));
+    versionCache = JSON.parse(readFileSync(join(here, '..', 'package.json'), 'utf8')).version ?? null;
+  } catch {
+    versionCache = null;
+  }
+  return versionCache;
+}
+
 /**
  * Which Anthropic account this machine is signed in to.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zopkit-bug-resolution-mcp",
-  "version": "1.9.0",
+  "version": "1.9.1",
   "type": "module",
   "description": "MCP server + status-line/hook reporters for Zopkit wrapper bug reports: fetch full bug context (with screenshots), submit how a bug was fixed, list bugs assigned to you, file new bug reports, and report REAL Claude Code usage \u2014 live per-session context and account rate limits via the status line, plus per-bug token attribution via PostToolUse hooks. Requires a BUG_REPORT_API_KEY (generated in the company-admin panel) \u2014 see README.md.",
   "license": "UNLICENSED",