@heyhuynhgiabuu/pi-pretty 0.6.4 → 0.6.6

package/pi-pretty.example.json

@@ -1,6 +0,0 @@
-{
-	"background": {
-		"tool": "#1e1e2e",
-		"error": "#2a1e1e"
-	}
-}

package/release-notes/v0.3.2.md

@@ -1,34 +0,0 @@
-# pi-pretty v0.3.2
-
-## Summary
-This patch release fixes inline image rendering reliability when running `pi-pretty` inside `tmux`.
-
-## What changed
-- Fixed terminal detection in tmux for:
-  - Kitty (`KITTY_WINDOW_ID`, `KITTY_PID`)
-  - WezTerm (`WEZTERM_EXECUTABLE`, `WEZTERM_CONFIG_DIR`, `WEZTERM_CONFIG_FILE`)
-- Added tmux fallback detection via:
-  - `tmux display-message -p "#{client_termname}"`
-- Replaced static tmux detection with runtime detection to avoid stale module-load state.
-- Added explicit warning when tmux passthrough is disabled:
-  - `tmux allow-passthrough is off. Run: tmux set -g allow-passthrough on`
-- Added non-PNG warning for Kitty/Ghostty image rendering path.
-- Added test coverage for image protocol detection and tmux passthrough warning behavior.
-- Updated README with tmux passthrough setup instructions.
-
-## Files
-- `src/index.ts`
-- `test/image-rendering.test.ts`
-- `README.md`
-
-## Verification
-- `npm run typecheck` ✅
-- `npm test` ✅ (46 tests)
-- `npm run lint` ⚠️ fails due to existing Biome diagnostics in legacy code paths (pre-existing, not introduced in this patch).
-
-## Upgrade notes
-When using `tmux`, enable passthrough:
-
-```tmux
-set -g allow-passthrough on
-```

package/release-notes/v0.3.3.md

@@ -1,48 +0,0 @@
-# pi-pretty v0.3.3
-
-## Summary
-This patch release combines the recent rendering and FFF-path fixes into a single `v0.3.3` release.
-
-## What changed
-- Fixed themed tool background rendering so `toolSuccessBg` and `toolErrorBg` fill the full rendered width for core tool output.
-- Preserved the active tool background across ANSI reset sequences to avoid broken background bands inside highlighted output.
-- Kept error rendering on `theme.fg("error", ...)` while switching error panels to `toolErrorBg`.
-- Moved pi-pretty FFF data from:
-  - `~/.pi/agent/fff`
-- To:
-  - `~/.pi/agent/pi-pretty/fff`
-- Added a helper to resolve the pi-pretty-specific FFF directory under `getAgentDir()`.
-- Updated README to document the pi-pretty-owned FFF data location.
-- Added a test that verifies the generated frecency/history DB paths use the new per-extension location.
-
-## Files
-- `src/index.ts`
-- `test/fff-integration.test.ts`
-- `README.md`
-- `package.json`
-- `package-lock.json`
-
-## Verification
-- `npm run typecheck` ✅
-- `npm test` ✅ (47 tests)
-- `npm run lint` ⚠️ still reports pre-existing Biome diagnostics in legacy code paths; no new release-blocking failure was introduced for this patch.
-
-## Upgrade notes
-If your Pi theme defines:
-
-```json
-{
-  "toolSuccessBg": "#1e2e1e",
-  "toolErrorBg": "#2e1e1e"
-}
-```
-
-core tool panels now render those backgrounds across the full line width instead of only behind printed characters.
-
-When FFF is available, pi-pretty now stores frecency/history data under:
-
-```text
-~/.pi/agent/pi-pretty/fff/
-```
-
-Existing data under `~/.pi/agent/fff` is not migrated automatically by this release.

package/release-notes/v0.4.0.md

@@ -1,58 +0,0 @@
-# pi-pretty v0.4.0
-
-## Summary
-This release makes bundled FFF search the primary product direction for `pi-pretty`.
-
-`pi-pretty` now owns the built-in `find` / `grep` experience directly via `@ff-labs/fff-node`, includes `multi_grep`, and documents the bundled workflow end-to-end.
-
-## What changed
-- Bundled `@ff-labs/fff-node` as a normal dependency instead of an optional coexistence path.
-- Restored bundled FFF-backed behavior for:
-  - `find`
-  - `grep`
-  - `multi_grep`
-  - `/fff-health`
-  - `/fff-rescan`
-- Kept the pi-pretty-specific FFF data directory:
-  - `~/.pi/agent/pi-pretty/fff/`
-- Updated README to document:
-  - bundled FFF ownership
-  - install/use flow
-  - `multi_grep` examples
-  - FFF maintenance commands
-  - the requirement not to co-load `pi-fff`
-- Tightened FFF/runtime typing:
-  - typed `CursorStore` and `fffFormatGrepText()` against `@ff-labs/fff-node`
-  - replaced remaining `src/index.ts` explicit `any` usage in tool wrappers with SDK/FFF-backed types
-  - typed `find`, `grep`, and `multi_grep` params/results/render paths against Pi tool inputs and FFF result interfaces
-  - removed several dead imports/constants and a non-null assertion in renderer code
-
-## Files
-- `src/index.ts`
-- `src/fff-helpers.ts`
-- `test/fff-integration.test.ts`
-- `test/image-rendering.test.ts`
-- `README.md`
-- `package.json`
-- `package-lock.json`
-
-## Verification
-- `npm run typecheck` ✅
-- `npm test` ✅ (47 tests)
-- `npm run lint -- --max-diagnostics=120` ✅
-- `rg "\\bany\\b" src/index.ts src/fff-helpers.ts` ✅ no matches
-
-## Upgrade notes
-- Use only `pi-pretty` for bundled FFF mode:
-
-```bash
-pi install npm:@heyhuynhgiabuu/pi-pretty
-```
-
-- Do **not** also load `pi-fff` in the same Pi setup.
-- To inspect or refresh the bundled index inside Pi, use:
-
-```text
-/fff-health
-/fff-rescan
-```

package/release-notes/v0.4.1.md

@@ -1,28 +0,0 @@
-# pi-pretty v0.4.1
-
-## Summary
-This patch release prevents `grep` from aborting Pi when FFF 0.5.2 indexes Unicode filenames and the grep call includes a `path` or `glob` constraint.
-
-## What changed
-- Constrained `grep` calls now bypass native FFF and use the SDK fallback path.
-- Unconstrained `grep` still uses FFF for the fast path.
-- Added regression tests for both `path` and `glob` constrained grep bypass behavior.
-
-## Why
-`@ff-labs/fff-node@0.5.2` can panic inside native Rust constraint matching when a byte-based slice lands inside a multi-byte UTF-8 character in an indexed filename, such as an en dash (`–`). Because that panic happens across FFI, JavaScript cannot catch it; the whole `pi` process aborts.
-
-This release avoids the crash-prone native constraint path until upstream FFF ships the Unicode boundary fix.
-
-## Files
-- `src/index.ts`
-- `test/fff-integration.test.ts`
-- `package.json`
-- `package-lock.json`
-
-## Verification
-- `npm run typecheck` ✅
-- `npm run lint` ✅
-- `npm test` ✅ (48 tests)
-
-## Upgrade notes
-No configuration changes required. After updating, file- or glob-scoped `grep` calls will prefer the SDK fallback for stability; broad unconstrained grep remains FFF-backed.

package/release-notes/v0.4.2.md

@@ -1,36 +0,0 @@
-# pi-pretty 0.4.2
-
-## Summary
-This patch release merges the reviewed `customizations` PR into `main` and ships safer `multi_grep` fallback behavior, improved theme resolution, normalized output handling, and clearer bash command rendering.
-
-## What changed
-- `multi_grep` now preserves constrained searches by routing them through a dedicated ripgrep fallback instead of silently dropping complex constraints.
-- Complex constraint expressions such as `*.ts !test/` are converted into ripgrep `--glob` filters, while invalid constraint syntax now returns an error instead of being ignored.
-- Constrained `grep` safety from `0.4.1` remains intact: `path`/`glob` constrained searches still avoid native FFF.
-- pi-pretty now reads `~/.pi/agent/settings.json` theme settings by default, while `PRETTY_THEME` continues to override explicitly.
-- Expanded bash tool rendering so expanded tool calls show the full command instead of the truncated preview.
-- Normalized read/grep output handling and tightened single-line-safe FFF grep record formatting.
-- Added test coverage for bash rendering, constrained grep and multi_grep fallback behavior, CRLF handling, and ripgrep constraint preservation.
-
-## Files
-- `src/index.ts`
-- `src/fff-helpers.ts`
-- `src/multi-grep-fallback.ts`
-- `test/bash-rendering.test.ts`
-- `test/fff-integration.test.ts`
-- `README.md`
-- `package.json`
-- `package-lock.json`
-
-## Verification
-- `npm run typecheck` ✅
-- `npm run lint` ✅
-- `npm test` ✅ (67 tests)
-
-## Upgrade notes
-No configuration changes are required.
-
-After updating:
-- constrained `grep` and `multi_grep` searches prefer safe fallback paths instead of unsafe native constrained matching
-- complex `multi_grep` constraints are preserved instead of being widened silently
-- theme selection can follow Pi settings automatically unless `PRETTY_THEME` is set

package/release-notes/v0.4.4.md

@@ -1,28 +0,0 @@
-# pi-pretty 0.4.4
-
-## Summary
-This patch release fixes terminal background tearing/misaligned cells by enforcing the pi-tui line-width contract for background-filled tool output.
-
-## What changed
-- Clamp every background-filled tool line to the active terminal width before adding background padding.
-- Use `@mariozechner/pi-tui` `truncateToWidth()` and `visibleWidth()` so ANSI escapes and wide Unicode cells are measured correctly.
-- Preserve the configured tool background after ANSI reset sequences even when truncation occurs.
-- Remove the 80-column minimum width floor so narrow terminals do not receive over-wide rendered lines.
-- Replace custom read-output truncation with pi-tui's ANSI-aware truncation helper.
-- Add regression coverage for expanded ANSI tool headers, wide characters, and narrow terminal widths.
-
-## Files
-- `src/index.ts`
-- `test/bash-rendering.test.ts`
-- `package.json`
-- `package-lock.json`
-
-## Verification
-- `npm run lint` ✅
-- `npm run typecheck` ✅
-- `npm test` ✅ (69 tests)
-
-## Upgrade notes
-No configuration changes are required.
-
-This release specifically follows the pi-tui requirement that rendered component lines must not exceed the available width, preventing terminal auto-wrap artifacts in red/error and themed tool backgrounds.

package/release-notes/v0.5.3.md

@@ -1,29 +0,0 @@
-# pi-pretty 0.5.3
-
-## Summary
-This release adds user-configurable tool output backgrounds via a `pi-pretty.json` config file, replacing the previous hardcoded theme-only dependency. It also fixes error tool background misalignment where the padding area showed the wrong background color.
-
-## What changed
-- Add `pi-pretty.json` config file support (loaded from `~/.pi/agent/pi-pretty.json` alongside `settings.json`).
-- Config fields: `background.tool` (normal tool output bg, hex) and `background.error` (error tool output bg, hex, defaults to tool bg).
-- Config values take priority over theme-provided backgrounds (`toolBg` / `toolErrorBg`).
-- Add `PRETTY_CONFIG_DIR` env var to override the config directory.
-- Fix: `fillToolBackground()` now uses a per-line RST matching the line's background color, fixing a visible color seam where padding showed `BG_BASE` instead of `BG_ERROR` on error tool output.
-- Fix: `renderToolError()` restores top spacing and applies two-space left padding to every line of multi-line error output.
-- Fix: `multi_grep` error path now uses `renderToolError()` instead of raw text without background fill.
-- Add `hexToAnsiBg()` converter and `PrettyConfig` exported interface.
-- Add `pi-pretty.example.json` in the project root.
-- Update README with configuration documentation.
-
-## Files
-- `src/index.ts`
-- `pi-pretty.example.json`
-- `README.md`
-
-## Verification
-- `npm run typecheck` ✅
-- `npm run lint` ✅ (no new issues)
-- `npm test` ✅ (74 tests)
-
-## Upgrade notes
-No configuration changes are required. Existing behavior is unchanged — config is optional. To customize backgrounds, create `~/.pi/agent/pi-pretty.json` with the `background` fields.

package/test/bash-rendering.test.ts

@@ -1,269 +0,0 @@
-import { visibleWidth } from "@earendil-works/pi-tui";
-import { describe, expect, it } from "vitest";
-
-import piPrettyExtension from "../src/index.js";
-
-class MockText {
-	private text = "";
-	constructor(_text = "", _x = 0, _y = 0) {}
-	setText(value: string) {
-		this.text = value;
-	}
-	getText() {
-		return this.text;
-	}
-	render(_width: number) {
-		return this.text.split("\n");
-	}
-}
-
-const mockTheme = {
-	fg: (_key: string, text: string) => text,
-	bold: (text: string) => text,
-};
-
-const ansiMockTheme = {
-	fg: (_key: string, text: string) => `\x1b[31m${text}\x1b[0m`,
-	bold: (text: string) => `\x1b[1m${text}\x1b[22m`,
-};
-
-function mockToolFactory(exec: any) {
-	return (_cwd: string) => ({
-		name: "mock",
-		description: "mock",
-		parameters: { type: "object", properties: {} },
-		execute: exec,
-	});
-}
-
-function stripAnsi(text: string): string {
-	return text.replace(/\x1b\[[0-9;]*m/g, "");
-}
-
-function withStdoutColumns<T>(columns: number, fn: () => T): T {
-	const descriptor = Object.getOwnPropertyDescriptor(process.stdout, "columns");
-	Object.defineProperty(process.stdout, "columns", { configurable: true, value: columns });
-	try {
-		return fn();
-	} finally {
-		if (descriptor) {
-			Object.defineProperty(process.stdout, "columns", descriptor);
-		} else {
-			delete (process.stdout as NodeJS.WriteStream & { columns?: number }).columns;
-		}
-	}
-}
-
-function loadBashTool() {
-	const noopExec = async () => ({ content: [{ type: "text", text: "" }] });
-	const tools = new Map<string, any>();
-	const pi = {
-		registerTool: (tool: any) => tools.set(tool.name, tool),
-		registerCommand: () => {},
-		on: () => {},
-	};
-
-	piPrettyExtension(pi, {
-		sdk: {
-			createReadToolDefinition: mockToolFactory(noopExec),
-			createBashToolDefinition: mockToolFactory(noopExec),
-			createLsToolDefinition: mockToolFactory(noopExec),
-			createFindToolDefinition: mockToolFactory(noopExec),
-			createGrepToolDefinition: mockToolFactory(noopExec),
-			getAgentDir: () => "/tmp/pi-pretty-test",
-		},
-		TextComponent: MockText,
-	});
-
-	return tools.get("bash");
-}
-
-describe("bash renderCall expansion", () => {
-	it("truncates long commands when collapsed", () => {
-		const bashTool = loadBashTool();
-		const command = `printf '${"x".repeat(120)}'`;
-
-		const rendered = bashTool.renderCall({ command }, mockTheme, {
-			lastComponent: new MockText(),
-			isError: false,
-			state: {},
-			expanded: false,
-			invalidate: () => {},
-		});
-
-		expect(rendered.getText()).toContain("bash");
-		expect(rendered.getText()).toContain("…");
-		expect(rendered.getText()).not.toContain(command);
-	});
-
-	it("shows the full command when expanded", () => {
-		const bashTool = loadBashTool();
-		const command = `printf '${"x".repeat(120)}'`;
-
-		const rendered = bashTool.renderCall({ command }, mockTheme, {
-			lastComponent: new MockText(),
-			isError: false,
-			state: {},
-			expanded: true,
-			invalidate: () => {},
-		});
-
-		expect(rendered.getText()).toContain(command);
-	});
-
-	it("preserves timeout text in both collapsed and expanded states", () => {
-		const bashTool = loadBashTool();
-		const command = `printf '${"x".repeat(120)}'`;
-
-		const collapsed = bashTool.renderCall({ command, timeout: 5 }, mockTheme, {
-			lastComponent: new MockText(),
-			isError: false,
-			state: {},
-			expanded: false,
-			invalidate: () => {},
-		});
-		const expanded = bashTool.renderCall({ command, timeout: 5 }, mockTheme, {
-			lastComponent: new MockText(),
-			isError: false,
-			state: {},
-			expanded: true,
-			invalidate: () => {},
-		});
-
-		expect(collapsed.getText()).toContain("(timeout 5s)");
-		expect(expanded.getText()).toContain("(timeout 5s)");
-	});
-
-	it("truncates ANSI tool headers that exceed the terminal width", () => {
-		withStdoutColumns(84, () => {
-			const bashTool = loadBashTool();
-			const command = `printf '${"界".repeat(120)}'`;
-
-			const rendered = bashTool.renderCall({ command }, ansiMockTheme, {
-				lastComponent: new MockText(),
-				isError: false,
-				state: {},
-				expanded: true,
-				invalidate: () => {},
-			});
-
-			for (const line of rendered.getText().split("\n")) {
-				expect(visibleWidth(line)).toBeLessThanOrEqual(84);
-			}
-		});
-	});
-
-	it("does not exceed narrow terminal widths", () => {
-		withStdoutColumns(24, () => {
-			const bashTool = loadBashTool();
-			const command = `printf '${"x".repeat(120)}'`;
-
-			const rendered = bashTool.renderCall({ command }, ansiMockTheme, {
-				lastComponent: new MockText(),
-				isError: false,
-				state: {},
-				expanded: true,
-				invalidate: () => {},
-			});
-
-			for (const line of rendered.getText().split("\n")) {
-				expect(visibleWidth(line)).toBeLessThanOrEqual(24);
-			}
-		});
-	});
-
-	it("does not add extra internal padding to the bash title in error state", () => {
-		withStdoutColumns(48, () => {
-			const bashTool = loadBashTool();
-			const rendered = bashTool.renderCall({ command: "false" }, mockTheme, {
-				lastComponent: new MockText(),
-				isError: true,
-				state: {},
-				expanded: false,
-				invalidate: () => {},
-			});
-
-			const lines = stripAnsi(rendered.getText()).split("\n");
-			expect(lines[1]).toMatch(/^  \$ false/);
-		});
-	});
-
-	it("pads every line of multi-line tool errors", () => {
-		withStdoutColumns(48, () => {
-			const bashTool = loadBashTool();
-			const rendered = bashTool.renderResult(
-				{ content: [{ type: "text", text: "\nfirst error\n\n\nsecond error\n" }] },
-				{},
-				ansiMockTheme,
-				{
-					lastComponent: new MockText(),
-					isError: true,
-					state: {},
-					expanded: false,
-					invalidate: () => {},
-				},
-			);
-
-			const lines = stripAnsi(rendered.getText()).split("\n");
-			expect(lines[0]).toContain("✗ exit 1");
-			expect(lines[1]).toMatch(/^─+$/);
-			expect(lines[2]).toMatch(/^  first error/);
-			expect(lines[3]).toMatch(/^  /);
-			expect(lines[3].trim()).toBe("");
-			expect(lines[4]).toMatch(/^  second error/);
-		});
-	});
-
-	it("applies tool background correctly to bash results without unnecessary resets", () => {
-		withStdoutColumns(64, () => {
-			const bashTool = loadBashTool();
-			const rendered = bashTool.renderResult(
-				{
-					content: [{ type: "text", text: "output" }],
-					details: { _type: "bashResult", text: "output", exitCode: 1, command: "test" },
-				},
-				{},
-				ansiMockTheme,
-				{
-					lastComponent: new MockText(),
-					isError: true,
-					state: { _tw: "64" },
-					expanded: false,
-					invalidate: () => {},
-				},
-			);
-
-			expect(rendered.getText()).toMatch(/\x1b\[48;/); // tool background is applied
-			expect(rendered.getText()).not.toContain("\x1b[0m");
-			expect(rendered.getText()).not.toContain("\x1b[49m");
-			for (const line of rendered.getText().split("\n")) {
-				expect(visibleWidth(line)).toBeLessThanOrEqual(64);
-			}
-		});
-	});
-
-	it("renders bash results using the component render width instead of stdout columns", () => {
-		withStdoutColumns(120, () => {
-			const bashTool = loadBashTool();
-			const rendered = bashTool.renderResult(
-				{ content: [{ type: "text", text: "hello world" }], details: { _type: "bashResult", text: "hello world", exitCode: 0, command: "echo hi" } },
-				{},
-				mockTheme,
-				{
-					lastComponent: new MockText(),
-					isError: false,
-					state: {},
-					expanded: false,
-					invalidate: () => {},
-				},
-			);
-
-			rendered.render(80);
-			const lines = stripAnsi(rendered.getText()).split("\n");
-			expect(lines.some((line) => /^─{80}$/.test(line))).toBe(true);
-			for (const line of rendered.getText().split("\n")) {
-				expect(visibleWidth(line)).toBeLessThanOrEqual(80);
-			}
-		});
-	});
-});