@pasko70/pibo 1.9.9 → 1.9.11

package/docs/ops/vscode-extension-release.md

@@ -1,160 +1,160 @@
-# Pibo VS Code Extension Release Runbook
-
-The Pibo VS Code extension is shipped as a `.vsix` artifact. This runbook describes the end-to-end release process and the split of responsibilities between the maintainer and the `pibo` release script.
-
-## Distribution channels
-
-The extension is published through two channels that are intentionally separate:
-
-| Channel | Owner | Cadence | What it carries |
-|---|---|---|---|
-| npm `@pasko70/pibo` | automated via `npm publish` (or the release script's `--publish-npm` flag) | every `main` commit that includes a version bump | the `pibo` CLI, the gateway, the WebView bundle at `dist/apps/chat-vscode-web/` |
-| VS Code Marketplace `pibo.pibo-vscode` | **maintainer uploads the VSIX manually** via <https://marketplace.visualstudio.com/manage> | every release that needs the extension UI updated | the `.vsix` produced by `npm run vscode:package` |
-
-The npm package and the Marketplace extension are versioned together. The release script bumps both `package.json` (npm) and `src/apps/chat-vscode/package.json` (extension) in one go so the published artifacts stay in lockstep.
-
-`pibo vscode install` (new since the distribution rework) downloads the VSIX from the GitHub Release for the configured repo (`Pascapone/pibo` by default). When the maintainer also uploads the same VSIX to the Marketplace, both channels serve identical bytes.
-
-## Versioning
-
-- The root `package.json#version` is the npm version. It follows [SemVer](https://semver.org/).
-- The extension's `src/apps/chat-vscode/package.json#version` is the Marketplace version. It is kept equal to the npm version (the release script enforces this).
-- A SemVer **minor** bump (e.g., `1.2.0` → `1.3.0`) is appropriate when the change is additive and backward-compatible. The distribution rework itself is a minor bump: existing `pibo` users are unaffected, and the new `pibo vscode install` command is opt-in.
-- A SemVer **major** bump is reserved for breaking changes to either the public CLI surface or the WebView host↔Web postMessage contract.
-
-## Release steps
-
-The release script does the heavy lifting. The maintainer's job is to review, commit, and push.
-
-### 1. Pick the version
-
-Decide on the next version. For the distribution rework that introduces `pibo vscode install`, the right bump is `1.2.0` → `1.3.0` (new CLI command, new marketplace-ready extension, no breaking changes).
-
-### 2. Bump + build + package (local)
-
-From the repo root:
-
-```bash
-node scripts/release.mjs --version 1.3.0
-```
-
-The script:
-
-1. Reads the current version from both `package.json` files.
-2. Writes the new version to both files.
-3. Runs `npm run build` (which includes the WebView build).
-4. Runs `npm run vscode:package` to produce `dist/apps/vscode-artifacts/pibo-vscode-1.3.0.vsix` and a stable `latest.vsix` copy.
-5. Prints the VSIX path and size.
-
-The script does **not** push to git or create a tag. The maintainer reviews the diff and commits it.
-
-### 3. Commit and tag
-
-```bash
-git add package.json src/apps/chat-vscode/package.json
-git commit -m "chore(release): bump @pasko70/pibo and pibo.pibo-vscode to 1.3.0"
-git tag -a v1.3.0 -m "@pasko70/pibo 1.3.0"
-git push origin main
-git push origin v1.3.0
-```
-
-### 4. Create a GitHub Release with the VSIX attached
-
-The maintainer's local machine has the `gh` CLI installed:
-
-```bash
-gh release create v1.3.0 \
-  dist/apps/vscode-artifacts/pibo-vscode-1.3.0.vsix \
-  --title "pibo 1.3.0" \
-  --notes "..."
-```
-
-In environments where `gh` is not available (e.g. the pibo compute workers),
-`scripts/create-github-release.mjs` performs the same action via the Pibo
-GitHub App, which has been installed on `Pascapone/pibo` with the
-`contents: write` scope. The script accepts the GitHub App credentials from
-`PIBO_GITHUB_APP_ID` and `PIBO_GITHUB_APP_KEY` environment variables, or
-from the well-known env file at
-`/root/.pibo/uploads/github-app.env` (with the PEM key auto-discovered
-next to it).
-
-```bash
-node scripts/create-github-release.mjs \
-  --tag v1.3.0 \
-  --asset dist/apps/vscode-artifacts/pibo-vscode-1.3.0.vsix
-```
-
-Both paths make the VSIX downloadable from a stable URL
-(`https://github.com/Pascapone/pibo/releases/download/v1.3.0/pibo-vscode-1.3.0.vsix`).
-The `pibo vscode install` command uses the GitHub Releases API to discover
-this URL automatically.
-
-The release script can also do this in one step:
-
-```bash
-node scripts/release.mjs --version 1.3.0 --create-release
-```
-
-…if the tag has already been pushed. Internally the release script calls
-`scripts/create-github-release.mjs`, so it works in worker environments
-without `gh`.
-
-### 5. Publish the npm package
-
-```bash
-npm publish
-```
-
-Or, in one go with the release script:
-
-```bash
-node scripts/release.mjs --version 1.3.0 --publish-npm --create-release
-```
-
-The publish step uploads the `pibo` CLI, the gateway plugins, and the WebView bundle. The Marketplace upload is intentionally **not** automated — see step 6.
-
-### 6. Upload the VSIX to the VS Code Marketplace (manual)
-
-The Marketplace does not currently accept a Personal Access Token from this account (Azure-side provisioning issue). The release is therefore finished by uploading the VSIX through the Marketplace web UI:
-
-1. Open <https://marketplace.visualstudio.com/manage>.
-2. Pick the publisher `pibo` (created during the first marketplace publish).
-3. Click **Upload new extension** and select `dist/apps/vscode-artifacts/pibo-vscode-1.3.0.vsix`.
-4. The Marketplace validates the manifest and publishes the extension. The publisher ID is `pibo.pibo-vscode`.
-
-After the upload, `code --install-extension pibo.pibo-vscode` works for end users.
-
-### 7. Verify
-
-```bash
-pibo vscode install --vsix dist/apps/vscode-artifacts/pibo-vscode-1.3.0.vsix
-pibo vscode status
-```
-
-Confirm that `status` reports `pibo.pibo-vscode@1.3.0` installed via the expected `code` binary, and that the WebView loads the gateway at `http://127.0.0.1:4788/apps/chat-vscode/`.
-
-## Rollback
-
-If a release is broken:
-
-- **npm**: `npm unpublish @pasko70/pibo@1.3.0` works only within 72 hours of publish. After that, publish `1.3.1` with a fix.
-- **VSIX via `pibo vscode install`**: delete the GitHub Release and re-create it with a fixed VSIX. Users who have already installed the extension will not auto-update until they run `pibo vscode install` again.
-- **Marketplace**: the Marketplace UI supports un-publishing or un-listing. For a fast fix, upload a corrected `.vsix` with the same version (the Marketplace accepts a re-upload before processing the original).
-
-## What ships in the `pibo` npm package
-
-The `files` whitelist in `package.json` controls what is published:
-
-- `dist/` — the compiled server, the gateway plugins, the WebView bundles (chat-ui, context-files-ui, chat-vscode-web).
-- `context/` — the bundled agent skills.
-- `skills/builtin/**` — built-in user skills.
-- `docs/ops/**` — operator runbooks.
-- `README.md` and `src/mcp/LICENSE.mcp-cli`.
-
-The `.vsix` is **not** in the npm package. It lives on the GitHub Release and (after the maintainer uploads it) on the VS Code Marketplace.
-
-## Why the WebView bundle is in the npm package
-
-The extension's WebView loads from `http://<gateway>/apps/chat-vscode/`, not from the `.vsix`. The gateway serves the bundle out of `dist/apps/chat-vscode-web/`. If the bundle were not in the npm package, the gateway would return 404 for the WebView and the extension would be unusable.
-
-Including the bundle in npm costs about 1 MB of disk per `pibo` install and zero runtime cost for users who never open the extension. Users who only use the `pibo` CLI never load the bundle.
+# Pibo VS Code Extension Release Runbook
+
+The Pibo VS Code extension is shipped as a `.vsix` artifact. This runbook describes the end-to-end release process and the split of responsibilities between the maintainer and the `pibo` release script.
+
+## Distribution channels
+
+The extension is published through two channels that are intentionally separate:
+
+| Channel | Owner | Cadence | What it carries |
+|---|---|---|---|
+| npm `@pasko70/pibo` | automated via `npm publish` (or the release script's `--publish-npm` flag) | every `main` commit that includes a version bump | the `pibo` CLI, the gateway, the WebView bundle at `dist/apps/chat-vscode-web/` |
+| VS Code Marketplace `pibo.pibo-vscode` | **maintainer uploads the VSIX manually** via <https://marketplace.visualstudio.com/manage> | every release that needs the extension UI updated | the `.vsix` produced by `npm run vscode:package` |
+
+The npm package and the Marketplace extension are versioned together. The release script bumps both `package.json` (npm) and `src/apps/chat-vscode/package.json` (extension) in one go so the published artifacts stay in lockstep.
+
+`pibo vscode install` (new since the distribution rework) downloads the VSIX from the GitHub Release for the configured repo (`Pascapone/pibo` by default). When the maintainer also uploads the same VSIX to the Marketplace, both channels serve identical bytes.
+
+## Versioning
+
+- The root `package.json#version` is the npm version. It follows [SemVer](https://semver.org/).
+- The extension's `src/apps/chat-vscode/package.json#version` is the Marketplace version. It is kept equal to the npm version (the release script enforces this).
+- A SemVer **minor** bump (e.g., `1.2.0` → `1.3.0`) is appropriate when the change is additive and backward-compatible. The distribution rework itself is a minor bump: existing `pibo` users are unaffected, and the new `pibo vscode install` command is opt-in.
+- A SemVer **major** bump is reserved for breaking changes to either the public CLI surface or the WebView host↔Web postMessage contract.
+
+## Release steps
+
+The release script does the heavy lifting. The maintainer's job is to review, commit, and push.
+
+### 1. Pick the version
+
+Decide on the next version. For the distribution rework that introduces `pibo vscode install`, the right bump is `1.2.0` → `1.3.0` (new CLI command, new marketplace-ready extension, no breaking changes).
+
+### 2. Bump + build + package (local)
+
+From the repo root:
+
+```bash
+node scripts/release.mjs --version 1.3.0
+```
+
+The script:
+
+1. Reads the current version from both `package.json` files.
+2. Writes the new version to both files.
+3. Runs `npm run build` (which includes the WebView build).
+4. Runs `npm run vscode:package` to produce `dist/apps/vscode-artifacts/pibo-vscode-1.3.0.vsix` and a stable `latest.vsix` copy.
+5. Prints the VSIX path and size.
+
+The script does **not** push to git or create a tag. The maintainer reviews the diff and commits it.
+
+### 3. Commit and tag
+
+```bash
+git add package.json src/apps/chat-vscode/package.json
+git commit -m "chore(release): bump @pasko70/pibo and pibo.pibo-vscode to 1.3.0"
+git tag -a v1.3.0 -m "@pasko70/pibo 1.3.0"
+git push origin main
+git push origin v1.3.0
+```
+
+### 4. Create a GitHub Release with the VSIX attached
+
+The maintainer's local machine has the `gh` CLI installed:
+
+```bash
+gh release create v1.3.0 \
+  dist/apps/vscode-artifacts/pibo-vscode-1.3.0.vsix \
+  --title "pibo 1.3.0" \
+  --notes "..."
+```
+
+In environments where `gh` is not available (e.g. the pibo compute workers),
+`scripts/create-github-release.mjs` performs the same action via the Pibo
+GitHub App, which has been installed on `Pascapone/pibo` with the
+`contents: write` scope. The script accepts the GitHub App credentials from
+`PIBO_GITHUB_APP_ID` and `PIBO_GITHUB_APP_KEY` environment variables, or
+from the well-known env file at
+`/root/.pibo/uploads/github-app.env` (with the PEM key auto-discovered
+next to it).
+
+```bash
+node scripts/create-github-release.mjs \
+  --tag v1.3.0 \
+  --asset dist/apps/vscode-artifacts/pibo-vscode-1.3.0.vsix
+```
+
+Both paths make the VSIX downloadable from a stable URL
+(`https://github.com/Pascapone/pibo/releases/download/v1.3.0/pibo-vscode-1.3.0.vsix`).
+The `pibo vscode install` command uses the GitHub Releases API to discover
+this URL automatically.
+
+The release script can also do this in one step:
+
+```bash
+node scripts/release.mjs --version 1.3.0 --create-release
+```
+
+…if the tag has already been pushed. Internally the release script calls
+`scripts/create-github-release.mjs`, so it works in worker environments
+without `gh`.
+
+### 5. Publish the npm package
+
+```bash
+npm publish
+```
+
+Or, in one go with the release script:
+
+```bash
+node scripts/release.mjs --version 1.3.0 --publish-npm --create-release
+```
+
+The publish step uploads the `pibo` CLI, the gateway plugins, and the WebView bundle. The Marketplace upload is intentionally **not** automated — see step 6.
+
+### 6. Upload the VSIX to the VS Code Marketplace (manual)
+
+The Marketplace does not currently accept a Personal Access Token from this account (Azure-side provisioning issue). The release is therefore finished by uploading the VSIX through the Marketplace web UI:
+
+1. Open <https://marketplace.visualstudio.com/manage>.
+2. Pick the publisher `pibo` (created during the first marketplace publish).
+3. Click **Upload new extension** and select `dist/apps/vscode-artifacts/pibo-vscode-1.3.0.vsix`.
+4. The Marketplace validates the manifest and publishes the extension. The publisher ID is `pibo.pibo-vscode`.
+
+After the upload, `code --install-extension pibo.pibo-vscode` works for end users.
+
+### 7. Verify
+
+```bash
+pibo vscode install --vsix dist/apps/vscode-artifacts/pibo-vscode-1.3.0.vsix
+pibo vscode status
+```
+
+Confirm that `status` reports `pibo.pibo-vscode@1.3.0` installed via the expected `code` binary, and that the WebView loads the gateway at `http://127.0.0.1:4788/apps/chat-vscode/`.
+
+## Rollback
+
+If a release is broken:
+
+- **npm**: `npm unpublish @pasko70/pibo@1.3.0` works only within 72 hours of publish. After that, publish `1.3.1` with a fix.
+- **VSIX via `pibo vscode install`**: delete the GitHub Release and re-create it with a fixed VSIX. Users who have already installed the extension will not auto-update until they run `pibo vscode install` again.
+- **Marketplace**: the Marketplace UI supports un-publishing or un-listing. For a fast fix, upload a corrected `.vsix` with the same version (the Marketplace accepts a re-upload before processing the original).
+
+## What ships in the `pibo` npm package
+
+The `files` whitelist in `package.json` controls what is published:
+
+- `dist/` — the compiled server, the gateway plugins, the WebView bundles (chat-ui, context-files-ui, chat-vscode-web).
+- `context/` — the bundled agent skills.
+- `skills/builtin/**` — built-in user skills.
+- `docs/ops/**` — operator runbooks.
+- `README.md` and `src/mcp/LICENSE.mcp-cli`.
+
+The `.vsix` is **not** in the npm package. It lives on the GitHub Release and (after the maintainer uploads it) on the VS Code Marketplace.
+
+## Why the WebView bundle is in the npm package
+
+The extension's WebView loads from `http://<gateway>/apps/chat-vscode/`, not from the `.vsix`. The gateway serves the bundle out of `dist/apps/chat-vscode-web/`. If the bundle were not in the npm package, the gateway would return 404 for the WebView and the extension would be unusable.
+
+Including the bundle in npm costs about 1 MB of disk per `pibo` install and zero runtime cost for users who never open the extension. Users who only use the `pibo` CLI never load the bundle.

package/package.json

@@ -1,95 +1,95 @@
-{
-  "name": "@pasko70/pibo",
-  "version": "1.9.9",
-  "type": "module",
-  "imports": {
-    "vscode": "./src/apps/chat-vscode/extension/src/vscode-shim.js"
-  },
-  "description": "Minimal TypeScript wrapper around Pi Coding Agent.",
-  "files": [
-    "dist",
-    "context",
-    "skills/builtin/**",
-    "docs/ops/**",
-    "README.md",
-    "src/mcp/LICENSE.mcp-cli"
-  ],
-  "bin": {
-    "pibo": "dist/bin/pibo.js",
-    "rg": "dist/bin/rg.js"
-  },
-  "engines": {
-    "node": ">=24"
-  },
-  "scripts": {
-    "dev": "tsx src/bin/pibo.ts",
-    "profile": "tsx src/bin/pibo.ts profile",
-    "tui": "tsx src/bin/pibo.ts tui",
-    "tui:routed": "tsx src/bin/pibo.ts tui:routed",
-    "tui:gateway": "tsx src/bin/pibo.ts tui gateway-producer",
-    "gateway": "tsx src/bin/pibo.ts gateway",
-    "gateway:web": "npm run web-ui:build && tsx src/bin/pibo.ts gateway:web",
-    "client": "tsx src/bin/pibo.ts client",
-    "chat-ui:build": "vite build --config src/apps/chat-ui/vite.config.ts",
-    "chat-ui:typecheck": "tsc -p src/apps/chat-ui/tsconfig.json --noEmit",
-    "context-files-ui:build": "vite build --config src/apps/context-files-ui/vite.config.ts",
-    "context-files-ui:typecheck": "tsc -p src/apps/context-files-ui/tsconfig.json --noEmit",
-    "web-ui:build": "npm run chat-ui:build && npm run context-files-ui:build",
-    "vscode:typecheck": "tsc -p src/apps/chat-vscode/extension/tsconfig.json --noEmit && tsc -p src/apps/chat-vscode/extension/webview/tsconfig.json --noEmit",
-    "vscode:webview:build": "vite build --config src/apps/chat-vscode/extension/webview/vite.config.ts",
-    "vscode:extension:build": "esbuild src/apps/chat-vscode/extension/src/extension.ts --bundle --platform=node --target=node24 --format=cjs --outfile=src/apps/chat-vscode/dist/extension/extension.cjs --external:vscode --sourcemap=inline",
-    "vscode:package": "node scripts/vscode-package.mjs",
-    "release": "node scripts/release.mjs",
-    "release:github": "node scripts/create-github-release.mjs",
-    "build": "tsc -p tsconfig.json && npm run web-ui:build && npm run vscode:webview:build && node scripts/ensure-bin-executable.mjs",
-    "start": "node dist/bin/pibo.js",
-    "test": "npm run build && node --test test/*.test.mjs test/chat-vscode/*.test.mjs",
-    "check:product-vocab": "node scripts/legacy-product-vocabulary-gate.mjs",
-    "validate:ink-web-derived": "node scripts/ink-cli-web-derived-parity-validate.mjs",
-    "compute:limited-worker-smoke": "node scripts/compute-limited-worker-smoke.mjs",
-    "typecheck": "tsc -p tsconfig.json --noEmit && npm run chat-ui:typecheck && npm run context-files-ui:typecheck && npm run vscode:typecheck",
-    "clean": "node -e \"fs.rmSync('dist', { recursive: true, force: true })\"",
-    "prepack": "npm run build"
-  },
-  "dependencies": {
-    "@earendil-works/pi-agent-core": "0.80.6",
-    "@earendil-works/pi-ai": "0.80.6",
-    "@earendil-works/pi-coding-agent": "0.80.6",
-    "@earendil-works/pi-tui": "0.80.6",
-    "@mdxeditor/editor": "^3.55.0",
-    "@modelcontextprotocol/sdk": "^1.29.0",
-    "@tailwindcss/vite": "^4.2.4",
-    "@tanstack/react-query": "^5.100.7",
-    "@tanstack/react-router": "^1.168.25",
-    "@tanstack/react-start": "^1.167.50",
-    "@uiw/react-json-view": "^2.0.0-alpha.41",
-    "@vscode/ripgrep": "^1.18.0",
-    "@xyflow/react": "12.10.2",
-    "better-auth": "^1.6.9",
-    "commander": "^14.0.3",
-    "ink": "^7.0.3",
-    "lexical": "^0.35.0",
-    "lucide-react": "^0.545.0",
-    "prismjs": "^1.30.0",
-    "react": "^19.2.5",
-    "react-dom": "^19.2.5",
-    "react-markdown": "^10.1.0",
-    "react-virtuoso": "^4.18.6",
-    "remark-gfm": "^4.0.1",
-    "tailwindcss": "^4.2.4"
-  },
-  "devDependencies": {
-    "@tanstack/router-plugin": "^1.167.28",
-    "@types/node": "^25.6.0",
-    "@types/prismjs": "^1.26.6",
-    "@types/react": "^19.2.14",
-    "@types/react-dom": "^19.2.3",
-    "@vitejs/plugin-react": "^6.0.1",
-    "@vscode/vsce": "^3.6.0",
-    "esbuild": "^0.27.7",
-    "tsx": "^4.21.0",
-    "typescript": "^6.0.3",
-    "vite": "^8.0.10",
-    "vite-tsconfig-paths": "^5.1.4"
-  }
-}
+{
+  "name": "@pasko70/pibo",
+  "version": "1.9.11",
+  "type": "module",
+  "imports": {
+    "vscode": "./src/apps/chat-vscode/extension/src/vscode-shim.js"
+  },
+  "description": "Minimal TypeScript wrapper around Pi Coding Agent.",
+  "files": [
+    "dist",
+    "context",
+    "skills/builtin/**",
+    "docs/ops/**",
+    "README.md",
+    "src/mcp/LICENSE.mcp-cli"
+  ],
+  "bin": {
+    "pibo": "dist/bin/pibo.js",
+    "rg": "dist/bin/rg.js"
+  },
+  "engines": {
+    "node": ">=24"
+  },
+  "scripts": {
+    "dev": "tsx src/bin/pibo.ts",
+    "profile": "tsx src/bin/pibo.ts profile",
+    "tui": "tsx src/bin/pibo.ts tui",
+    "tui:routed": "tsx src/bin/pibo.ts tui:routed",
+    "tui:gateway": "tsx src/bin/pibo.ts tui gateway-producer",
+    "gateway": "tsx src/bin/pibo.ts gateway",
+    "gateway:web": "npm run web-ui:build && tsx src/bin/pibo.ts gateway:web",
+    "client": "tsx src/bin/pibo.ts client",
+    "chat-ui:build": "vite build --config src/apps/chat-ui/vite.config.ts",
+    "chat-ui:typecheck": "tsc -p src/apps/chat-ui/tsconfig.json --noEmit",
+    "context-files-ui:build": "vite build --config src/apps/context-files-ui/vite.config.ts",
+    "context-files-ui:typecheck": "tsc -p src/apps/context-files-ui/tsconfig.json --noEmit",
+    "web-ui:build": "npm run chat-ui:build && npm run context-files-ui:build",
+    "vscode:typecheck": "tsc -p src/apps/chat-vscode/extension/tsconfig.json --noEmit && tsc -p src/apps/chat-vscode/extension/webview/tsconfig.json --noEmit",
+    "vscode:webview:build": "vite build --config src/apps/chat-vscode/extension/webview/vite.config.ts",
+    "vscode:extension:build": "esbuild src/apps/chat-vscode/extension/src/extension.ts --bundle --platform=node --target=node24 --format=cjs --outfile=src/apps/chat-vscode/dist/extension/extension.cjs --external:vscode --sourcemap=inline",
+    "vscode:package": "node scripts/vscode-package.mjs",
+    "release": "node scripts/release.mjs",
+    "release:github": "node scripts/create-github-release.mjs",
+    "build": "tsc -p tsconfig.json && npm run web-ui:build && npm run vscode:webview:build && node scripts/ensure-bin-executable.mjs",
+    "start": "node dist/bin/pibo.js",
+    "test": "npm run build && node --test test/*.test.mjs test/chat-vscode/*.test.mjs",
+    "check:product-vocab": "node scripts/legacy-product-vocabulary-gate.mjs",
+    "validate:ink-web-derived": "node scripts/ink-cli-web-derived-parity-validate.mjs",
+    "compute:limited-worker-smoke": "node scripts/compute-limited-worker-smoke.mjs",
+    "typecheck": "tsc -p tsconfig.json --noEmit && npm run chat-ui:typecheck && npm run context-files-ui:typecheck && npm run vscode:typecheck",
+    "clean": "node -e \"fs.rmSync('dist', { recursive: true, force: true })\"",
+    "prepack": "npm run build"
+  },
+  "dependencies": {
+    "@earendil-works/pi-agent-core": "0.80.6",
+    "@earendil-works/pi-ai": "0.80.6",
+    "@earendil-works/pi-coding-agent": "0.80.6",
+    "@earendil-works/pi-tui": "0.80.6",
+    "@mdxeditor/editor": "^3.55.0",
+    "@modelcontextprotocol/sdk": "^1.29.0",
+    "@tailwindcss/vite": "^4.2.4",
+    "@tanstack/react-query": "^5.100.7",
+    "@tanstack/react-router": "^1.168.25",
+    "@tanstack/react-start": "^1.167.50",
+    "@uiw/react-json-view": "^2.0.0-alpha.41",
+    "@vscode/ripgrep": "^1.18.0",
+    "@xyflow/react": "12.10.2",
+    "better-auth": "^1.6.9",
+    "commander": "^14.0.3",
+    "ink": "^7.0.3",
+    "lexical": "^0.35.0",
+    "lucide-react": "^0.545.0",
+    "prismjs": "^1.30.0",
+    "react": "^19.2.5",
+    "react-dom": "^19.2.5",
+    "react-markdown": "^10.1.0",
+    "react-virtuoso": "^4.18.6",
+    "remark-gfm": "^4.0.1",
+    "tailwindcss": "^4.2.4"
+  },
+  "devDependencies": {
+    "@tanstack/router-plugin": "^1.167.28",
+    "@types/node": "^25.6.0",
+    "@types/prismjs": "^1.26.6",
+    "@types/react": "^19.2.14",
+    "@types/react-dom": "^19.2.3",
+    "@vitejs/plugin-react": "^6.0.1",
+    "@vscode/vsce": "^3.6.0",
+    "esbuild": "^0.27.7",
+    "tsx": "^4.21.0",
+    "typescript": "^6.0.3",
+    "vite": "^8.0.10",
+    "vite-tsconfig-paths": "^5.1.4"
+  }
+}

package/skills/builtin/graphify/SKILL.md

@@ -1,52 +1,52 @@
----
-name: graphify
-description: Use this skill when a user asks to graph, map, or visualize a codebase/workspace with Graphify and inspect the generated graphify-out/graph.html, graphify-out/graph.json, or graphify-out/GRAPH_REPORT.md artifacts.
----
-
-# Graphify Codebase Visualization
-
-Use Graphify to turn a workspace folder into an interactive knowledge graph and report. Prefer this skill for requests like "graph this repo", "visualize this codebase", "map the workspace", or "show me the project structure as a graph".
-
-## Prerequisites
-
-Graphify is exposed as a curated Pibo CLI tool:
-
-```bash
-pibo tools show graphify
-pibo tools install graphify
-eval "$(pibo tools env graphify)"
-```
-
-Inside the Pibo source repo while testing local changes, use:
-
-```bash
-npm run --silent dev -- tools show graphify
-npm run --silent dev -- tools install graphify
-eval "$(npm run --silent dev -- tools env graphify)"
-```
-
-The Pibo installer uses the PyPI package `graphifyy` and runs `graphify install --platform pi` after installing the CLI.
-
-## Workflow
-
-1. Identify the workspace path from the active Pibo Room/session context or from the user's request.
-2. Confirm the path is inside the intended workspace boundary before graphing.
-3. Prefer an ignored artifact directory for generated files when possible. If you generate in the repo root, check `git status --short` before and after.
-4. Run Graphify on the selected folder. With `graphifyy==0.9.x`, `graphify .` writes extraction output under `graphify-out/`.
-5. If you need an HTML graph and markdown report from a code-only extraction without an LLM key, run `graphify cluster-only . --no-label` after `graphify .`.
-6. Read `graphify-out/GRAPH_REPORT.md` first for the summary, then open `graphify-out/graph.html` when the user wants an interactive view.
-
-```bash
-cd /path/to/workspace
-graphify .
-graphify cluster-only . --no-label
-ls graphify-out/graph.html graphify-out/graph.json graphify-out/GRAPH_REPORT.md
-```
-
-## Operating rules
-
-- Treat `graphify-out/graph.html`, `graphify-out/graph.json`, and `graphify-out/GRAPH_REPORT.md` as derived artifacts unless the user explicitly wants them committed.
-- Code-only extraction can run without an LLM API key. Including docs, README files, papers, images, or semantic-labeling steps may require a configured Graphify backend/API key; if no key is available, graph a code-only subdirectory or skip semantic labels with `cluster-only . --no-label`.
-- For large monorepos, start with a focused subdirectory such as `src/`, a code package, or a docs folder only when the needed LLM backend is configured.
-- Re-run Graphify on demand after branch or workspace changes; do not assume an old graph is current.
-- If Graphify is unavailable, report the missing install and suggest `pibo tools install graphify` rather than hand-writing a replacement graph.
+---
+name: graphify
+description: Use this skill when a user asks to graph, map, or visualize a codebase/workspace with Graphify and inspect the generated graphify-out/graph.html, graphify-out/graph.json, or graphify-out/GRAPH_REPORT.md artifacts.
+---
+
+# Graphify Codebase Visualization
+
+Use Graphify to turn a workspace folder into an interactive knowledge graph and report. Prefer this skill for requests like "graph this repo", "visualize this codebase", "map the workspace", or "show me the project structure as a graph".
+
+## Prerequisites
+
+Graphify is exposed as a curated Pibo CLI tool:
+
+```bash
+pibo tools show graphify
+pibo tools install graphify
+eval "$(pibo tools env graphify)"
+```
+
+Inside the Pibo source repo while testing local changes, use:
+
+```bash
+npm run --silent dev -- tools show graphify
+npm run --silent dev -- tools install graphify
+eval "$(npm run --silent dev -- tools env graphify)"
+```
+
+The Pibo installer uses the PyPI package `graphifyy` and runs `graphify install --platform pi` after installing the CLI.
+
+## Workflow
+
+1. Identify the workspace path from the active Pibo Room/session context or from the user's request.
+2. Confirm the path is inside the intended workspace boundary before graphing.
+3. Prefer an ignored artifact directory for generated files when possible. If you generate in the repo root, check `git status --short` before and after.
+4. Run Graphify on the selected folder. With `graphifyy==0.9.x`, `graphify .` writes extraction output under `graphify-out/`.
+5. If you need an HTML graph and markdown report from a code-only extraction without an LLM key, run `graphify cluster-only . --no-label` after `graphify .`.
+6. Read `graphify-out/GRAPH_REPORT.md` first for the summary, then open `graphify-out/graph.html` when the user wants an interactive view.
+
+```bash
+cd /path/to/workspace
+graphify .
+graphify cluster-only . --no-label
+ls graphify-out/graph.html graphify-out/graph.json graphify-out/GRAPH_REPORT.md
+```
+
+## Operating rules
+
+- Treat `graphify-out/graph.html`, `graphify-out/graph.json`, and `graphify-out/GRAPH_REPORT.md` as derived artifacts unless the user explicitly wants them committed.
+- Code-only extraction can run without an LLM API key. Including docs, README files, papers, images, or semantic-labeling steps may require a configured Graphify backend/API key; if no key is available, graph a code-only subdirectory or skip semantic labels with `cluster-only . --no-label`.
+- For large monorepos, start with a focused subdirectory such as `src/`, a code package, or a docs folder only when the needed LLM backend is configured.
+- Re-run Graphify on demand after branch or workspace changes; do not assume an old graph is current.
+- If Graphify is unavailable, report the missing install and suggest `pibo tools install graphify` rather than hand-writing a replacement graph.