heyspex 0.1.0 → 0.2.1

package/vendor/heyspex-mcp/package-root.mjs

@@ -0,0 +1,32 @@
+/**
+ * package-root.mjs — the ONE place this package derives its own install
+ * location from `import.meta.url`.
+ *
+ * WHY IT IS ITS OWN MODULE: the console's remote MCP endpoint
+ * (`POST /api/mcp`, WP6) runs this whole module graph through webpack, and a
+ * bundler REPLACES `import.meta.url` with the absolute `file://` URL the
+ * module had ON THE BUILD MACHINE. Every module that computed its own
+ * package root therefore baked a second copy of the builder's checkout path
+ * into the serverless chunk (`file:///C:/dev-projects/heyspex-app/...`),
+ * which on Vercel resolves under `/vercel/path0` and misses at `/var/task`.
+ * Funnelling the derivation through this module leaves exactly one such
+ * literal in the bundle instead of one per consumer, and it is inert: nothing
+ * imports off it without an `existsSync` guard or a try/catch.
+ *
+ * Behaviour for the stdio server is byte-for-byte what each consumer computed
+ * inline before:
+ *   MODULE_DIR   = <install>/vendor/heyspex-mcp
+ *   PACKAGE_ROOT = <install>            (repo root in the monorepo,
+ *                                        `node_modules/heyspex` when packed)
+ *
+ * NOTE: `PACKAGE_ROOT` is never the VAULT root — see read-path.mjs's module
+ * doc for why the two must not be conflated.
+ */
+import { dirname } from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+/** Directory holding this package's MCP modules (`vendor/heyspex-mcp`). */
+export const MODULE_DIR = dirname(fileURLToPath(import.meta.url));
+
+/** This package's own install root (two levels above {@link MODULE_DIR}). */
+export const PACKAGE_ROOT = dirname(dirname(MODULE_DIR));

package/vendor/heyspex-mcp/peer-presence.mjs

@@ -223,7 +223,14 @@ export function resetPeerPresenceCache() {
   lastGoodChecked = false;
 }
 
-async function readClaimsFromConsole(consoleUrl, fetchFn, timeoutMs, headers) {
+// Exported for scripts/validate-no-foreign-session-sweep.mjs (HS-T9KQ): that
+// gate needs the RAW claims array (specId/sessionId/agent/staleAt/expiresAt),
+// not the formatted/grouped-by-session `peer_agents` block `fetchPeerAgents`
+// returns (which truncates sessionId to 8 chars and drops per-claim specId).
+// This was already the lowest-level structured fetch in this module — adding
+// `export` here changes nothing about how `resolvePeerPresence`/`fetchPeerAgents`
+// call it or what they return.
+export async function readClaimsFromConsole(consoleUrl, fetchFn, timeoutMs, headers) {
   const url = `${String(consoleUrl).replace(/\/+$/, '')}/api/claims`;
   const init = { signal: AbortSignal.timeout?.(timeoutMs) };
   // Cloud console gates /api/claims behind the same bearer every other console