@tryglen/pi 0.6.0 → 0.6.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tryglen/pi",
-  "version": "0.6.0",
+  "version": "0.6.3",
   "description": "Shared team memory for coding agents — automatic recall and capture on every turn via the glen CLI.",
   "keywords": [
     "pi-package",
@@ -31,6 +31,7 @@
     "access": "public"
   },
   "scripts": {
+    "prepublishOnly": "echo 'Do not publish from this folder. pi-publish.yml packs, checks and publishes the tarball.' && exit 1",
     "typecheck": "tsc --noEmit",
     "test": "vitest run"
   },

package/skills/code-search/SKILL.md

@@ -5,7 +5,7 @@ description: Trace a specific piece of code to the agent conversations that prod
 
 Resolve the file and line range the user is asking about, then run
 `glen code-search <path:start-end> "<the user's question>"` via Bash — e.g.
-`glen code-search src/server/api/foo.ts:40-85 "why is this rate-limited?"`.
+`glen code-search src/api/rate-limit.ts:40-85 "why is this rate-limited?"`.
 
 The output is the ranked memory plus the full transcripts of the conversations
 behind the commits that last touched those lines. Answer from those transcripts —

package/skills/invite/SKILL.md

@@ -16,12 +16,6 @@ lands in the pool. When the user wants to bring someone in:
    - `· <email> is already a member`: nothing to do.
    - `warning: could not invite <email> (<reason>)`: relay the reason.
 
-Or share a link instead of emailing: run `glen invite` with NO email to print a
-shareable join link for the org. Anyone who signs in with a verified email on the
-org's work-email domain joins automatically — good for dropping in a team channel.
-(Requires "Let teammates join with their work email" to be enabled in
-Settings → General.)
-
 Notes:
 - Invites are sent by email and expire after 48 hours; the teammate clicks the
   link, signs in, and lands directly in the shared memory.

package/src/_utils/parse-hook-output.ts

@@ -1,3 +1,5 @@
+import { parseJson } from "./parse-json";
+
 // A hook prints either the JSON envelope or plain text meant as context.
 export const parseHookOutput = (
   raw: string,
@@ -17,11 +19,3 @@ export const parseHookOutput = (
     notice: typeof notice === "string" ? notice : "",
   };
 };
-
-const parseJson = (text: string): unknown => {
-  try {
-    return JSON.parse(text) as unknown;
-  } catch {
-    return undefined;
-  }
-};

package/src/_utils/parse-json.ts

@@ -0,0 +1,8 @@
+// Bad JSON comes back as undefined: JSON.parse can only report it by throwing.
+export const parseJson = (text: string): unknown => {
+  try {
+    return JSON.parse(text) as unknown;
+  } catch {
+    return undefined;
+  }
+};

package/src/_utils/run-glen-hook.ts

@@ -17,7 +17,8 @@ export const runGlenHook = (
     const chunks: Buffer[] = [];
     const timer = setTimeout(() => child.kill("SIGKILL"), timeoutMs);
     child.stdout.on("data", (chunk: Buffer) => chunks.push(chunk));
-    child.stdin.on("error", () => {});
+    // A glen that exits before reading its payload makes this write fail (EPIPE); close still resolves.
+    child.stdin.on("error", () => undefined);
     child.on("error", (error: NodeJS.ErrnoException) => {
       clearTimeout(timer);
       resolve({ kind: error.code === "ENOENT" ? "missing" : "failed" });