@cydm/pie 2.1.0 → 2.1.1

package/README.md

@@ -317,7 +317,7 @@ Run `pie doctor` to check whether chrome-devtools-axi and a Chrome browser are d
 
 ## Terminal UI Automation
 
-The built-in `tui-use` skill drives interactive terminal programs - REPLs, pdb/gdb debugger sessions, and full-screen TUI apps - through a PTY: read the screen as text, send keystrokes, and wait for output with `wait`/`wait --text`. Pie ships only the skill definition; the CLI runs on demand via `npx -y --install-strategy=nested tui-use@0.1.20` (the version tag in the skill is the lock). Use plain `bash` for anything non-interactive. First invocation installs the PTY runtime (macOS/Windows prebuilt; Linux compiles node-pty from source) and starts a session daemon (state in `~/.tui-use`); Windows ConPTY is not officially verified upstream.
+The built-in `tui-use` skill drives interactive terminal programs - REPLs, pdb/gdb debugger sessions, and full-screen TUI apps - through Pie's packaged PTY runtime. Run `node <skill-baseDir>/tui-use-cli.js --help`; no first-use dependency download or global CLI is required. Windows uses native PowerShell and ConPTY. State lives in `~/.pie/tui-use`, or a dedicated `PIE_TUI_USE_STATE_DIR`. Always target sessions with `--session <id>`, confirm termination with `wait --exit`, and clean up only sessions and daemons you own. Use plain `bash` for non-interactive commands.
 
 ## Desktop Control (computer-use)
 
@@ -325,7 +325,8 @@ The built-in `computer-use` extension (vendored from `@injaneity/pi-computer-use
 
 Tools are tiered:
 
-- **Observe tier (default)** - `find_roots`, `observe_ui`, `search_ui`, `expand_ui`, `inspect_ui`, `read_text`, `wait_for`, plus the CDP browser tools `launch_browser`, `navigate_browser`, `evaluate_browser`. These only read screen/UI state.
+- **Observe tier (default)** - `find_roots`, `observe_ui`, `search_ui`, `expand_ui`, `inspect_ui`, `read_text`, `wait_for` read screen/UI state.
+- **Browser tier (default)** - `launch_browser`, `navigate_browser`, `evaluate_browser` control a managed CDP context. Navigation and JavaScript evaluation can have side effects; these are not read-only tools.
 - **Act tier (first-use confirmation)** - `act_ui` synthesizes real input (click, type, scroll, keypress, drag). The first `act_ui` call in each session asks for confirmation (class `computer_use_act`); YOLO mode bypasses it, and non-interactive hosts block it deterministically.
 
 Platform notes:
@@ -412,7 +413,9 @@ npm run verify:terminal:matrix
 
 Use `npm run verify:agent` when model credentials are available and you want the real daily agent gate.
 Use `npm run verify:agent:nightly` before release candidates that claim real-provider reliability.
-Use `UNITY_EDITOR="/path/to/Unity" npm run verify:unity:reliability` before Unity release candidates. For live Unity Dev RPC coverage, run `PIE_UNITY_REAL_RPC=1 UNITY_EDITOR="/path/to/Unity" npm run verify:unity:reliability`.
+Unity checks in the default chain are offline tests and static package/bundle
+checks only. Real Editor, reload, Play Mode, and Player verification use the
+manual checklist in `products/pie-unity/TESTING.md`, not an automated Unity gate.
 Set `PIE_REAL_BROWSER=1` when you want `verify:browser` to open a real browser session instead of only checking the chrome-devtools-axi CLI contract.
 Set `PIE_REAL_WEB=1` when you want `verify:web` to run real provider web research smoke with fetched or browser-read citations.
 

package/dist/builtin/extensions/ask-user/index.js

@@ -1,7 +1,7 @@
 import { createRequire as __createRequire } from "node:module"; const require = __createRequire(import.meta.url);
 import {
   createAskUserCapability
-} from "../../../chunks/chunk-PMPD56N2.js";
+} from "../../../chunks/chunk-LU7RKALH.js";
 import "../../../chunks/chunk-QJH6YN2W.js";
 import "../../../chunks/chunk-IM43UYVV.js";
 import "../../../chunks/chunk-XXGYUYXI.js";