pi-copy-mode 0.3.2 → 0.3.3

package/README.md

@@ -1,6 +1,6 @@
-# pi-copy-mode
+# @luan.sh/pi-copy-mode&nbsp;[<img src="https://pi.luan.sh/icons/pi.svg" width="14" alt="Pi gallery">](https://pi.dev/packages/@luan.sh/pi-copy-mode)&nbsp;[<img src="https://pi.luan.sh/icons/npm.svg" width="14" alt="npm">](https://www.npmjs.com/package/@luan.sh/pi-copy-mode)
 
-`pi-copy-mode` adds Vim-style transcript selection, copying,
+`@luan.sh/pi-copy-mode` adds Vim-style transcript selection, copying,
 annotations, and reactions to Pi. Select characters, lines, or columns, copy
 them, or attach feedback to your next request directly from the selection.
 
@@ -9,23 +9,23 @@ commands.
 
 ## Preview
 
-![pi-copy-mode in Bootty](https://github.com/luan/agents/releases/download/v0.3.2/pi-copy-mode.png)
+![@luan.sh/pi-copy-mode in Bootty](https://pi.luan.sh/media/previews/pi-copy-mode-9b8c74e7ea97.png)
 
-[Watch the demo](https://github.com/luan/agents/releases/download/v0.3.2/pi-copy-mode.mp4).
+[Watch the demo](https://pi.luan.sh/media/previews/pi-copy-mode-7a4bd7d42c6a.mp4).
 
 ## Install
 
 ```sh
-pi install npm:pi-copy-mode
+pi install npm:@luan.sh/pi-copy-mode
 ```
 
 Optional companions:
 
-- `pi install npm:pi-xsettings` adds the `/xsettings` UI for the
+- `pi install npm:@luan.sh/pi-xsettings` adds the `/xsettings` UI for the
   settings below and binds the `copy-mode.enter` action to a global key from
   `keybindings.json`; without it the default setting applies and copy mode can
   only be entered from a mouse selection (see below).
-- `pi install npm:pi-developer-messages` routes annotation guidance
+- `pi install npm:@luan.sh/pi-developer-messages` routes annotation guidance
   through developer messages. Without it, the same guidance is appended to
   the system prompt only when a request contains annotations.
 
@@ -66,7 +66,7 @@ Behaviour of the actions:
   clipboard when Pi provides one and falls back to an OSC 52 escape sequence
   otherwise. A "Copied!" or "Copy failed" pill appears at the cursor.
 - `annotate` and `react` publish `selection.comment` and `selection.reaction`
-  requests through the `pi-libtui/selection` registry. The built-in annotation feature handles both requests.
+  requests through the `@luan.sh/pi-libtui/selection` registry. The built-in annotation feature handles both requests.
   While the handler runs, copy-mode input is suspended. A confirmed request
   collapses the selection to the cursor and keeps copy mode active; a
   cancelled one keeps the range. When the request was started from a mouse
@@ -75,7 +75,7 @@ Behaviour of the actions:
 - Folds: `foldPrefix` arms a prefix; the next key is matched against
   `foldOpen`, `foldClose`, `foldOpenAll`, and `foldCloseAll`. The suffix keys
   do nothing without the prefix. Open/close apply to the fold under the
-  cursor, provided by other extensions through the `pi-libtui/folding`
+  cursor, provided by other extensions through the `@luan.sh/pi-libtui/folding`
   registry.
 
 A left click inside copy mode moves the cursor to that cell and drops the
@@ -118,14 +118,14 @@ as a hoverable pill. Directives inside inline or fenced code remain text.
 ## Keybindings
 
 No action in this package has a default key. Actions are registered through
-`pi-libactions`, and keys come from `keybindings.json` in Pi's agent
+`@luan.sh/pi-libactions`, and keys come from `keybindings.json` in Pi's agent
 directory, normally `~/.pi/agent/keybindings.json`. The file is a JSON object
 mapping action ID to one key ID or an array of key IDs. Key IDs are lowercase:
 write `shift+v` rather than `V`, `escape` rather than `Escape`. Invalid key IDs
 are ignored. The file is read when a session starts; run `/reload` after
 editing it.
 
-Global entry (exposed as a shortcut only when `pi-xsettings` is
+Global entry (exposed as a shortcut only when `@luan.sh/pi-xsettings` is
 installed):
 
 ```json
@@ -170,7 +170,7 @@ One example per group; the full ID list follows.
 
 ## Settings
 
-Settings use the `pi-copy-mode` namespace:
+Settings use the `@luan.sh/pi-copy-mode` namespace:
 
 | Key | Default | Meaning |
 | --- | --- | --- |
@@ -178,11 +178,11 @@ Settings use the `pi-copy-mode` namespace:
 | `copyOnSelect` | `false` | Copy text immediately when a mouse selection is completed. When off, the selection stays available for the action bar and keyboard adoption. |
 
 Edit them under Interaction → Copy mode via `/xsettings` when
-`pi-xsettings` is installed; otherwise the compiled defaults apply.
+`@luan.sh/pi-xsettings` is installed; otherwise the compiled defaults apply.
 
 ## Library API
 
-Importing `pi-copy-mode` does not start the extension. It exports:
+Importing `@luan.sh/pi-copy-mode` does not start the extension. It exports:
 
 - Keybinding contracts: `COPY_MODE_ACTIONS`, `loadCopyModeKeybindings`, and
   `matchCopyModeAction`, with the `CopyModeAction` and `CopyModeKeybindings`
@@ -191,7 +191,7 @@ Importing `pi-copy-mode` does not start the extension. It exports:
   `moveVirtualCursor`, `graphemeEnd`, and `scrollTopForCursor`, plus their
   document and point types.
 
-`pi-copy-mode/annotations` exposes annotation helpers without starting Pi:
+`@luan.sh/pi-copy-mode/annotations` exposes annotation helpers without starting Pi:
 
 - Envelope: `serializeEnvelope`, `parseEnvelope`, `projectEnvelope`,
   `responseAnnotations`, `annotationText`.
@@ -204,7 +204,7 @@ Importing `pi-copy-mode` does not start the extension. It exports:
   `ParsedResponseAnnotations`, `ResolvedAnnotationLink`.
 
 ```ts
-import { parseEnvelope, projectEnvelope } from "pi-copy-mode/annotations";
+import { parseEnvelope, projectEnvelope } from "@luan.sh/pi-copy-mode/annotations";
 
 const parsed = parseEnvelope(messageText);
 const readable = parsed ? projectEnvelope(messageText) : messageText;
@@ -236,7 +236,7 @@ The extension registers the `copy-mode.enter` action and the setting at load
 time, and mounts one session-scoped host widget per TUI session. The host
 reads the fullscreen transcript through a validated private Pi surface, draws
 the cursor and selection as screen decorations, and talks to other extensions
-only through the shared `pi-libtui` selection, folding, and mouse registries.
+only through the shared `@luan.sh/pi-libtui` selection, folding, and mouse registries.
 Annotations live in their own feature directory and register alongside copy
 mode under the same ownership claim. If two copies load, only the owner
 registers features; it releases ownership on reload or quit. The annotation
@@ -268,7 +268,7 @@ or native executable is registered.
 
 - A key does nothing: there are no built-in keys. Check the action ID and key
   ID in `keybindings.json` and run `/reload`. For `copy-mode.enter`,
-  `pi-xsettings` must be installed.
+  `@luan.sh/pi-xsettings` must be installed.
 - Comment or react requires a completed selection. Both are built in; no
   separate annotations package is needed. An empty reaction list shows a
   warning until at least one choice is configured.
@@ -285,4 +285,4 @@ harnesses/pi/agent/packages/pi-copy-mode. Run `bun run typecheck` and
 `bun test test` in that directory.
 
 The combined gallery video includes selection/copying and annotation workflows.
-[Selection and copying](https://github.com/luan/agents/releases/download/v0.3.2/pi-copy-mode-selection.mp4) · [Comments and reactions](https://github.com/luan/agents/releases/download/v0.3.2/pi-copy-mode-annotations.mp4).
+[Selection and copying](https://pi.luan.sh/media/previews/pi-copy-mode-selection-d6c073fbd593.mp4) · [Comments and reactions](https://pi.luan.sh/media/previews/pi-copy-mode-annotations-34a491d60fd7.mp4).

package/node_modules/{pi-libactions → @luan.sh/pi-libactions}/README.md

@@ -1,23 +1,23 @@
-# pi-libactions
+# @luan.sh/pi-libactions&nbsp;[<img src="https://pi.luan.sh/icons/pi.svg" width="14" alt="Pi gallery">](https://pi.dev/packages/@luan.sh/pi-libactions)&nbsp;[<img src="https://pi.luan.sh/icons/npm.svg" width="14" alt="npm">](https://www.npmjs.com/package/@luan.sh/pi-libactions)
 
-`pi-libactions` is a UI-free action registry and keybinding loader
+`@luan.sh/pi-libactions` is a UI-free action registry and keybinding loader
 for Pi extensions. It is a library, not a Pi extension: importing it registers
 no commands, shortcuts, tools, or UI, and it is not installed with `pi install`
 on its own. It reaches users as a dependency of the extensions that use it.
 
 The registry lets an extension publish a named action without knowing which
-host will expose it. A shortcut host (currently `pi-xsettings`) reads
+host will expose it. A shortcut host (currently `@luan.sh/pi-xsettings`) reads
 the user's `keybindings.json` and binds each configured key to the matching
-action. Modal features such as `pi-copy-mode` read the same snapshot
+action. Modal features such as `@luan.sh/pi-copy-mode` read the same snapshot
 without registering their keys as global editor shortcuts.
 
 ## Preview
 
 Actions registered by Side Panel and Side Chat, bound by Xsettings, and listed in Pi's `/hotkeys`. The library itself registers no UI.
 
-![pi-libactions in Bootty](https://github.com/luan/agents/releases/download/v0.3.2/pi-libactions.png)
+![@luan.sh/pi-libactions in Bootty](https://pi.luan.sh/media/previews/pi-libactions-bbaab600e262.png)
 
-[Watch the demo](https://github.com/luan/agents/releases/download/v0.3.2/pi-libactions.mp4).
+[Watch the demo](https://pi.luan.sh/media/previews/pi-libactions-c0f46f189045.mp4).
 
 ## For users: `keybindings.json`
 
@@ -67,7 +67,7 @@ Rules the loader applies:
 
 Which action IDs exist depends on the extensions you have installed; each
 extension's README lists its IDs. Bindings only take effect when a shortcut
-host is installed: `pi install npm:pi-xsettings` provides one that
+host is installed: `pi install npm:@luan.sh/pi-xsettings` provides one that
 calls `pi.registerShortcut()` for every configured key. Without a host, the
 registry still works but nothing binds global keys.
 
@@ -81,16 +81,16 @@ ships inside your published package:
 ```json
 {
   "dependencies": {
-    "pi-libactions": "^0.1.0"
+    "@luan.sh/pi-libactions": "^0.1.0"
   },
-  "bundledDependencies": ["pi-libactions"]
+  "bundledDependencies": ["@luan.sh/pi-libactions"]
 }
 ```
 
 Then import the public SDK:
 
 ```ts
-import { registerAction } from "pi-libactions/sdk";
+import { registerAction } from "@luan.sh/pi-libactions/sdk";
 ```
 
 The package has no runtime dependencies; `@earendil-works/pi-coding-agent` and
@@ -121,7 +121,7 @@ Use a stable, namespaced ID (for example `myext.panel.open`). Register during
 extension setup and keep the disposer for reload and shutdown:
 
 ```ts
-import { registerAction } from "pi-libactions/sdk";
+import { registerAction } from "@luan.sh/pi-libactions/sdk";
 
 const unregister = registerAction({
   id: "example.open",
@@ -140,7 +140,7 @@ unregister();
 registry uses the full API:
 
 ```ts
-import { ensureActionsRegistry } from "pi-libactions/sdk";
+import { ensureActionsRegistry } from "@luan.sh/pi-libactions/sdk";
 
 const actions = ensureActionsRegistry();
 const stopListening = actions.onRegister((action) => {
@@ -170,7 +170,7 @@ Behaviour, as implemented in `src/protocol/actions.ts`:
 ### Reading keybindings from an extension
 
 ```ts
-import { loadActionKeybindings, isActionKeyId } from "pi-libactions/sdk";
+import { loadActionKeybindings, isActionKeyId } from "@luan.sh/pi-libactions/sdk";
 
 const bindings = loadActionKeybindings(); // defaults to <agent dir>/keybindings.json
 const keys = bindings["example.open"] ?? []; // readonly KeyId[], frozen

package/node_modules/{pi-libactions → @luan.sh/pi-libactions}/package.json

@@ -1,6 +1,6 @@
 {
-  "name": "pi-libactions",
-  "version": "0.3.2",
+  "name": "@luan.sh/pi-libactions",
+  "version": "0.3.3",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -18,8 +18,8 @@
   },
   "pi": {
     "extensions": [],
-    "image": "https://github.com/luan/agents/releases/download/v0.3.2/pi-libactions.png",
-    "video": "https://github.com/luan/agents/releases/download/v0.3.2/pi-libactions.mp4"
+    "image": "https://pi.luan.sh/media/previews/pi-libactions-bbaab600e262.png",
+    "video": "https://pi.luan.sh/media/previews/pi-libactions-c0f46f189045.mp4"
   },
   "dependencies": {},
   "peerDependencies": {
@@ -36,5 +36,8 @@
     "typecheck": "tsc --build",
     "test": "bun test --only-failures test"
   },
-  "bundledDependencies": []
+  "bundledDependencies": [],
+  "publishAliases": [
+    "pi-libactions"
+  ]
 }

package/node_modules/{pi-libtui → @luan.sh/pi-libtui}/README.md

@@ -1,11 +1,11 @@
-# pi-libtui
+# @luan.sh/pi-libtui&nbsp;[<img src="https://pi.luan.sh/icons/pi.svg" width="14" alt="Pi gallery">](https://pi.dev/packages/@luan.sh/pi-libtui)&nbsp;[<img src="https://pi.luan.sh/icons/npm.svg" width="14" alt="npm">](https://www.npmjs.com/package/@luan.sh/pi-libtui)
 
 Shared terminal UI for Pi extensions: layouts, split panes, dialogs, pickers,
 selection actions, semantic colors, icons, cursors, syntax highlighting,
 animated tool surfaces, streamed output, diffs, terminal projection, and the
 protocols those pieces need. The primary audience is extension authors.
 
-The package has two surfaces. `import "pi-libtui"` is a
+The package has two surfaces. `import "@luan.sh/pi-libtui"` is a
 side-effect-free library: it does not start Pi, probe the terminal, register a
 tool, or install UI. `src/extension.ts` is a Pi extension (listed in the
 package's `pi.extensions`) that installs the generic mouse, cursor, and
@@ -18,24 +18,24 @@ registers no model-facing tools, keybindings, or feature-specific UI.
 
 The native palette diagnostic and shared picker components in Xsettings.
 
-![pi-libtui in Bootty](https://github.com/luan/agents/releases/download/v0.3.2/pi-libtui.png)
+![@luan.sh/pi-libtui in Bootty](https://pi.luan.sh/media/previews/pi-libtui-1820a03ca387.png)
 
-[Watch the demo](https://github.com/luan/agents/releases/download/v0.3.2/pi-libtui.mp4).
+[Watch the demo](https://pi.luan.sh/media/previews/pi-libtui-e7ff85f140d3.mp4).
 
 ## Install
 
 ```sh
-pi install npm:pi-libtui
+pi install npm:@luan.sh/pi-libtui
 ```
 
 This loads the host extension and the `harmonious` theme on its own. Feature
-packages normally bundle their own copy instead: add `pi-libtui` to
+packages normally bundle their own copy instead: add `@luan.sh/pi-libtui` to
 both `dependencies` and `bundledDependencies` in `package.json`, and list
 `"./node_modules/pi-libtui/src/extension.ts"` in the package's
 `pi.extensions` so the mouse/cursor bridge is active. The host claims itself
 once per process, so several installed copies do not conflict.
 
-Optional companion: `pi install npm:pi-xsettings` adds the `/xsettings`
+Optional companion: `pi install npm:@luan.sh/pi-xsettings` adds the `/xsettings`
 UI that publishes the appearance settings below; without it the compiled
 defaults apply.
 
@@ -47,6 +47,59 @@ neither a generated 256-color palette nor an ANSI base-16 palette, the host
 switches to Pi's built-in theme for the detected light or dark scheme (dark if
 the measurement fails).
 
+## Components
+
+Captures of the shared components inside the extensions that use them. The
+images are served from the documentation site.
+
+`ActionPanel` with a `DialogButtonBar` footer in a `DialogOverlay`: the
+pi-copy-mode reaction picker.
+
+![ActionPanel and DialogButtonBar in pi-copy-mode](https://pi.luan.sh/media/libtui/action-panel.png)
+
+`MultiSelect` with ordered checkboxes, a filter `SemanticInput`, and a
+`DialogButtonBar`: the pi-xsettings segment editor.
+
+![MultiSelect in pi-xsettings](https://pi.luan.sh/media/libtui/multi-select.png)
+
+`mountSplitPane` with side-panel tabs from `registerSidePanelProvider`:
+pi-panels hosting a pi-side conversation.
+
+![Split pane and side-panel tabs in pi-panels](https://pi.luan.sh/media/libtui/split-panes.png)
+
+`UnifiedDiffView` from `pi-libtui/diff`: the pi-fileops `apply_patch` result.
+
+![UnifiedDiffView in pi-fileops](https://pi.luan.sh/media/libtui/unified-diff.png)
+
+`PtyPane` over `TerminalProjection` from `pi-libtui/terminal`: the
+pi-exec-command Process Hub attached to a running server.
+
+![PtyPane in pi-exec-command](https://pi.luan.sh/media/libtui/terminal.png)
+
+`renderDetailCard` as an anchored overlay: a pi-copy-mode annotation.
+
+![Detail card in pi-copy-mode](https://pi.luan.sh/media/libtui/detail-card.png)
+
+`ToolActivity` and `ToolTranscript` from `pi-libtui/tool`: pi-tool-search
+and pi-exec-command rows collapsed into an `Explored` group.
+
+![ToolActivity rows in pi-tool-search](https://pi.luan.sh/media/libtui/tool-activity.png)
+
+`ProgressBar`, `renderPill`, and `renderEditorTokenPills`: the
+pi-custom-editor status row and file tokens.
+
+![Status row and editor pills in pi-custom-editor](https://pi.luan.sh/media/libtui/status-row.png)
+
+`TransientPill`: the pi-tuicr confirmation after a review comment is added.
+
+![TransientPill in pi-tuicr](https://pi.luan.sh/media/libtui/transient-pill.png)
+
+Components without a capture in a shipped extension: `PickerPanel`
+(pi-prompt-storage), `SearchableSelect` and `SelectBox` (pi-xsettings
+editors), `SelectionActionBar` (pi-copy-mode), `FramedEditorOverlay`,
+`mountHoverTooltip`, `FloatingOverlay`, `ActivityIndicator` styles, and
+`applyScrollbar`. Add them here when a gallery recording shows them in use.
+
 ## Public modules
 
 Every entry point is a side-effect-free import. "Host required" means the
@@ -54,15 +107,15 @@ Pi-native behaviour also needs the extension loaded.
 
 | Import path | Principal exports / capability | Host required |
 | --- | --- | --- |
-| `pi-libtui` | Layouts, split panes, side-panel protocol, dialogs, pickers, inputs, selection actions, semantic colors, icons, cursors, `PtyProcess`, `PtyPane`, `applyScrollbar`, `PointerInteractionController`, `RenderedLinesCache`, `SyntaxText`, motion/progress, appearance (`getTuiAppearance`, `configureTuiAppearance`, `subscribeTuiAppearance`), `ensureNativeBinary` | Rendering no; panes, PTYs, and bridges yes |
-| `pi-libtui/diff` | `createUnifiedDiffModel`, `parseUnifiedDiff`, `renderUnifiedDiff`, `UnifiedDiffView`, bounded diff models/viewports | No |
-| `pi-libtui/editor` | `ensureEditorRegistry`, `dispatchEditorPaste`, `dispatchEditorRender`, `SemanticEditor`, `semanticEditorTheme`, editor registry contracts | Only to connect the registry to Pi's editor |
-| `pi-libtui/folding` | `ensureFoldingRegistry`, `foldTargetAt`, `clearFoldingCurrent`, fold-target contracts | Only for copy-mode keyboard integration |
-| `pi-libtui/mouse` | `ensureMouseRegistry`, `registerModalPointerShield`, viewport handlers, pointer contracts, `getFullscreenLayoutCapability`, `publishFullscreenLayoutCapability`, `resolveFullscreenLayout` | Yes for terminal pointer events and layout geometry |
-| `pi-libtui/selection` | `ensureSelectionRegistry`, native selection geometry, completion events, action contracts | Yes for Pi-native selection events |
-| `pi-libtui/stream` | `BoundedStreamBuffer`, bounded UTF-8/ANSI-safe stream snapshots | No |
-| `pi-libtui/terminal` | `TerminalProjection`, incremental `TerminalOutput` for bounded PTY/ANSI projection | No |
-| `pi-libtui/tool` | `ToolAction`, `LiveToolAction`, `ToolDisclosureAction`, `ToolActivity`, `ToolOutput`, `ToolTranscript`, `ToolViewRegion`, tool-call preview helpers | No for rendering |
+| `@luan.sh/pi-libtui` | Layouts, split panes, side-panel protocol, dialogs, pickers, inputs, selection actions, semantic colors, icons, cursors, `PtyProcess`, `PtyPane`, `applyScrollbar`, `PointerInteractionController`, `RenderedLinesCache`, `SyntaxText`, motion/progress, appearance (`getTuiAppearance`, `configureTuiAppearance`, `subscribeTuiAppearance`), `ensureNativeBinary` | Rendering no; panes, PTYs, and bridges yes |
+| `@luan.sh/pi-libtui/diff` | `createUnifiedDiffModel`, `parseUnifiedDiff`, `renderUnifiedDiff`, `UnifiedDiffView`, bounded diff models/viewports | No |
+| `@luan.sh/pi-libtui/editor` | `ensureEditorRegistry`, `dispatchEditorPaste`, `dispatchEditorRender`, `SemanticEditor`, `semanticEditorTheme`, editor registry contracts | Only to connect the registry to Pi's editor |
+| `@luan.sh/pi-libtui/folding` | `ensureFoldingRegistry`, `foldTargetAt`, `clearFoldingCurrent`, fold-target contracts | Only for copy-mode keyboard integration |
+| `@luan.sh/pi-libtui/mouse` | `ensureMouseRegistry`, `registerModalPointerShield`, viewport handlers, pointer contracts, `getFullscreenLayoutCapability`, `publishFullscreenLayoutCapability`, `resolveFullscreenLayout` | Yes for terminal pointer events and layout geometry |
+| `@luan.sh/pi-libtui/selection` | `ensureSelectionRegistry`, native selection geometry, completion events, action contracts | Yes for Pi-native selection events |
+| `@luan.sh/pi-libtui/stream` | `BoundedStreamBuffer`, bounded UTF-8/ANSI-safe stream snapshots | No |
+| `@luan.sh/pi-libtui/terminal` | `TerminalProjection`, incremental `TerminalOutput` for bounded PTY/ANSI projection | No |
+| `@luan.sh/pi-libtui/tool` | `ToolAction`, `LiveToolAction`, `ToolDisclosureAction`, `ToolActivity`, `ToolOutput`, `ToolTranscript`, `ToolViewRegion`, tool-call preview helpers | No for rendering |
 
 The `ensure*Registry` functions create or reuse a process-global capability
 keyed by `Symbol.for`, so feature packages and the host share one instance.
@@ -74,16 +127,16 @@ guarded Pi 0.84–0.85 adapter; unsupported hosts keep their native transcript.
 
 ## Native binaries
 
-Feature packages shell out to Rust binaries such as `terminal_bridge` (the
+Feature packages shell out to Rust binaries such as `terminal-bridge` (the
 exported `TERMINAL_BRIDGE` descriptor). Requires a Rust toolchain
-(https://rustup.rs). The `terminal_bridge` binary builds itself on first use
-under Pi's agent directory (`native/terminal-bridge/v<version>/`), where
-`<version>` is this package's version. Set `PI_TERMINAL_BRIDGE_BINARY` to use
+(https://rustup.rs). The `terminal-bridge` binary builds itself on first use
+under Pi's agent directory (`native/terminal-bridge/<revision>/`), where
+`<revision>` is the source commit recorded in the packaged `native-revision` file. Set `PI_TERMINAL_BRIDGE_BINARY` to use
 a prebuilt binary; it must point at an executable file.
 
 `ensureNativeBinary(binary, hooks?)` resolves in this order: the descriptor's
-env override, then `<agentDir>/native/<crate>/v<version>/bin/<name>`, building
-it on first use when absent. Builds are keyed by crate and version, so every
+env override, then `<agentDir>/native/<crate>/<revision>/bin/<name>`, building
+it on first use when absent. Builds are keyed by crate and source commit, so every
 installed copy shares them, and concurrent requests within one process share
 one build. Pass `onBuild` to show the delay in the UI. The extension host keeps
 the shared PTY host alive across an extension reload; a session switch or quit
@@ -125,8 +178,8 @@ shape is absent.
 
 This package has no settings store of its own. It exposes an appearance
 registry with compiled defaults (`DEFAULT_TUI_APPEARANCE`) that a settings host
-such as `pi-xsettings` overrides through `configureTuiAppearance()`;
-with pi-xsettings installed they are edited live via `/xsettings`. Keys and
+such as `@luan.sh/pi-xsettings` overrides through `configureTuiAppearance()`;
+with @luan.sh/pi-xsettings installed they are edited live via `/xsettings`. Keys and
 defaults:
 
 | Key | Default | Values |
@@ -188,7 +241,7 @@ through `src/color/resolver.ts`. Feature code uses only the root color API:
 ## Troubleshooting
 
 - A feature renders but clicks do nothing: the host extension is not loaded.
-  Install `pi-libtui` as a Pi package or list its `src/extension.ts`
+  Install `@luan.sh/pi-libtui` as a Pi package or list its `src/extension.ts`
   in the feature package's `pi.extensions`.
 - Nerd Font or Powerline glyphs are missing: set the icon pack to `unicode` and
   disable Powerline in `/xsettings`. Those are also the compiled defaults.
@@ -201,5 +254,6 @@ Source: https://github.com/luan/agents, directory
 harnesses/pi/agent/packages/pi-libtui. Run `bun run typecheck` and
 `bun test test` in that directory. When running from that checkout,
 `ensureNativeBinary` also looks for `target/{release,debug}/<name>` in the Cargo
-workspace and reports an unbuilt checkout instead of building; builds are pinned
-to the `v<version>` git tag, so publishing requires a matching tag.
+workspace and reports an unbuilt checkout instead of building. `just pi-pack`
+records the checkout commit in every bundled `@luan.sh/pi-libtui/native-revision` file,
+so native builds do not depend on npm versions or repository-wide release tags.

package/node_modules/@luan.sh/pi-libtui/native-revision

@@ -0,0 +1 @@
+eace67b49e52950cb408c08f290f1ca9c409d68a

package/node_modules/{pi-libtui → @luan.sh/pi-libtui}/package.json

@@ -1,6 +1,6 @@
 {
-  "name": "pi-libtui",
-  "version": "0.3.2",
+  "name": "@luan.sh/pi-libtui",
+  "version": "0.3.9",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -30,8 +30,8 @@
     "themes": [
       "./themes"
     ],
-    "image": "https://github.com/luan/agents/releases/download/v0.3.2/pi-libtui.png",
-    "video": "https://github.com/luan/agents/releases/download/v0.3.2/pi-libtui.mp4"
+    "image": "https://pi.luan.sh/media/previews/pi-libtui-1820a03ca387.png",
+    "video": "https://pi.luan.sh/media/previews/pi-libtui-e7ff85f140d3.mp4"
   },
   "peerDependencies": {
     "@earendil-works/pi-coding-agent": "*",
@@ -51,5 +51,8 @@
     "typecheck": "tsc --build",
     "test": "bun test --only-failures --timeout 15000 test"
   },
-  "bundledDependencies": []
+  "bundledDependencies": [],
+  "publishAliases": [
+    "pi-libtui"
+  ]
 }

package/node_modules/{pi-libtui → @luan.sh/pi-libtui}/src/color/preview.ts

@@ -13,7 +13,7 @@ const HUE_EDGES: readonly ChannelMask[] = [
 	[true, false, true],
 ];
 
-/** Width of the upstream color256 terminal preview, including its base16 legend. */
+/** Width of the color256 terminal preview, including its base16 legend. */
 export const COLOR256_PREVIEW_WIDTH = 69;
 
 /**

package/node_modules/{pi-libtui → @luan.sh/pi-libtui}/src/native-binary.ts

@@ -35,7 +35,7 @@ export type NativeBinaryLocation =
 
 export const TERMINAL_BRIDGE: NativeBinary = {
 	crate: "terminal-bridge",
-	binaryName: "terminal_bridge",
+	binaryName: "terminal-bridge",
 	env: "PI_TERMINAL_BRIDGE_BINARY",
 };
 
@@ -81,7 +81,8 @@ export interface EnsureNativeBinaryHooks {
  * revision under Pi's agent directory and shared by every installed pi-libtui copy.
  */
 export async function ensureNativeBinary(binary: NativeBinary, hooks: EnsureNativeBinaryHooks = {}): Promise<string> {
-	const location = locateNativeBinary(binary, processOptions());
+	const options = processOptions();
+	const location = locateNativeBinary(binary, options);
 	if (location.kind === "found") return location.path;
 	if (location.kind === "unbuilt-checkout") {
 		throw new Error(
@@ -92,7 +93,7 @@ export async function ensureNativeBinary(binary: NativeBinary, hooks: EnsureNati
 	const existing = builds.get(location.path);
 	if (existing) return existing;
 	hooks.onBuild?.(`Building ${binary.binaryName} (first use); this takes a minute.`);
-	const build = runCargo(nativeBuildArguments(binary, nativeRevision(), location.installRoot), location.installRoot)
+	const build = runCargo(nativeBuildArguments(binary, options.rev, location.installRoot), location.installRoot)
 		.then(() => {
 			if (!isExecutable(location.path)) throw new Error(`cargo install did not produce ${location.path}`);
 			return location.path;
@@ -106,12 +107,11 @@ export function terminalBridgeBinaryPath(): Promise<string> {
 	return ensureNativeBinary(TERMINAL_BRIDGE);
 }
 
-/** Builds are pinned to the git tag matching this package's version. Tag the repository when publishing. */
+/** The pack step records the exact source commit independently of npm versions. */
 export function nativeRevision(): string {
-	const manifest = JSON.parse(readFileSync(new URL("../package.json", import.meta.url), "utf8")) as {
-		version: string;
-	};
-	return `v${manifest.version}`;
+	const revision = readFileSync(new URL("../native-revision", import.meta.url), "utf8").trim();
+	if (!/^[a-f0-9]{40}$/.test(revision)) throw new Error("Invalid native source revision; reinstall the package.");
+	return revision;
 }
 
 function processOptions(): NativeBinaryOptions {

package/node_modules/{pi-libtui → @luan.sh/pi-libtui}/src/panels.ts

@@ -1,7 +1,7 @@
 import type { Theme } from "@earendil-works/pi-coding-agent";
 import type { Component, Focusable } from "@earendil-works/pi-tui";
-import type { SplitPaneHost, TuiIconName } from "pi-libtui";
-import type { TuiMouseEvent } from "pi-libtui/mouse";
+import type { SplitPaneHost, TuiIconName } from "@luan.sh/pi-libtui";
+import type { TuiMouseEvent } from "@luan.sh/pi-libtui/mouse";
 
 export const SIDE_PANEL_REGISTRY_KEY = Symbol.for("pi-panels/registry/v1");
 export const SIDE_PANEL_PROTOCOL = "pi-panels/registry/v1" as const;

package/node_modules/{pi-libtui → @luan.sh/pi-libtui}/test/color-preview.test.ts

@@ -3,7 +3,7 @@ import { visibleWidth } from "@earendil-works/pi-tui";
 import { COLOR256_PREVIEW_WIDTH, renderColor256Preview } from "../src/color/preview.ts";
 
 describe("color256 preview", () => {
-	test("matches the upstream terminal grid dimensions and labels", () => {
+	test("matches the terminal grid dimensions and labels", () => {
 		const lines = renderColor256Preview("harmonious");
 		expect(lines).toHaveLength(20);
 		expect(lines.every((line) => visibleWidth(line) === COLOR256_PREVIEW_WIDTH)).toBe(true);

package/node_modules/{pi-libtui → @luan.sh/pi-libtui}/test/editor-chrome.test.ts

@@ -1,13 +1,13 @@
 import { describe, expect, test } from "bun:test";
 import type { Theme } from "@earendil-works/pi-coding-agent";
 import { stripTerminalSequences, visibleWidth } from "@earendil-works/pi-tui";
-import { tuiTheme } from "pi-libtui";
+import { tuiTheme } from "@luan.sh/pi-libtui";
 import {
 	type EditorCompositionStyle,
 	renderEditorComposition,
 	renderEditorCompositionPreview,
 	renderEditorCompositionStatus,
-} from "pi-libtui/editor";
+} from "@luan.sh/pi-libtui/editor";
 
 const theme = {
 	name: "editor-chrome-test",

package/node_modules/{pi-libtui → @luan.sh/pi-libtui}/test/native-binary.test.ts

@@ -10,7 +10,7 @@ const options = (executables: readonly string[], environment: Record<string, str
 	rev: "v1.2.3",
 	isExecutable: (path: string) => executables.includes(path),
 });
-const managed = join("/agent/native", "terminal-bridge", "v1.2.3", "bin", "terminal_bridge");
+const managed = join("/agent/native", "terminal-bridge", "v1.2.3", "bin", "terminal-bridge");
 
 test("env override wins and must be executable", () => {
 	expect(locateNativeBinary(TERMINAL_BRIDGE, options(["/x/bridge"], { [ENV]: "/x/bridge" }))).toEqual({

package/node_modules/{pi-libtui → @luan.sh/pi-libtui}/test/public-surface.test.ts

@@ -1,15 +1,15 @@
 import { describe, expect, test } from "bun:test";
 
 const PUBLIC_ENTRYPOINTS = [
-	"pi-libtui",
-	"pi-libtui/diff",
-	"pi-libtui/editor",
-	"pi-libtui/folding",
-	"pi-libtui/mouse",
-	"pi-libtui/selection",
-	"pi-libtui/stream",
-	"pi-libtui/terminal",
-	"pi-libtui/tool",
+	"@luan.sh/pi-libtui",
+	"@luan.sh/pi-libtui/diff",
+	"@luan.sh/pi-libtui/editor",
+	"@luan.sh/pi-libtui/folding",
+	"@luan.sh/pi-libtui/mouse",
+	"@luan.sh/pi-libtui/selection",
+	"@luan.sh/pi-libtui/stream",
+	"@luan.sh/pi-libtui/terminal",
+	"@luan.sh/pi-libtui/tool",
 ] as const;
 
 const CAPABILITY_KEYS = [
@@ -30,7 +30,7 @@ describe("public module boundaries", () => {
 		}
 		const after = CAPABILITY_KEYS.map((key) => Object.hasOwn(globalThis, key));
 		expect(after).toEqual(before);
-		const mouse = await import("pi-libtui/mouse");
+		const mouse = await import("@luan.sh/pi-libtui/mouse");
 		expect(Object.keys(mouse).sort()).toEqual([
 			"FULLSCREEN_LAYOUT_CAPABILITY_KEY",
 			"FULLSCREEN_LAYOUT_PROTOCOL",
@@ -44,7 +44,7 @@ describe("public module boundaries", () => {
 			"registerModalPointerShield",
 			"resolveFullscreenLayout",
 		]);
-		const editor = await import("pi-libtui/editor");
+		const editor = await import("@luan.sh/pi-libtui/editor");
 		expect(Object.keys(editor).sort()).toEqual([
 			"EDITOR_PROTOCOL",
 			"EDITOR_REGISTRY_KEY",