summrise-agent 1.2.480 → 1.2.481

package/README.md

@@ -6,18 +6,41 @@ package; the `summrise` CLI manages setup, updates and the tunnel.
 
 ## Install (fresh device)
 
+**Two ways, and the first needs neither Node nor npm.**
+
+### One file (a clean Windows machine)
+
+Download and run **[SummriseAgent-Setup.exe](https://agent.saisi.online/summrise-agent/SummriseAgent-Setup.exe)**.
+It is self-contained — the release's own package is embedded, so it needs no network for the agent itself — and it
+elevates itself, writes the registry keys, registers both scheduled tasks and starts the agent. If the machine has no
+Node >= 18 it fetches a portable one; if it has one, it reuses it and leaves it alone.
+
+### Through npm
+
 ```powershell
 npm i -g https://agent.saisi.online/summrise-agent/summrise-agent-latest.tgz
 summrise setup --reg-key <key-from-console>   # --reg-key is optional (local mode works without it)
 ```
 
+**Run `setup` from an elevated PowerShell.** The install directory is under `Program Files` and the registry key is
+`HKLM`, so a normal shell fails with `EPERM: operation not permitted, mkdir 'C:\Program Files\Summrise\scripts'` —
+a stack trace where the useful sentence is "run it as administrator".
+
+**In PowerShell, `summrise` resolves to npm's `.ps1` shim, which the default execution policy blocks**
+(*"无法加载文件 …summrise.ps1，因为在此系统上禁止运行脚本"*). **Use `summrise.cmd <command>`**, which bypasses the
+policy and changes nothing on the machine — or `Set-ExecutionPolicy -Scope CurrentUser RemoteSigned`, once.
+
+The device's name is written to `etc\summrise-agent.hostname` and defaults to **this machine's `%COMPUTERNAME%`**
+(lower-cased, under `.agent.saisi.online`). `setup --hostname <name>` overrides it; the name is what the console lists
+the device as and what its tunnel is called.
+
 `setup` installs to the registry-configured directory
 (`HKLM\SOFTWARE\Summrise\Agent\InstallDir`), registers the boot-start
 `SummriseAgent` scheduled task as SYSTEM (no execution-time limit,
 restart-on-failure ×8, 5-min repetition watchdog) and starts it. With a
 registration key the device registers itself with a Summrise Gate console.
 
-## Update (one click)
+## Update (two steps, in this order)
 
 ```powershell
 npm i -g --prefix (Split-Path (Get-Command summrise).Source) https://agent.saisi.online/summrise-agent/summrise-agent-latest.tgz
@@ -47,6 +70,21 @@ tree → copy with retry → restart task. The terminal connection
 drops ~10 s; reconnect afterwards. Even a failed copy restarts the task —
 the device is never left dark.
 
+## Gateway and tunnel
+
+A device is useful locally with no cloud at all. Pointing it at a Summrise Gate console adds remote access, and the
+**Gateway** card in the panel is where that happens: the console URL, an optional registration key, and **Save &
+connect**.
+
+The tunnel is provisioned **through the Cloudflare API**, which matters because the alternative does not work on a
+service: `cloudflared tunnel login` is INTERACTIVE — a browser, a human and a zone — so a device running as SYSTEM can
+never produce the `cert.pem` that `cloudflared tunnel create` and `cloudflared tunnel route dns` require. Every one of
+those steps now goes through the API instead, including finding a tunnel that already exists (the API answers
+`1013 You already have a tunnel with this name`, which is success, not failure).
+
+If a connect attempt fails, the panel's message carries the API's own reply, and the agent's log at
+`<DataDir>\logs\agent.log` carries more — `<DataDir>` is `HKLM\SOFTWARE\Summrise\Agent\DataDir`.
+
 ## CLI commands
 
 ```
@@ -57,11 +95,18 @@ summrise <setup|status|start|stop|restart|update|uninstall|run|tunnel>
 
 - **OSC 633 shell integration** (VS Code approach): PowerShell prompts and
   command boundaries arrive as invisible sequences — clean display, exit codes.
-- **56 MCP tools**: terminal (27: PTY/SSH/serial, history with exit codes, SFTP,
-  saved connections, secrets, background jobs), system (9), memory (6),
-  mcp-client (4), monitor (4), playwright (2), runs (2), update (agent_update),
-  design (page_view). Measured from `agent/spec-tools.json`, which
-  `cargo test spec_snapshot` regenerates from the live registry.
+- **MCP tools** for the terminal (PTY/SSH/serial, history with exit codes, SFTP,
+  saved connections, secrets, background jobs), the system, memory, the browser,
+  monitors, runs and updates. **Count them rather than trusting this file:**
+
+  ```bash
+  grep -oE '"name": *"[a-z_]+"' agent/spec-tools.json | sed 's/.*"\(.*\)"/\1/' | sort -u | wc -l
+  ```
+
+  (It answers **57** today. This section used to state a number and a per-plugin
+  breakdown, and both had gone stale — a hand-written count is a claim nothing
+  re-checks, and the command above is one line.) `agent/spec-tools.json` is
+  regenerated from the live registry by `cargo test spec_snapshot`.
 - **Electron desktop shell**: tray with live agent status, native menu,
   CDP :9333 for AI-driven UI.
 - **Memory plugin**: device-local knowledge base with multi-word search and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "summrise-agent",
-  "version": "1.2.480",
+  "version": "1.2.481",
   "description": "Summrise Agent — Windows device MCP server (terminal/SSH/serial) + panel. Self-hosted npm distribution.",
   "//build": "唯一构建路径：在本目录执行 npm run build。它是自包含的：经 npm exec 按需拉取 typescript@5，无需预装任何 node_modules（干净检出可跑；旧脚本引用 ../summrise-desktop-electron/node_modules/.bin/tsc，干净检出必 ENOENT）。必须用 npm exec --package … -- tsc 的形式：npx 会吃掉传给 tsc 的 -p/--outDir 等参数（round-435：npx 写法从未真正跑通过）。先编 electron TS（--noCheck 纯 emit，与 release.yml 一致）同步两处 src/*.js，再编 src/summrise.ts 到 bin/summrise.js 并校验 round-298 标记（弱 oracle，只证某次构建发生，新鲜性由 publish-release.sh 的 tsc 重编 + cmp 门保证）。",
   "bin": {