@compr/opscontext-mcp 2.1.0 → 2.1.3

package/dist/tools-manifest.d.ts

@@ -0,0 +1,37 @@
+/**
+ * Tools Manifest — single source of truth for the MCP tool catalog.
+ *
+ * Why: the info panel in the VS Code extension (and the README) historically
+ * hardcoded the tool count ("Active on all 17 MCP tools"). When new tools
+ * shipped (drift_status was the 21st), those displays silently drifted.
+ *
+ * Fix: every tool exposed via `server.tool(...)` in `index.ts` MUST appear
+ * in `ALL_TOOLS` below. A regression test in `tests/tools-manifest.test.ts`
+ * counts `^server.tool(` lines in `index.ts` and asserts the count matches
+ * `ALL_TOOLS.length`. If you add or remove a tool, this list + the test
+ * fail together — no silent drift possible.
+ *
+ * Consumers:
+ *   - `index.ts` writes `~/.contextengine/server-meta.json` on startup with
+ *     `{ toolCount, premiumCount, freeCount, version, generatedAt }` so the
+ *     VS Code extension can read it without needing an active MCP session.
+ *   - `activation.ts` imports `PREMIUM_TOOL_NAMES` (the subset that requires
+ *     a PRO license).
+ *
+ * @module tools-manifest
+ */
+/**
+ * Every tool name registered on the MCP server, in registration order.
+ * Order is not load-bearing — kept stable for easier diffs.
+ */
+export declare const ALL_TOOLS: readonly ["search_context", "list_sources", "read_source", "reindex", "list_projects", "check_ports", "run_audit", "score_project", "save_session", "load_session", "list_sessions", "delete_session", "audit_verify", "drift_status", "end_session", "save_learning", "list_learnings", "delete_learning", "import_learnings", "activate", "activation_status"];
+/**
+ * The 4 tools gated behind PRO activation. Subset of `ALL_TOOLS`.
+ * Must match `PREMIUM_TOOLS` in `src/activation.ts` (asserted by test).
+ */
+export declare const PREMIUM_TOOL_NAMES: readonly ["score_project", "run_audit", "check_ports", "list_projects"];
+/** Total count — what users see as "Active on all N MCP tools". */
+export declare const TOOL_COUNT: 21;
+/** Free-tier tool count — everything except `PREMIUM_TOOL_NAMES`. */
+export declare const FREE_TOOL_COUNT: number;
+//# sourceMappingURL=tools-manifest.d.ts.map

package/dist/tools-manifest.js

@@ -0,0 +1,64 @@
+/**
+ * Tools Manifest — single source of truth for the MCP tool catalog.
+ *
+ * Why: the info panel in the VS Code extension (and the README) historically
+ * hardcoded the tool count ("Active on all 17 MCP tools"). When new tools
+ * shipped (drift_status was the 21st), those displays silently drifted.
+ *
+ * Fix: every tool exposed via `server.tool(...)` in `index.ts` MUST appear
+ * in `ALL_TOOLS` below. A regression test in `tests/tools-manifest.test.ts`
+ * counts `^server.tool(` lines in `index.ts` and asserts the count matches
+ * `ALL_TOOLS.length`. If you add or remove a tool, this list + the test
+ * fail together — no silent drift possible.
+ *
+ * Consumers:
+ *   - `index.ts` writes `~/.contextengine/server-meta.json` on startup with
+ *     `{ toolCount, premiumCount, freeCount, version, generatedAt }` so the
+ *     VS Code extension can read it without needing an active MCP session.
+ *   - `activation.ts` imports `PREMIUM_TOOL_NAMES` (the subset that requires
+ *     a PRO license).
+ *
+ * @module tools-manifest
+ */
+/**
+ * Every tool name registered on the MCP server, in registration order.
+ * Order is not load-bearing — kept stable for easier diffs.
+ */
+export const ALL_TOOLS = [
+    "search_context",
+    "list_sources",
+    "read_source",
+    "reindex",
+    "list_projects",
+    "check_ports",
+    "run_audit",
+    "score_project",
+    "save_session",
+    "load_session",
+    "list_sessions",
+    "delete_session",
+    "audit_verify",
+    "drift_status",
+    "end_session",
+    "save_learning",
+    "list_learnings",
+    "delete_learning",
+    "import_learnings",
+    "activate",
+    "activation_status",
+];
+/**
+ * The 4 tools gated behind PRO activation. Subset of `ALL_TOOLS`.
+ * Must match `PREMIUM_TOOLS` in `src/activation.ts` (asserted by test).
+ */
+export const PREMIUM_TOOL_NAMES = [
+    "score_project",
+    "run_audit",
+    "check_ports",
+    "list_projects",
+];
+/** Total count — what users see as "Active on all N MCP tools". */
+export const TOOL_COUNT = ALL_TOOLS.length;
+/** Free-tier tool count — everything except `PREMIUM_TOOL_NAMES`. */
+export const FREE_TOOL_COUNT = ALL_TOOLS.length - PREMIUM_TOOL_NAMES.length;
+//# sourceMappingURL=tools-manifest.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@compr/opscontext-mcp",
-  "version": "2.1.0",
+  "version": "2.1.3",
   "description": "OpsContext for AI Agents — read-only fleet visibility (PM2/nginx/Docker/git/cron) + tamper-evident audit log + policy-as-code hooks. The ops + compliance layer Claude Code can't grow natively.",
   "type": "module",
   "main": "dist/index.js",
@@ -44,8 +44,9 @@
     "developer-tools"
   ],
   "author": {
-    "name": "FASTPROD (PROD LLC)",
-    "url": "https://compr.fr"
+    "name": "PROD LLC (operating brand of CSS LLC, Swiss, est. 2005)",
+    "email": "yannick@compr.ch",
+    "url": "https://github.com/FASTPROD/ContextEngine/blob/main/docs/about.md"
   },
   "license": "BSL-1.1",
   "repository": {

package/skills/opscontext/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: opscontext
-description: "OpsContext for AI Agents — the ops + compliance layer Claude Code can't grow natively. Read-only fleet visibility (PM2/nginx/Docker/git/cron) + tamper-evident hash-chained audit log (SOC2 CC7.2 / ISO 27001 A.12.4.1) + declarative policy-as-code git hooks (.contextengine/policy.json with secret_patterns, doc_coverage, deploy_verify_hosts, bypass_tokens) + persistent learnings + hybrid BM25/semantic search. Use when: (1) searching project documentation or context files, (2) collecting operational insights from workspaces, (3) storing and retrieving persistent learnings across sessions, (4) auditing project compliance or AI-readiness, (5) managing session data, (6) verifying the audit log chain, (7) authoring/validating policy.json. Zero API keys — runs 100% locally with CPU embeddings."
+description: "OpsContext for AI Agents — the ops + compliance layer Claude Code can't grow natively. Read-only fleet visibility (PM2/nginx/Docker/git/cron) + tamper-evident hash-chained audit log producing evidence aligned with SOC 2 CC7.2 and ISO 27001 A.12.4.1 (evidence artifacts only — OpsContext itself is not certified; see docs/compliance/) + declarative policy-as-code git hooks (.contextengine/policy.json with secret_patterns, doc_coverage, deploy_verify_hosts, bypass_tokens) + persistent learnings + hybrid BM25/semantic search. Use when: (1) searching project documentation or context files, (2) collecting operational insights from workspaces, (3) storing and retrieving persistent learnings across sessions, (4) auditing project compliance or AI-readiness, (5) managing session data, (6) verifying the audit log chain, (7) authoring/validating policy.json. Zero API keys — runs 100% locally with CPU embeddings."
 homepage: https://www.npmjs.com/package/@compr/opscontext-mcp
 metadata: { "openclaw": { "emoji": "🧭", "requires": { "bins": ["npx"] }, "homepage": "https://www.npmjs.com/package/@compr/opscontext-mcp" } }
 ---