@qialike/cli 0.8.1 → 0.9.0

package/README.md

@@ -15,11 +15,26 @@ Terminal client for **DeepSeek Harness** — a full-screen TUI over an agent ses
 
 ## Install (Windows)
 
-```sh
+Node.js **≥ 18** is required — it ships the `npm` used below. Install it first (the terminal must be
+reopened afterwards so PATH picks it up), then install this package:
+
+```powershell
+winget install OpenJS.NodeJS.LTS     # or download the LTS installer from https://nodejs.org/
+node --version                       # reopen the terminal, then check both
+npm --version
 npm i -g @qialike/cli
 qialike --version
 ```
 
+On Windows npm's global prefix is `%APPDATA%\npm` — inside your user profile, and on the user PATH
+already — so this needs **no administrator rights**.
+
+**Run it inside the Windows Terminal app**, not the legacy console window that `cmd.exe` /
+`powershell.exe` open on their own: qialike draws 24-bit colour, `▀▄█` half-block art, emoji and a
+flat cursor, and it takes mouse input — Windows Terminal handles all of that, the old console host
+handles it poorly. Install it with `winget install Microsoft.WindowsTerminal` (Windows 11 ships it),
+then open a PowerShell or cmd tab there — the shell is still your choice.
+
 **You do not choose an architecture.** The package declares one optional dependency per Windows
 target — `@qialike/cli-win32-x64` and `@qialike/cli-win32-arm64` — each restricted with `os`/`cpu`,
 so npm downloads only the payload that matches your machine (x64 or arm64), never both.
@@ -31,9 +46,25 @@ an interrupted install all leave the launcher without a binary. It then prints t
 install the package for your architecture, for example:
 
 ```sh
-npm i -g @qialike/cli-win32-arm64@0.8.1
+npm i -g @qialike/cli-win32-arm64@0.9.0
 ```
 
+The version is pinned to the one you already have: a bare `npm i -g
+@qialike/cli-win32-arm64` can resolve a platform package that does not match the parent that sent
+you here. Use the version the launcher printed.
+
+## Uninstalling
+
+Two steps, because this package puts the program outside the harness home:
+
+```sh
+qialike uninstall                 # clears the harness home (state, settings, sessions)
+npm uninstall -g @qialike/cli     # removes the program itself
+```
+
+`qialike uninstall` prints that second command for you — it cannot run it, because the payload sits
+under your package manager's prefix rather than in `%USERPROFILE%\.dsh\bin`.
+
 ## Alternative installers
 
 - Shell installer (Linux, macOS): `curl -fsSL https://qialike.com/install | bash`

package/bin/qialike.js

@@ -150,7 +150,18 @@ if (!existsSync(exe)) {
 
 // Hand the terminal over: stdio is inherited, because the TUI owns raw mode,
 // colour and resize. The child's exit code is what the caller sees.
-const result = spawnSync(exe, process.argv.slice(2), { stdio: 'inherit' })
+//
+// `QIALIKE_INSTALLED_VIA` tells the program it was reached through a package
+// manager. It matters for exactly one thing: `qialike uninstall` clears the
+// harness home, but THIS copy lives under the manager's prefix (npm's
+// %APPDATA%\npm\node_modules\…), so only `npm uninstall -g @qialike/cli` can
+// remove it — and nothing in the home hints that the copy came from npm rather
+// than from the shell installer. The launcher is the one component that knows,
+// so it says so.
+const result = spawnSync(exe, process.argv.slice(2), {
+  stdio: 'inherit',
+  env: { ...process.env, QIALIKE_INSTALLED_VIA: 'npm' },
+})
 
 if (result.error) {
   const reason = result.error instanceof Error ? result.error.message : String(result.error)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@qialike/cli",
-  "version": "0.8.1",
+  "version": "0.9.0",
   "description": "Terminal client for DeepSeek Harness. Installs the Windows binary for your architecture (x64 or arm64) automatically.",
   "license": "MIT",
   "repository": {
@@ -18,8 +18,8 @@
     "node": ">=18"
   },
   "optionalDependencies": {
-    "@qialike/cli-win32-x64": "0.8.1",
-    "@qialike/cli-win32-arm64": "0.8.1"
+    "@qialike/cli-win32-x64": "0.9.0",
+    "@qialike/cli-win32-arm64": "0.9.0"
   },
   "publishConfig": {
     "access": "public"