@memnexus-ai/mx-agent-cli 0.1.181 → 0.1.182

package/dist/__tests__/coordination-brief-pin.test.d.ts

@@ -0,0 +1,20 @@
+/**
+ * KI-COORDMT-HOOK-EXPORT-ROBUSTNESS — publish-side sha pin for the session-start
+ * coordination-brief hook (Red Team v2.41 Step-6 Major).
+ *
+ * WHY HERE (defense in depth): the CLI publish workflow (mx-agent-cli-publish.yml)
+ * triggers on agent-config/** and BUNDLES agent-config/hooks/coordination-brief.sh
+ * into the published package (scripts/bundle-config.mjs). Its test gate is the CLI
+ * `npm test` suite. Without a pin assertion IN THIS SUITE, a PR that edits only the
+ * hook could ship an un-vetted hook in a new CLI even if someone later loosens the
+ * coordination-service workflow's path filters. This test makes that impossible:
+ * the CLI cannot go green — and therefore cannot publish — with a drifted hook.
+ *
+ * THREE PIN SITES MUST BUMP TOGETHER when coordination-brief.sh changes:
+ *   1. coordination-service/src/__tests__/coordination-brief-drift.test.ts  (PINNED_SHA256)
+ *   2. cli/src/__tests__/coordination-brief-pin.test.ts                     (this file)
+ *   3. spearmint-private .github/workflows/coordination-hook-pin.yml        (PINNED_SHA256)
+ * See the drift-test header for the full re-distribution procedure.
+ */
+export {};
+//# sourceMappingURL=coordination-brief-pin.test.d.ts.map

package/dist/__tests__/coordination-brief-pin.test.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"coordination-brief-pin.test.d.ts","sourceRoot":"","sources":["../../src/__tests__/coordination-brief-pin.test.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG"}

package/dist/__tests__/coordination-brief-pin.test.js

@@ -0,0 +1,37 @@
+/**
+ * KI-COORDMT-HOOK-EXPORT-ROBUSTNESS — publish-side sha pin for the session-start
+ * coordination-brief hook (Red Team v2.41 Step-6 Major).
+ *
+ * WHY HERE (defense in depth): the CLI publish workflow (mx-agent-cli-publish.yml)
+ * triggers on agent-config/** and BUNDLES agent-config/hooks/coordination-brief.sh
+ * into the published package (scripts/bundle-config.mjs). Its test gate is the CLI
+ * `npm test` suite. Without a pin assertion IN THIS SUITE, a PR that edits only the
+ * hook could ship an un-vetted hook in a new CLI even if someone later loosens the
+ * coordination-service workflow's path filters. This test makes that impossible:
+ * the CLI cannot go green — and therefore cannot publish — with a drifted hook.
+ *
+ * THREE PIN SITES MUST BUMP TOGETHER when coordination-brief.sh changes:
+ *   1. coordination-service/src/__tests__/coordination-brief-drift.test.ts  (PINNED_SHA256)
+ *   2. cli/src/__tests__/coordination-brief-pin.test.ts                     (this file)
+ *   3. spearmint-private .github/workflows/coordination-hook-pin.yml        (PINNED_SHA256)
+ * See the drift-test header for the full re-distribution procedure.
+ */
+import { describe, it, expect } from 'vitest';
+import { readFileSync } from 'node:fs';
+import { createHash } from 'node:crypto';
+import { fileURLToPath } from 'node:url';
+import { join, dirname } from 'node:path';
+const here = dirname(fileURLToPath(import.meta.url));
+// cli/src/__tests__ → mx-agent-system/agent-config/hooks/coordination-brief.sh
+const HOOK_FILE = join(here, '..', '..', '..', 'agent-config', 'hooks', 'coordination-brief.sh');
+// Mirror of the platform PINNED_SHA256 (coordination-brief-drift.test.ts). Bump in
+// lockstep with the other two pin sites named in the header above.
+const PINNED_SHA256 = '3c636034e87f89efdb4d4b2cb270e73b2769710dde42651cdd9ee7d865028962';
+describe('coordination-brief hook pin — publish-side gate (KI-COORDMT-HOOK-EXPORT-ROBUSTNESS)', () => {
+    it('the bundled hook matches its pinned sha256 (else the CLI must not publish)', () => {
+        const bytes = readFileSync(HOOK_FILE);
+        const actual = createHash('sha256').update(bytes).digest('hex');
+        expect(actual).toBe(PINNED_SHA256);
+    });
+});
+//# sourceMappingURL=coordination-brief-pin.test.js.map

package/dist/__tests__/coordination-brief-pin.test.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"coordination-brief-pin.test.js","sourceRoot":"","sources":["../../src/__tests__/coordination-brief-pin.test.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAEH,OAAO,EAAE,QAAQ,EAAE,EAAE,EAAE,MAAM,EAAE,MAAM,QAAQ,CAAC;AAC9C,OAAO,EAAE,YAAY,EAAE,MAAM,SAAS,CAAC;AACvC,OAAO,EAAE,UAAU,EAAE,MAAM,aAAa,CAAC;AACzC,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AACzC,OAAO,EAAE,IAAI,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAE1C,MAAM,IAAI,GAAG,OAAO,CAAC,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC;AACrD,+EAA+E;AAC/E,MAAM,SAAS,GAAG,IAAI,CAAC,IAAI,EAAE,IAAI,EAAE,IAAI,EAAE,IAAI,EAAE,cAAc,EAAE,OAAO,EAAE,uBAAuB,CAAC,CAAC;AAEjG,mFAAmF;AACnF,mEAAmE;AACnE,MAAM,aAAa,GAAG,kEAAkE,CAAC;AAEzF,QAAQ,CAAC,qFAAqF,EAAE,GAAG,EAAE;IACnG,EAAE,CAAC,4EAA4E,EAAE,GAAG,EAAE;QACpF,MAAM,KAAK,GAAG,YAAY,CAAC,SAAS,CAAC,CAAC;QACtC,MAAM,MAAM,GAAG,UAAU,CAAC,QAAQ,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC;QAChE,MAAM,CAAC,MAAM,CAAC,CAAC,IAAI,CAAC,aAAa,CAAC,CAAC;IACrC,CAAC,CAAC,CAAC;AACL,CAAC,CAAC,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@memnexus-ai/mx-agent-cli",
-  "version": "0.1.181",
+  "version": "0.1.182",
   "description": "CLI for creating and managing AI agent teams",
   "type": "module",
   "bin": {