@tinoy/pi-ext-lib 0.2.0 → 0.3.0

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@tinoy/pi-ext-lib",
-	"version": "0.2.0",
+	"version": "0.3.0",
 	"description": "Shared helpers for pi extensions: the hook log envelope, TUI tool headers, and the system-prompt block seam.",
 	"license": "MIT",
 	"repository": {
@@ -17,6 +17,7 @@
 		".": "./src/index.ts"
 	},
 	"files": [
+		"src/glob.ts",
 		"src/hook-log.ts",
 		"src/index.ts",
 		"src/neighbour.ts",

package/src/glob.ts

@@ -0,0 +1,24 @@
+/**
+ * glob.ts — path/glob overlap, the predicate the fleet and its claim guard must agree on.
+ *
+ * `globOverlap` answers "do these two path patterns address the same tree": an exact
+ * match, either side a directory prefix of the other, or a `*` wildcard anywhere in
+ * either side. It lives here because both extension packages that ask the question
+ * need the same answer, and a shared library is a cheaper owner than a dependency
+ * between the two packages.
+ */
+
+/** Glob/path overlap: exact, directory prefix, or '*' anywhere in either side. */
+export function globOverlap(a: string, b: string): boolean {
+	const x = a.replace(/\/+$/, "");
+	const y = b.replace(/\/+$/, "");
+	if (x === y) return true;
+	if (x.includes("*")) return new RegExp(`^${x.split("*").map(escapeRe).join(".*")}$`).test(y);
+	if (y.includes("*")) return new RegExp(`^${y.split("*").map(escapeRe).join(".*")}$`).test(x);
+	return x.startsWith(`${y}/`) || y.startsWith(`${x}/`);
+}
+
+/** Escape every RegExp metacharacter in `s`, so it can be embedded in a pattern. */
+export function escapeRe(s: string): string {
+	return s.replace(/[.*+?^${}()|[\]\\]/g, "\\$&");
+}

package/src/index.ts

@@ -9,6 +9,7 @@
  * each was already in the tree, so the copy is the one canonical file for any
  * package that depends on this one.
  */
+export { escapeRe, globOverlap } from "./glob.ts";
 export { HOOK_LOG_PATH, hookLog } from "./hook-log.ts";
 export { type NeighbourReport, optionalNeighbour } from "./neighbour.ts";
 export {

package/src/tool-header.ts

@@ -4,7 +4,7 @@
  * pi bundles its TUI inside the agent and does not expose `@earendil-works/pi-tui`
  * to extensions, so a header cannot be a `Text`; it must be a duck-typed
  * component (`render(width)` + `invalidate()`), the shape
- * extensions/deepseek-cost.ts uses for its entry renderer.
+ * the deepseek-cost entry uses for its entry renderer.
  *
  * A header is ONE line: the tool name plus the few fields a reader needs to
  * follow the transcript. Free text is flattened and clipped before theming, so