pi-link 0.1.15-beta.0 → 0.1.15

package/CHANGELOG.md

@@ -6,9 +6,25 @@ This changelog is based on the git history from `2026-03-21` (initial commit) th
 
 ---
 
-## 0.1.15-beta.0 — 2026-05-17
+## 0.1.15 — 2026-05-18
 
-Beta release for the 0.1.15 cycle. Install with `npm i -g pi-link@beta` for soak; `npm i -g pi-link` continues to install 0.1.14. Promotion to `latest` after smoke + at least one external user confirmation.
+Stable release for the 0.1.15 cycle, promoted after beta soak.
+
+### Install note for Pi 0.75+
+
+Pi 0.75 installs Pi packages under `~/.pi/agent/npm/`, so `pi install npm:pi-link` still enables the in-Pi extension features (`/link*`, tools, `--link`) but no longer puts the `pi-link` shell launcher on PATH.
+
+If you use `pi-link <name>` from your shell, also install the launcher globally:
+
+```sh
+npm i -g pi-link
+```
+
+Users who only use pi-link inside Pi do not need this extra step. Background: [pi-mono#4587](https://github.com/earendil-works/pi-mono/issues/4587).
+
+### Breaking
+
+- **Pi 0.74+ is now required.** pi-link now uses the `@earendil-works/*` Pi package namespace. Users on Pi ≤0.73 should pin `pi-link@0.1.14`.
 
 ### Added
 
@@ -22,21 +38,21 @@ Beta release for the 0.1.15 cycle. Install with `npm i -g pi-link@beta` for soak
 
 ### Changed
 
+- **Removed Pi peer dependencies from `package.json`.** Pi provides its own extension APIs at load time; declaring them as npm peers caused unnecessary install warnings and duplicate package installs. `ws` remains the only runtime dependency.
 - **`pi-link --resolve <missing-name>` now exits with code `2`** (was `0`). Single match still exits `0`; ambiguous still exits `1`; not found is now distinguishable from success in scripts. The legacy `pi-link resolve <missing-name>` form gets the same fix.
 - **`pi-link <name> <extra-positional>` now errors** instead of silently passing the extra to Pi as a prompt. Catches typos like `pi-link resolv foo`. Tokens that follow a flag without `=` are still accepted as that flag's value (e.g. `pi-link worker --model opus` works). Use `--` to pass bare positionals through unchanged: `pi-link worker -- some-arg`.
 - **`pi-link foo --help` now errors** with "cannot combine session name and --help" instead of silently passing `--help` to Pi. Run `pi --help` for Pi's own help.
+- **Published tarball trimmed to 7 files.** Explicit `files` allowlist so internal planning artifacts and the test harness no longer ship to npm.
 
 ### Deprecated
 
-- **`pi-link list` and `pi-link resolve` subcommands.** Use `--list` / `--resolve` instead. Subcommands still work for one release with a stderr deprecation warning, then will be removed. The `--global` flag placement is more flexible in the deprecated `resolve` form than the canonical `--resolve` form: `pi-link resolve --global foo` is still accepted, while `pi-link --resolve --global foo` is an error (use `pi-link --resolve foo --global` or `--resolve=foo --global`).
+- **`pi-link list` and `pi-link resolve` subcommands.** Use `--list` / `--resolve` instead. Subcommands still work for one release with a stderr deprecation warning, then will be removed.
 
-### Fixed
-
-- **Pi-bundled imports now declared as peer dependencies.** `package.json` adds `@mariozechner/pi-coding-agent`, `@mariozechner/pi-tui`, and `typebox` as `peerDependencies` with `"*"` ranges, matching Pi's `docs/packages.md` convention for packages that import Pi-bundled modules. Previously only `ws` was declared, so consumers whose toolchain didn't auto-resolve modules through Pi's loader (e.g. some Docker setups) hit `ERR_MODULE_NOT_FOUND` on `typebox`. With modern npm/pnpm, peer deps auto-install alongside the package; older toolchains may need explicit `npm install`.
+### Migration from 0.1.14
 
-### Migration
+Existing launcher aliases keep working for this release, but deprecated `list` / `resolve` subcommands now print a stderr warning.
 
-All existing scripts and aliases continue to work — the deprecated subcommands print a stderr warning but produce identical output (and the new exit-code 2 on missing resolve). Scripts that depended on `pi-link resolve <name>` returning exit 0 for missing names need updating to handle 2. Most callers already treated empty stdout as "not found" and will be unaffected.
+One behavior change may affect scripts: `pi-link resolve <missing>` now exits `2` instead of `0`, so callers that trusted exit `0` to mean "found" should update their handling.
 
 To silence the deprecation warning, switch to the flag form:
 
@@ -48,9 +64,15 @@ To silence the deprecation warning, switch to the flag form:
 | `pi-link resolve foo -g`       | `pi-link --resolve foo -g`                                         |
 | `pi-link resolve --global foo` | `pi-link --resolve foo --global` (order matters in canonical form) |
 
-### Test coverage
+---
+
+## 0.1.15-beta.0 — 2026-05-17 _(pulled — do not install)_
+
+Initial 0.1.15 beta, superseded by `0.1.15`.
+
+**Issue:** peer dependencies still pointed at the old `@mariozechner/*` namespace, causing npm to install deprecated Pi 0.73 packages on Pi 0.74+ systems.
 
-40 automated cases in `test/cli-flags-test.mjs` covering: canonical forms (5), deprecation aliases (4), orphan-positional rejection (7), mode-selecting validation (11), help / unknown / managed-flag rejection (8), wrapper-vs-pi flag boundaries (4). Cases that exercise the launch path use a stubbed `pi` on PATH that records argv + `PI_LINK_NAME`. Run with `node test/cli-flags-test.mjs`.
+**Resolution:** stable `0.1.15` uses the `@earendil-works/*` runtime imports and removes Pi npm peer dependencies.
 
 ---
 

package/README.md

@@ -36,7 +36,7 @@ A single Pi terminal is powerful. Multiple terminals working together unlock new
 
 ## Prerequisites
 
-- [Pi coding agent](https://github.com/badlogic/pi-mono) installed and working
+- [Pi coding agent](https://github.com/badlogic/pi-mono), version **0.74 or later** (for pi-link 0.1.15+). On Pi ≤0.73, pin `pi-link@0.1.14`.
 - Node.js (LTS recommended)
 
 ---
@@ -45,14 +45,37 @@ A single Pi terminal is powerful. Multiple terminals working together unlock new
 
 ### Install
 
+The minimum install — enables every in-Pi feature (`/link`, `link_send`, `link_prompt`, `/link-connect`, `--link` flag, auto-resume, all LLM tools):
+
 ```bash
 pi install npm:pi-link
 ```
 
+That's it. For most users this is all you need.
+
+#### Optional: shell launcher
+
+If you also want the `pi-link <name>` shell command to start named sessions from a terminal prompt (e.g. `pi-link builder` in one window, `pi-link reviewer` in another), install the CLI globally as well:
+
+```bash
+npm i -g pi-link
+```
+
+Or install both in one line:
+
+```bash
+pi install npm:pi-link && npm i -g pi-link
+```
+
+The shell launcher is convenience-only — you can always reach the same functionality from inside Pi via `/link-connect <name>` and `/link-name <name>`.
+
+> **Why two installs?** Pi 0.75 installs Pi packages into a private npm root (`~/.pi/agent/npm/`) for safer permission handling ([pi-mono#4587](https://github.com/earendil-works/pi-mono/issues/4587)). That's where the Pi extension lives, but it means the `pi-link` shell command is no longer on system PATH. `npm i -g pi-link` puts it on PATH separately. Both installs are safe to use together.
+
 ### Uninstall
 
 ```bash
-pi uninstall npm:pi-link
+pi uninstall npm:pi-link      # Remove Pi extension
+npm uninstall -g pi-link      # Remove CLI launcher (if you installed it)
 ```
 
 ### Usage
@@ -431,11 +454,13 @@ When the hub goes down and a client promotes itself, terminal names and in-fligh
 
 ### Provided by Pi (no install needed)
 
-| Package                         | Purpose                                          |
-| ------------------------------- | ------------------------------------------------ |
-| `@mariozechner/pi-coding-agent` | Pi SDK types (ExtensionAPI, ExtensionContext)    |
-| `@mariozechner/pi-tui`          | TUI Text widget for custom message rendering     |
-| `typebox`                       | JSON Schema type definitions for tool parameters |
+| Package                           | Purpose                                          |
+| --------------------------------- | ------------------------------------------------ |
+| `@earendil-works/pi-coding-agent` | Pi SDK types (ExtensionAPI, ExtensionContext)    |
+| `@earendil-works/pi-tui`          | TUI Text widget for custom message rendering     |
+| `typebox`                         | JSON Schema type definitions for tool parameters |
+
+> **Pi version requirement:** pi-link 0.1.15+ requires Pi 0.74 or later (the `@earendil-works/*` namespace). Users on Pi 0.73 or earlier should pin `pi-link@0.1.14`.
 
 ### `package.json`
 

package/index.ts

@@ -13,8 +13,8 @@
 import type {
   ExtensionAPI,
   ExtensionContext,
-} from "@mariozechner/pi-coding-agent";
-import { Text } from "@mariozechner/pi-tui";
+} from "@earendil-works/pi-coding-agent";
+import { Text } from "@earendil-works/pi-tui";
 import { Type } from "typebox";
 import * as crypto from "node:crypto";
 import * as os from "node:os";

package/package.json

@@ -1,12 +1,20 @@
 {
   "name": "pi-link",
-  "version": "0.1.15-beta.0",
+  "version": "0.1.15",
   "description": "WebSocket-based inter-terminal communication for Pi. Connect multiple Pi terminals over a local link network.",
   "author": "alvivar",
   "license": "MIT",
   "bin": {
     "pi-link": "bin/pi-link.mjs"
   },
+  "files": [
+    "bin",
+    "skills",
+    "index.ts",
+    "README.md",
+    "CHANGELOG.md",
+    "LICENSE"
+  ],
   "repository": {
     "type": "git",
     "url": "git+https://github.com/alvivar/pi-link.git"
@@ -22,11 +30,6 @@
   "dependencies": {
     "ws": "^8.20.0"
   },
-  "peerDependencies": {
-    "@mariozechner/pi-coding-agent": "*",
-    "@mariozechner/pi-tui": "*",
-    "typebox": "*"
-  },
   "devDependencies": {
     "@types/ws": "^8.18.1"
   },