@treeport/treeport 0.5.0 → 0.7.0

package/drizzle/meta/_journal.json

@@ -71,6 +71,34 @@
       "when": 1786800000000,
       "tag": "0009_open_folders",
       "breakpoints": true
+    },
+    {
+      "idx": 10,
+      "version": "6",
+      "when": 1787565462059,
+      "tag": "0010_browser_panels_and_permissions",
+      "breakpoints": true
+    },
+    {
+      "idx": 11,
+      "version": "6",
+      "when": 1787939530241,
+      "tag": "0011_free_magdalene",
+      "breakpoints": true
+    },
+    {
+      "idx": 12,
+      "version": "6",
+      "when": 1788000000000,
+      "tag": "0012_terminal_host_cutover",
+      "breakpoints": true
+    },
+    {
+      "idx": 13,
+      "version": "6",
+      "when": 1788100000000,
+      "tag": "0013_workspace_item_order",
+      "breakpoints": true
     }
   ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@treeport/treeport",
-  "version": "0.5.0",
+  "version": "0.7.0",
   "description": "A tree-first terminal driver for persistent development workspaces.",
   "type": "module",
   "bin": {
@@ -35,23 +35,29 @@
     "access": "public"
   },
   "dependencies": {
-    "@hono/node-server": "^2.0.10",
-    "@hono/zod-validator": "^0.9.0",
+    "@effect/opentelemetry": "^0.64.0",
+    "@effect/platform": "^0.97.1",
+    "@effect/platform-node": "^0.108.1",
+    "@effect/rpc": "^0.76.2",
     "@libsql/client": "^0.17.4",
+    "@opentelemetry/sdk-trace-base": "^2.11.0",
+    "@opentelemetry/sdk-trace-node": "^2.11.0",
+    "@playwright/cli": "0.1.18",
     "@radix-ui/react-context-menu": "^2.3.7",
     "@vitejs/plugin-react": "5.2.0",
-    "@xterm/headless": "^6.0.0",
+    "@xterm/addon-serialize": "0.15.0-beta.301",
+    "@xterm/headless": "6.1.0-beta.303",
+    "cmdk": "^1.1.1",
     "commander": "14.0.3",
     "drizzle-orm": "^0.45.2",
-    "effect": "^3.22.0",
-    "hono": "^4.11.7",
+    "effect": "^3.22.1",
     "jsonc-parser": "^3.3.1",
     "node-pty": "1.2.0-beta.14",
-    "socket.io": "4.8.3",
-    "socket.io-client": "4.8.3",
+    "playwright": "1.61.1",
     "vite": "8.1.5",
+    "ws": "^8.21.1",
     "zod": "^4.3.6",
-    "@treeport/panel-sdk": "0.5.0"
+    "@treeport/panel-sdk": "0.7.0"
   },
   "devDependencies": {
     "@fontsource-variable/inter": "^5.2.8",
@@ -68,9 +74,11 @@
     "@tanstack/react-router": "^1.170.18",
     "@types/react": "^19.2.10",
     "@types/react-dom": "^19.2.3",
-    "@xterm/addon-fit": "^0.11.0",
-    "@xterm/addon-web-links": "^0.12.0",
-    "@xterm/xterm": "^6.0.0",
+    "@types/ws": "^8.18.1",
+    "@xterm/addon-fit": "0.12.0-beta.301",
+    "@xterm/addon-image": "0.10.0-beta.301",
+    "@xterm/addon-web-links": "0.13.0-beta.301",
+    "@xterm/xterm": "6.1.0-beta.304",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
     "drizzle-kit": "^0.31.10",
@@ -89,7 +97,7 @@
     "build:node": "tsdown",
     "build:web": "vite build",
     "check:package": "node scripts/check-package.mjs",
-    "test:package": "node scripts/smoke-package.mjs",
+    "test:package": "node scripts/smoke-package.mjs && node scripts/smoke-upgrade.mjs",
     "dev": "node scripts/development.mjs",
     "dev:server": "rm -rf .treeport-dev-dist && TREEPORT_DATA_DIR=.treeport-dev/data TREEPORT_RUNTIME_DIR=.treeport-dev/runtime TREEPORT_DAEMON_LIFECYCLE=external tsdown --watch --out-dir .treeport-dev-dist",
     "start": "TREEPORT_WEB_DIST=dist/web node dist/node/server/index.js",

package/skills/treeport/SKILL.md

@@ -1,12 +1,14 @@
 ---
 name: treeport
-description: Understand Treeport-managed terminal context and safely create persistent, observable terminals and child trees with the Treeport CLI. Use when an agent or extension needs to inspect its Treeport environment, open another session, or spawn work in a separate tree.
+description: Detailed Treeport CLI guidance for child-tree orchestration, lifecycle, services, remote access, updates, and recovery. Use when compact Pi guidance or command help is not sufficient. Do not load for routine background processes or browser tabs in a managed Pi session.
 compatibility: Requires the treeport CLI on PATH and a reachable Treeport daemon. Creation commands also require the requested child executable to be installed.
 ---
 
 # Treeport
 
-Treeport is a generic terminal and tree layer. Its terminals are persistent tmux sessions that appear in the Treeport UI. A user can open a created terminal, take control of the normal application TUI, and continue working in the same session.
+In a managed Pi session, use the injected CLI guidance for routine terminal and browser operations. Load this skill only when you need more detail.
+
+Treeport is a generic terminal and tree layer. Its persistent terminals are owned by Treeport's detached terminal host and appear in the Treeport UI. A user can open a created terminal, take control of the normal application TUI, and continue working in the same session.
 
 Treeport does not define task sources, planning or approval states, agent tool policies, or provider-specific workflows. The caller owns names, commands, prompts, and higher-level orchestration.
 
@@ -21,7 +23,7 @@ Treeport does not define task sources, planning or approval states, agent tool p
 - When the lifecycle is `external`, never run `treeport start`, `treeport stop`, or `treeport remote enable`.
 - In the external lifecycle, the parent process owns startup, shutdown, and remote exposure.
 - When the lifecycle is `service`, normal `start` and `stop` delegate to the OS manager.
-- Use bare `treeport update` to update a supported local npm installation. It preserves tmux terminals and an enabled service, and restarts only a daemon that was running.
+- Use bare `treeport update` to update a supported local npm installation. It preserves hosted terminals and an enabled service, and restarts only a daemon that was running.
 - Never run bare `treeport update` for an external or selected remote daemon.
 - Never invoke `sudo` for a normal service or update operation.
 - Normal macOS service mode is a user/login LaunchAgent and does not need an administrator.
@@ -37,7 +39,7 @@ Run:
 treeport context
 ```
 
-Inside a managed terminal, this reports the current project, tree, terminal, paths, statuses, IDs, and daemon URL. It reports whether Treeport, the OS service, or an external process manages the daemon lifecycle. It resolves the injected IDs strictly. It does not guess identity from the current path.
+Inside a managed terminal, this reports the current project, tree, terminal, paths, statuses, IDs, tree context values, and daemon URL. User-supplied context can contain an issue identifier, a task description, or other information for the tree. Use these values as task input when the caller asks you to work from the tree context. It reports whether Treeport, the OS service, or an external process manages the daemon lifecycle. It resolves the injected IDs strictly. It does not guess identity from the current path.
 
 Outside Treeport it reports that the terminal is not managed and exits successfully. `TREEPORT_API_URL` may be configured outside a managed terminal; if any context ID is present, however, all injected values are required. Partial IDs or IDs that no longer belong together fail instead of falling back to path inference.
 
@@ -59,7 +61,7 @@ Launch a program directly:
 treeport terminal create --worktree <tree-id> --name <terminal-name> -- <program> <arg> ...
 ```
 
-The command returns after Treeport creates the tmux session. The program continues independently of the browser and of the caller that created it.
+The command returns after the detached terminal host creates the session. The program continues independently of the browser, API daemon, and caller that created it.
 
 ## Create a child tree and terminal
 
@@ -80,7 +82,7 @@ Treeport serializes tree mutations per project. If a caller needs several child
 
 ## Interpret creation results
 
-A successful `terminal create` means the tmux session was created. The requested program can still exit later.
+A successful `terminal create` means the hosted terminal was created. The requested program can still exit later.
 
 `spawn` is intentionally non-atomic after Git creates the worktree:
 
@@ -133,6 +135,60 @@ treeport terminal wait <terminal-id> --until exit
 
 Treeport does not infer agent settlement. An orchestrator can inspect first, wait for `working` if no progress cycle has been observed, and then wait for `idle`. Progress depends on the child application emitting OSC `9;4`; for Pi, `terminal.showTerminalProgress` must be enabled. Applications should clear progress or refresh active progress more frequently than the five-minute lease. A null progress value is not proof that every application supports progress reporting.
 
+## Inspect the worktree application in a browser tab
+
+The Browser primitive has one live runtime for each browser tab.
+
+Electron owns the visible `<webview>` page for a local desktop connection.
+
+Playwright controls managed Chromium for a web or remote desktop connection.
+
+Never attach Treeport to a personal browser profile.
+
+First, inspect the available browser tabs:
+
+```sh
+treeport browser list
+```
+
+If no browser tab is open, open one in the current tree:
+
+```sh
+treeport browser open --worktree .
+```
+
+Use these commands on the current live page:
+
+```sh
+treeport browser snapshot
+treeport browser click e12
+treeport browser fill e14 "value"
+treeport browser press Enter
+treeport browser console
+treeport browser network
+treeport browser screenshot
+```
+
+The commands select the only browser tab in the current tree.
+
+When more than one browser tab exists, add `--panel <panel-id>`.
+
+Snapshot references belong to one runtime generation.
+
+Take a new snapshot after navigation or a runtime change.
+
+A local desktop owner does not need managed Chromium.
+
+If no local owner exists, check managed Chromium before daemon automation:
+
+```sh
+treeport browser status
+```
+
+Ask the user before you run `treeport browser install`.
+
+Leave the browser tab open so the user can inspect the result.
+
 ## Automation and integrations
 
 Extensions and scripts should add `--json` before the `--` command separator: