pi-tool-discipline 0.1.6 → 0.1.8

package/README.md

@@ -21,20 +21,23 @@ tool, not bash").
 
 Two mechanisms, applied automatically in every session:
 
-1. **Search-tool registration (root fix).** Registers tools named `grep`,
-   `find`, and `ls` (skipped if already registered). Their presence flips pi's
-   `hasGrep`/`hasFind`/`hasLs` check, so the conflicting bash guideline is
-   **never generated**. Each tool always has a working fs-based implementation
-   (`extensions/search.ts`); visibility is toggled per capability — hidden
-   while its FFF counterpart (`ffgrep`/`fffind`) is active, visible as a
-   fallback when pi-fff is not installed.
-2. **System-prompt injection (fallback + rules).** On every agent start,
-   appends an idempotent "Tool Discipline" section to the system prompt:
-   content search with `ffgrep`, path search with `fffind`, file reads with
-   `read` (offset/limit), no bash `grep`/`rg`/`find`/`ls`/`cat`/`sed`/`head`/
-   `tail`/`which` for searching, bash reserved for pipelines/git/npm/network,
-   `rg` (never `grep`) as the last resort. Also strips the default bash
-   guideline text in environments where the registration is disabled.
+1. **Activate search tools (root fix).** pi 0.84+ ships real `grep` / `find` /
+   `ls` built-in tool definitions but only activates `read`/`bash`/`edit`/
+   `write` by default. This extension activates the built-ins, so pi's
+   `hasGrep`/`hasFind`/`hasLs` check passes and the conflicting
+   `Use bash for file operations like ls, rg, find` guideline is **never
+   generated** — the model is never told to use bash for searching. On older
+   pi versions without these built-ins, fs-based fallbacks
+   (`extensions/search.ts`) are registered instead, with their text snippet
+   suppressed while `ffgrep`/`fffind` from pi-fff are active (the registered
+   tool schema remains present either way).
+2. **System-prompt injection (rules).** On every agent start, appends an
+   idempotent "Tool Discipline" section to the system prompt: content search
+   with `ffgrep`, path search with `fffind`, file reads with `read`
+   (offset/limit), no bash `grep`/`rg`/`find`/`ls`/`cat`/`sed`/`head`/`tail`/
+   `which` for searching, bash reserved for pipelines/git/npm/network, `rg`
+   (never `grep`) as the last resort. Also strips the bash guideline text as
+   a belt-and-suspenders fallback.
 
 ## Install
 
@@ -44,8 +47,9 @@ pi install npm:pi-tool-discipline
 pi -e npm:pi-tool-discipline
 ```
 
-Requires `@ff-labs/pi-fff` (or any other extension providing `ffgrep`/`fffind`)
-for the discipline to point at real search tools.
+Requires nothing extra. With `@ff-labs/pi-fff` installed, the model prefers
+`ffgrep`/`fffind`; without it, Pi's built-in `grep`/`find`/`ls` tools (activated
+by this extension, or fs-based fallbacks on older pi versions) are used.
 
 ## Verify
 
@@ -58,10 +62,21 @@ You can also inspect the system prompt: the string
 
 ## Security
 
-This extension runs with full system access like any pi extension. It only
-registers inert placeholder tools and appends text to the system prompt; it
-does not execute commands, read files, or touch network. Review the source in
-`extensions/index.ts` before installing.
+This extension runs with full system access like any pi extension. What it does:
+- Activates pi's built-in `grep`/`find`/`ls` tools (read-only file search).
+- Injects text into the system prompt (discipline rules).
+- On pi versions without built-in search tools, registers read-only fs-based
+  fallback implementations that read file contents under the searched path.
+
+**Disclosure:** pi's built-in `grep`/`find` tools execute the `rg`/`fd`
+binaries, and pi may auto-download those binaries from GitHub on first use
+(`ensureTool`). This extension itself does not execute commands, write files,
+or touch the network — that claim covers only its own fs-based fallback
+implementations, not the pi built-ins it activates.
+
+The fallback search tools only read. Note that any installed tool, including
+this one, can be invoked by the model. Review the source in `extensions/`
+before installing.
 
 ## License
 

package/extensions/index.ts

@@ -13,12 +13,14 @@
  *   rules that say to use the grep tool instead.
  *
  * How it works:
- *   A. Registers working search tools named `grep` / `find` / `ls` (skipped
- *      when already registered). Their presence flips pi's hasGrep/hasFind/
- *      hasLs check, so the conflicting bash guideline is never generated.
- *      Each tool is always functional (fs-based, see search.ts); visibility
- *      is toggled via promptSnippet — hidden while its FFF counterpart
- *      (ffgrep / fffind) is active, visible as a fallback when it is not.
+ *   A. Ensures `grep` / `find` / `ls` tools are ACTIVE in the session. pi 0.84+
+ *      ships real built-in definitions (createAllToolDefinitions) but only
+ *      activates read/bash/edit/write by default — this extension activates
+ *      the built-ins, so pi's hasGrep/hasFind/hasLs check passes and the
+ *      conflicting bash guideline is never generated, and the model always has
+ *      search tools. On older pi versions without the built-ins, fs-based
+ *      fallbacks (search.ts) are registered instead (visible only when the
+ *      FFF counterpart ffgrep/fffind is absent).
  *   B. On before_agent_start, appends the tool-discipline rules to the system
  *      prompt (idempotent) and strips the bash guideline text as a fallback.
  */
@@ -35,24 +37,14 @@ const PLACEHOLDER_NAMES = ["grep", "find", "ls"] as const;
 /** FFF search tools that indicate pi-fff (or equivalent) is installed. */
 const FFF_TOOLS = ["ffgrep", "fffind"];
 
-/**
- * The exact guidelines pi's builder injects when no search tool is active.
- * Stripped from the system prompt as a fallback (plan B).
- */
-const BASH_GUIDELINES = [
-	"Use bash for file operations like ls, rg, find",
-	"Use bash or PowerShell for file operations like listing, searching, and finding files",
-	"Use PowerShell for file operations like listing, searching, and finding files",
-];
-
 const DISCIPLINE = `
 ## Tool Discipline (pi-tool-discipline)
 
 Search tool priority:
 
 1. ffgrep / fffind (from @ff-labs/pi-fff) — always preferred. They work with absolute paths outside the workspace and support regex / path / exclude filters.
-2. Without pi-fff, use the grep / find / ls TOOLS (fallbacks provided by this extension). If a search seems to miss something, adjust its parameters (path, caseSensitive, maxResults) — never fall back to bash's grep or find.
-3. Never run bash \`grep\` or \`find\`. Never use bash \`ls\`/\`cat\`/\`head\`/\`tail\`/\`sed\`/\`which\` directly for searching or reading — use ffgrep / fffind / read (or the grep/find/ls fallback tools) instead.
+2. Without pi-fff, use the grep / find / ls TOOLS (Pi built-ins on pi 0.84+, fs fallbacks on older versions). Fill their parameters according to each tool's declared schema — built-in grep uses ignoreCase/limit, built-in find uses a glob pattern. Never fall back to bash's grep or find.
+3. Never run bash \`grep\` or \`find\`. Never use bash \`ls\`/\`cat\`/\`head\`/\`tail\`/\`sed\`/\`which\` directly for searching or reading — use ffgrep / fffind / read (or the grep/find/ls tools) instead.
 4. Read files with \`read\` (offset/limit for large files).
 5. Bash stays allowed only when dedicated tools cannot do the job: pipelines, git, npm, running programs, network requests, file mutations.
 6. If bash searching is truly unavoidable, use \`rg\` (never \`grep\`).`;
@@ -62,7 +54,7 @@ interface FallbackTool {
 	description: string;
 	snippet: string;
 	parameters: ReturnType<typeof Type.Object>;
-	execute: (params: any, cwd: string) => string;
+	execute: (params: any, cwd: string, signal?: AbortSignal) => Promise<string>;
 }
 
 const FALLBACK_TOOLS: Record<string, FallbackTool> = {
@@ -72,7 +64,7 @@ const FALLBACK_TOOLS: Record<string, FallbackTool> = {
 			"Search file contents for a text pattern. Fallback for environments without ffgrep; prefer ffgrep when available.",
 		snippet: "Search file contents (fallback when ffgrep is unavailable)",
 		parameters: grepSchema,
-		execute: (params, cwd) => grepFiles({ ...params, cwd }),
+		execute: async (params, cwd, signal) => grepFiles({ ...params, cwd, signal }),
 	},
 	find: {
 		label: "find (fallback)",
@@ -80,7 +72,7 @@ const FALLBACK_TOOLS: Record<string, FallbackTool> = {
 			"Find files by path/name substring. Fallback for environments without fffind; prefer fffind when available.",
 		snippet: "Find files by path/name (fallback when fffind is unavailable)",
 		parameters: findSchema,
-		execute: (params, cwd) => findFiles({ ...params, cwd }),
+		execute: async (params, cwd, signal) => findFiles({ ...params, cwd, signal }),
 	},
 	ls: {
 		label: "ls (fallback)",
@@ -88,16 +80,27 @@ const FALLBACK_TOOLS: Record<string, FallbackTool> = {
 			"List directory entries. Fallback for environments without fffind; prefer fffind when available.",
 		snippet: "List directory entries (fallback when fffind is unavailable)",
 		parameters: lsSchema,
-		execute: (params, cwd) => listDir({ ...params, cwd }),
+		execute: async (params, cwd) => listDir({ ...params, cwd }),
 	},
 };
 
+/**
+ * Strip only the exact generated guideline bullets (with the "- " prefix), so
+ * quoted references inside project instructions or custom prompts are not
+ * rewritten. Activation normally prevents pi from generating these anyway;
+ * this is a belt-and-suspenders fallback.
+ */
 function stripBashGuidelines(prompt: string): string {
-	let out = prompt;
-	for (const guideline of BASH_GUIDELINES) {
-		out = out.replaceAll(guideline, "Use ffgrep/fffind for file operations like ls, rg, find");
-	}
-	return out;
+	return prompt
+		.replace("- Use bash for file operations like ls, rg, find", "- Use ffgrep/fffind for file operations like ls, rg, find")
+		.replace(
+			"- Use bash or PowerShell for file operations like listing, searching, and finding files",
+			"- Use ffgrep/fffind for file operations like listing, searching, and finding files",
+		)
+		.replace(
+			"- Use PowerShell for file operations like listing, searching, and finding files",
+			"- Use ffgrep/fffind for file operations like listing, searching, and finding files",
+		);
 }
 
 export default function toolDiscipline(pi: ExtensionAPI) {
@@ -105,23 +108,29 @@ export default function toolDiscipline(pi: ExtensionAPI) {
 	// Done in session_start: action methods (getAllTools/registerTool) are not
 	// available during extension loading, and tools registered here are
 	// refreshed into the session (and system prompt) immediately.
-	pi.on("session_start", (event, ctx) => {
+	pi.on("session_start", () => {
 		const all = new Set(pi.getAllTools().map((t) => t.name));
-		// Use ACTIVE tools (respects --exclude-tools / allowed lists), not the
-		// full registry: getAllTools() still reports excluded tools.
 		const active = new Set(pi.getActiveTools());
-		// Decide per capability so partial FFF availability (e.g. only ffgrep
-		// active) still leaves a real fallback for the missing side.
 		const hasFfgrep = active.has("ffgrep");
 		const hasFffind = active.has("fffind");
+
+		// 1) Activate built-in grep/find/ls when they exist (pi 0.84+ ships real
+		//    definitions via createAllToolDefinitions but only activates
+		//    read/bash/edit/write by default). Activating them flips
+		//    hasGrep/hasFind/hasLs so the bash guideline is never generated, and
+		//    gives the model real built-in search tools.
+		const toActivate = PLACEHOLDER_NAMES.filter((name) => all.has(name) && !active.has(name));
+		if (toActivate.length > 0) {
+			// setActiveTools rebuilds the system prompt immediately.
+			pi.setActiveTools([...active, ...toActivate]);
+		}
+
+		// 2) Older pi without built-in grep/find/ls: register working fs-based
+		//    fallbacks (search.ts). Visibility is per-capability: hidden while
+		//    the FFF counterpart is active, visible when it is not.
 		let registeredAny = false;
-		// All three names always get a WORKING implementation (no inert
-		// placeholders — a refreshed tool can be called by the model, so an
-		// empty implementation would be a trap). Visibility toggles via
-		// promptSnippet: hidden when the FFF counterpart is active, visible
-		// (with a fallback hint) when it is not.
 		const registerSearchTool = (name: string, fffActive: boolean) => {
-			if (all.has(name)) return; // already registered by another extension
+			if (all.has(name)) return; // built-in exists — handled above
 			const fallback = FALLBACK_TOOLS[name];
 			pi.registerTool({
 				name,
@@ -132,8 +141,8 @@ export default function toolDiscipline(pi: ExtensionAPI) {
 					"Use ffgrep/fffind when they are available; grep/find/ls are fallbacks only for environments without pi-fff.",
 				],
 				parameters: fallback.parameters,
-				async execute(_toolCallId, params, _signal, _onUpdate, execCtx) {
-					const text = fallback.execute(params ?? {}, execCtx.cwd);
+				async execute(_toolCallId, params, signal, _onUpdate, execCtx) {
+					const text = await fallback.execute(params ?? {}, execCtx.cwd, signal);
 					return {
 						content: [{ type: "text", text }],
 						details: { fallback: true },
@@ -146,10 +155,9 @@ export default function toolDiscipline(pi: ExtensionAPI) {
 		registerSearchTool("find", hasFffind);
 		registerSearchTool("ls", hasFffind);
 		// Tools registered in session_start do not enter selectedTools until the
-		// registry is refreshed. Without this, pi keeps injecting the bash
-		// guideline (verified empirically on pi 0.84.4). refreshTools exists at
-		// runtime (ExtensionActions) but is not declared on ExtensionAPI's type.
-		// Known limitation: with peer version "*", other pi versions may differ.
+		// registry is refreshed. refreshTools exists at runtime (ExtensionActions)
+		// but is not declared on ExtensionAPI's type. Known limitation: with peer
+		// version "*", other pi versions may differ.
 		if (registeredAny) (pi as unknown as { refreshTools: () => void }).refreshTools();
 	});
 
@@ -161,7 +169,7 @@ export default function toolDiscipline(pi: ExtensionAPI) {
 		return { systemPrompt: `${prompt}\n${MARK}\n${DISCIPLINE}` };
 	});
 
-	// Status command: /tool-discipline — verify tool registration and injection.
+	// Status command: /tool-discipline — verify tool activation and injection.
 	pi.registerCommand("tool-discipline", {
 		description: "Show pi-tool-discipline status (tools + injected guideline)",
 		handler: async (_args, ctx) => {
@@ -169,13 +177,13 @@ export default function toolDiscipline(pi: ExtensionAPI) {
 			const active = new Set(pi.getActiveTools());
 			const fff = FFF_TOOLS.filter((name) => active.has(name));
 			const registered = PLACEHOLDER_NAMES.filter((n) => all.has(n));
-			const visible = PLACEHOLDER_NAMES.filter((n) => active.has(n));
+			const activeTools = PLACEHOLDER_NAMES.filter((n) => active.has(n));
 			const injected = ctx.getSystemPrompt().includes(MARK);
 			ctx.ui.notify(
 				`pi-tool-discipline\n` +
 					`fff active: ${fff.length > 0 ? fff.join(", ") : "(none)"}\n` +
-					`grep/find/ls registered: ${registered.length > 0 ? registered.join(", ") : "(none)"}\n` +
-					`visible to model: ${visible.length > 0 ? visible.join(", ") : "(none)"}\n` +
+					`grep/find/ls defined: ${registered.length > 0 ? registered.join(", ") : "(none)"}\n` +
+					`grep/find/ls active: ${activeTools.length > 0 ? activeTools.join(", ") : "(none)"}\n` +
 					`discipline injected: ${injected ? "yes" : "no"}`,
 				"info",
 			);

package/extensions/search.ts

@@ -1,15 +1,18 @@
 /**
  * Fallback search implementations for environments without @ff-labs/pi-fff.
- * Pure Node fs-based; no shell, no external deps.
+ * Pure Node fs-based (async, abort-aware); no shell, no external deps.
  */
-import { readdirSync, readFileSync, statSync, lstatSync } from "fs";
+import { readdir, readFile, stat, lstat } from "fs/promises";
 import { join, resolve, relative } from "path";
 import { Type } from "typebox";
 
 const SKIP_DIRS = new Set(["node_modules", ".git", ".hg", ".svn"]);
 const MAX_FILES = 2000;
+const MAX_VISITED = 5000; // total entries touched, bounds slow/odd trees
 const MAX_FILE_BYTES = 1024 * 1024; // content search skips files larger than 1 MiB
 const MAX_OUTPUT_BYTES = 50 * 1024;
+const TRUNCATE_MARKER = "\n[output truncated]";
+const CAPPED_MARKER = "\n[search capped — traversal stopped early]";
 
 interface FileMatch {
 	file: string;
@@ -17,66 +20,102 @@ interface FileMatch {
 	text: string;
 }
 
+interface WalkState {
+	visited: number;
+	capped: boolean;
+}
+
 /**
- * Collect files under dir (depth-limited, symlink-safe, bounded).
- * Does NOT filter by size — path search must find large files too.
+ * Collect regular files under dir (depth-limited, symlink-safe, bounded,
+ * abort-aware). Only isFile() entries are collected — FIFOs, devices, sockets
+ * would block a read. Individual OS filesystem requests may still be
+ * uninterruptible, but traversal checks the signal between operations.
  */
-function walk(dir: string, out: string[], depth = 0): void {
-	if (depth > 12) return;
+async function walk(dir: string, out: string[], state: WalkState, signal?: AbortSignal, depth = 0): Promise<void> {
+	if (depth > 12 || state.visited >= MAX_VISITED) {
+		state.capped = true;
+		return;
+	}
 	let entries: string[];
 	try {
-		entries = readdirSync(dir);
+		entries = await readdir(dir);
 	} catch {
 		return;
 	}
 	for (const entry of entries) {
-		if (out.length >= MAX_FILES) return; // enforce limit inside the loop
+		if (signal?.aborted) {
+			state.capped = true;
+			return;
+		}
+		if (out.length >= MAX_FILES || state.visited >= MAX_VISITED) {
+			state.capped = true;
+			return; // in-loop bound
+		}
 		if (entry.startsWith(".") || SKIP_DIRS.has(entry)) continue;
 		const p = join(dir, entry);
+		state.visited++;
 		try {
-			const lst = lstatSync(p);
+			const lst = await lstat(p);
 			if (lst.isSymbolicLink()) continue; // never follow symlinks
-			if (lst.isDirectory()) walk(p, out, depth + 1);
-			else out.push(p);
+			if (lst.isDirectory()) await walk(p, out, state, signal, depth + 1);
+			else if (lst.isFile()) out.push(p); // regular files only
 		} catch {
 			// unreadable entries are skipped
 		}
 	}
 }
 
-/** Truncate by BYTE length (not UTF-16 chars), keeping complete lines. */
+/** Truncate by BYTE length, keep complete lines, reserve space for the marker. */
 function truncate(text: string, maxBytes = MAX_OUTPUT_BYTES): string {
 	const buf = Buffer.from(text, "utf8");
-	if (buf.length <= maxBytes) return text;
-	const cut = buf.subarray(0, maxBytes).toString("utf8");
+	const budget = maxBytes - Buffer.byteLength(TRUNCATE_MARKER);
+	if (buf.length <= budget) return text;
+	const cut = buf.subarray(0, budget).toString("utf8");
 	const lastNewline = cut.lastIndexOf("\n");
-	const base = lastNewline > 0 ? cut.slice(0, lastNewline) : cut;
-	return `${base}\n[output truncated]`;
+	if (lastNewline <= 0) return TRUNCATE_MARKER.trim(); // nothing complete fits
+	return `${cut.slice(0, lastNewline)}\n${TRUNCATE_MARKER}`;
 }
 
-export function grepFiles(opts: {
+async function resolveRoot(cwd: string, sub?: string): Promise<string | null> {
+	const root = resolve(cwd, sub || ".");
+	try {
+		const st = await stat(root);
+		return st.isDirectory() ? root : null;
+	} catch {
+		return null;
+	}
+}
+
+export async function grepFiles(opts: {
 	pattern: string;
 	path?: string;
 	caseSensitive?: boolean;
 	maxResults?: number;
 	cwd: string;
-}): string {
-	const root = resolve(opts.cwd, opts.path || ".");
+	signal?: AbortSignal;
+}): Promise<string> {
+	const root = await resolveRoot(opts.cwd, opts.path);
+	if (!root) return `Error: search path not found: ${resolve(opts.cwd, opts.path || ".")}`;
 	const pattern = opts.caseSensitive ? opts.pattern : opts.pattern.toLowerCase();
 	const limit = opts.maxResults ?? 100;
 	const files: string[] = [];
-	walk(root, files);
+	const state: WalkState = { visited: 0, capped: false };
+	await walk(root, files, state, opts.signal);
 	const matches: FileMatch[] = [];
 	for (const file of files) {
+		if (opts.signal?.aborted) {
+			state.capped = true;
+			break;
+		}
 		if (matches.length >= limit) break;
 		try {
-			if (statSync(file).size > MAX_FILE_BYTES) continue; // cap only before reading content
+			if ((await stat(file)).size > MAX_FILE_BYTES) continue; // cap only before reading content
 		} catch {
 			continue;
 		}
 		let content: string;
 		try {
-			content = readFileSync(file, "utf8");
+			content = await readFile(file, "utf8");
 		} catch {
 			continue;
 		}
@@ -89,31 +128,45 @@ export function grepFiles(opts: {
 			}
 		}
 	}
-	if (matches.length === 0) return "No matches found";
+	if (matches.length === 0) return state.capped ? `No matches found${CAPPED_MARKER}` : "No matches found";
 	let out = "";
 	for (const m of matches) out += `${m.file}:${m.line}: ${m.text}\n`;
-	return truncate(out);
+	out = truncate(out);
+	return state.capped ? `${out}${CAPPED_MARKER}` : out;
 }
 
-export function findFiles(opts: { pattern?: string; path?: string; maxResults?: number; cwd: string }): string {
-	const root = resolve(opts.cwd, opts.path || ".");
+export async function findFiles(opts: {
+	pattern?: string;
+	path?: string;
+	maxResults?: number;
+	cwd: string;
+	signal?: AbortSignal;
+}): Promise<string> {
+	const root = await resolveRoot(opts.cwd, opts.path);
+	if (!root) return `Error: search path not found: ${resolve(opts.cwd, opts.path || ".")}`;
 	const files: string[] = [];
-	walk(root, files);
+	const state: WalkState = { visited: 0, capped: false };
+	await walk(root, files, state, opts.signal);
 	const needle = opts.pattern?.toLowerCase();
 	// Match against the RELATIVE path so a pattern matching an ancestor
 	// directory does not hit every file, and rendered output stays relative.
 	const rel = files.map((f) => relative(root, f));
 	const hits = needle ? rel.filter((r) => r.toLowerCase().includes(needle)) : rel;
-	if (hits.length === 0) return "No matching files found";
-	return truncate(hits.slice(0, opts.maxResults ?? 100).join("\n"));
+	if (hits.length === 0) return state.capped ? `No matching files found${CAPPED_MARKER}` : "No matching files found";
+	let out = truncate(hits.slice(0, opts.maxResults ?? 100).join("\n"));
+	if (state.capped) out += CAPPED_MARKER;
+	return out;
 }
 
-export function listDir(opts: { path?: string; cwd: string }): string {
-	const dir = resolve(opts.cwd, opts.path || ".");
+export async function listDir(opts: { path?: string; cwd: string }): Promise<string> {
+	const root = await resolveRoot(opts.cwd, opts.path);
+	if (!root) return `Error: directory not found: ${resolve(opts.cwd, opts.path || ".")}`;
 	try {
-		return truncate(readdirSync(dir).join("\n"));
+		const entries = await readdir(root);
+		if (entries.length === 0) return "(empty directory)";
+		return truncate(entries.join("\n"));
 	} catch (error: any) {
-		return `Error listing ${dir}: ${error.message}`;
+		return `Error listing ${root}: ${error.message}`;
 	}
 }
 
@@ -121,13 +174,13 @@ export const grepSchema = Type.Object({
 	pattern: Type.String({ description: "Text to search for in file contents" }),
 	path: Type.Optional(Type.String({ description: "Directory to search (defaults to cwd)" })),
 	caseSensitive: Type.Optional(Type.Boolean({ description: "Case-sensitive match (default false)" })),
-	maxResults: Type.Optional(Type.Number({ description: "Max matches (default 100)" })),
+	maxResults: Type.Optional(Type.Integer({ minimum: 1, description: "Max matches (default 100)" })),
 });
 
 export const findSchema = Type.Object({
 	pattern: Type.Optional(Type.String({ description: "Substring to match in file path or name (empty lists all)" })),
 	path: Type.Optional(Type.String({ description: "Directory to search (defaults to cwd)" })),
-	maxResults: Type.Optional(Type.Number({ description: "Max results (default 100)" })),
+	maxResults: Type.Optional(Type.Integer({ minimum: 1, description: "Max results (default 100)" })),
 });
 
 export const lsSchema = Type.Object({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-tool-discipline",
-  "version": "0.1.6",
+  "version": "0.1.8",
   "description": "pi extension: enforce ffgrep/fffind-first search discipline and neutralize the default bash file-operation guideline",
   "type": "module",
   "license": "MIT",
@@ -41,12 +41,12 @@
   },
   "peerDependencies": {
     "@earendil-works/pi-coding-agent": "*",
-    "@sinclair/typebox": "*"
+    "typebox": "*"
   },
   "devDependencies": {
     "@earendil-works/pi-coding-agent": "*",
-    "@sinclair/typebox": "*",
     "@types/node": "^22.0.0",
+    "typebox": "*",
     "typescript": "^5.0.0"
   }
 }