@pify/cli 0.1.1 → 0.1.2

package/README.md

@@ -1,11 +1,8 @@
 # @pify/cli
 
-Front door for the [Pify](https://github.com/pifydev) suite: install and update the
-[pi coding agent](https://github.com/earendil-works/pi), manage the `@pify/*`
-extension packages with short names, and scaffold new Pi Packages.
+Front door for the [Pify](https://github.com/pifydev) suite: install and update the [pi coding agent](https://github.com/earendil-works/pi), manage the `@pify/*` extension packages with short names, and scaffold new Pi Packages.
 
-> Not to be confused with the unscoped npm package `pify` (sindresorhus's
-> promisify library) — unrelated.
+> Not to be confused with the unscoped npm package `pify` (sindresorhus's promisify library) — unrelated.
 
 ## Install
 
@@ -34,29 +31,17 @@ pify doctor                # diagnose node / npm / pi / settings
 pify init my-extension     # scaffold a new Pi Package
 ```
 
-Every command supports `--help`; `install`/`remove`/`update` support `--dry-run`;
-`list`/`doctor` support `--json`.
+Every command supports `--help`; `install`/`remove`/`update` support `--dry-run`; `list`/`doctor` support `--json`.
 
 ## How it relates to `pi`
 
-`pify` deliberately does **not** replace pi's package manager. Every package
-operation delegates to `pi install` / `pi remove` / `pi update`, which own
-`~/.pi/agent/settings.json` and the extension npm workspace — pify never edits
-pi's settings. What `pify` adds:
-
-- **Bootstrap** — `pi update` can't run when pi isn't installed yet; `pify setup`
-  closes that gap (`npm install -g --ignore-scripts @earendil-works/pi-coding-agent`,
-  matching pi's own self-update invocation).
-- **Catalog** — `@pify/*` short names, discovery (including packages that are
-  planned but not yet published), and install state at a glance.
-- **One-pass update** — `pify update` chains pi's self-update with per-package
-  updates of everything from this org, without touching non-Pify packages you
-  manage separately.
+`pify` deliberately does **not** replace pi's package manager. Every package operation delegates to `pi install` / `pi remove` / `pi update`, which own `~/.pi/agent/settings.json` and the extension npm workspace — pify never edits pi's settings. What `pify` adds:
+
+- **Bootstrap** — `pi update` can't run when pi isn't installed yet; `pify setup` closes that gap (`npm install -g --ignore-scripts @earendil-works/pi-coding-agent`, matching pi's own self-update invocation).
+- **Catalog** — `@pify/*` short names, discovery (including packages that are planned but not yet published), and install state at a glance.
+- **One-pass update** — `pify update` chains pi's self-update with per-package updates of everything from this org, without touching non-Pify packages you manage separately.
 - **Doctor** — environment sanity checks for support requests.
-- **Scaffolding** — `pify init` emits a correctly-shaped Pi Package: raw
-  TypeScript entry (no build step; pi loads `.ts` via jiti), host packages as
-  optional `peerDependencies`, `files` allowlist that actually ships the
-  sources, and a lifecycle-correct extension factory.
+- **Scaffolding** — `pify init` emits a correctly-shaped Pi Package: raw TypeScript entry (no build step; pi loads `.ts` via jiti), host packages as optional `peerDependencies`, `files` allowlist that actually ships the sources, and a lifecycle-correct extension factory.
 
 ## Packages
 
@@ -74,16 +59,9 @@ pi's settings. What `pify` adds:
 | `@pify/workflow` | Deterministic multi-step agent workflows |
 | `@pify/yolo` | Auto-approve everything, with an undo trail |
 
-The catalog ships inside the CLI and refreshes (at most daily) from
-[`catalog.json` on `main`](https://github.com/pifydev/cli/blob/main/catalog.json),
-so newly published packages appear without a CLI update. A fetched catalog is
-validated before use — every entry must stay inside the `@pify` scope — and any
-invalid document is discarded entirely. Overrides: `PIFY_CATALOG_URL` (remote
-URL), `PIFY_OFFLINE=1` or `PI_OFFLINE=1` (skip all network lookups).
+The catalog ships inside the CLI and refreshes (at most daily) from [`catalog.json` on `main`](https://github.com/pifydev/cli/blob/main/catalog.json), so newly published packages appear without a CLI update. A fetched catalog is validated before use — every entry must stay inside the `@pify` scope — and any invalid document is discarded entirely. Overrides: `PIFY_CATALOG_URL` (remote URL), `PIFY_OFFLINE=1` or `PI_OFFLINE=1` (skip all network lookups).
 
-Explicit `@pify/<name>` arguments bypass the catalog's published/planned gate
-(with a warning), so a freshly published package is installable before the
-catalog propagates.
+Explicit `@pify/<name>` arguments bypass the catalog's published/planned gate (with a warning), so a freshly published package is installable before the catalog propagates.
 
 ## Exit codes
 
@@ -96,9 +74,7 @@ catalog propagates.
 | 4 | Not found (unknown catalog name; not yet published; not installed) |
 | 5 | A delegated `pi`/`npm` subprocess exited non-zero |
 
-Colored output respects `NO_COLOR`, `FORCE_COLOR`, `--no-color`, and non-TTY
-pipes. Results go to stdout; warnings and errors go to stderr. No interactive
-prompts anywhere — behavior is identical in TTY and CI except color.
+Colored output respects `NO_COLOR`, `FORCE_COLOR`, `--no-color`, and non-TTY pipes. Results go to stdout; warnings and errors go to stderr. No interactive prompts anywhere — behavior is identical in TTY and CI except color.
 
 ## Development
 
@@ -109,8 +85,7 @@ npm test           # builds first, then node --test
 npm run typecheck
 ```
 
-Requires Node >= 22.19.0 (same floor as the pi coding agent).
-Tested with pi 0.84.4.
+Requires Node >= 22.19.0 (same floor as the pi coding agent). Tested with pi 0.84.4.
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pify/cli",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Front door for the Pify suite: install and update the pi coding agent, manage @pify packages, and scaffold Pi Packages",
   "keywords": [
     "pify",