@dotobokuri/fleet-console 1.16.1 → 1.17.1

package/AGENTS.md

@@ -125,7 +125,9 @@ These guards are robustness measures on top of the trust model, not a replacemen
   - `notifications.emit` feeds `operationNotifications` (ALERTS are shown only for Operations that are not currently visible).
   - `status.set` / `status.clear` feed `operationStatus`, which drives the running-panel perimeter progress rim and beacon.
 - `theme` is passed to plugins through `OperationRenderContext` (not through a capability), so plugins receive the current `ConsoleTheme` reactively on every canvas render. Host token boundaries remain unchanged: these are transient client-only values; no tokens, paths, or credentials cross into plugin code.
-- Terminal renderer and font preferences are **not** in `OperationRenderContext`. The Terminal plugin owns these prefs end-to-end through a module-scoped `useSyncExternalStore` store (`client/shared/terminal-prefs-store.ts`), stored under `fleet-plugin.terminal.renderer` and `fleet-plugin.terminal.font` localStorage keys. All mounted terminal panels subscribe directly and react instantly to settings changes. `fleet-plugin.terminal.*` keys are Terminal plugin-owned; core and other plugins must not read or write them.
+- Terminal renderer and font preferences are **not** in `OperationRenderContext`. The Terminal plugin owns these prefs end-to-end through a module-scoped `useSyncExternalStore` store (`client/shared/terminal-prefs-store.ts`). All mounted terminal panels subscribe directly and react instantly to settings changes. **Terminal Renderer** is persisted in localStorage under `fleet-plugin.terminal.renderer` (per-browser volatile). **Terminal Font** (name + size) is persisted on the console server under `plugins.terminal.font` via `ClientSettingsCapability` (`GET`/`PUT /api/v1/settings/plugins/terminal`); it survives browser changes and console restarts. On first load the store seeds the server from `fleet-plugin.terminal.font` localStorage if the server has no value (1-time migration), then removes the local key. `fleet-plugin.terminal.*` localStorage keys are Terminal plugin-owned; core and other plugins must not read or write them.
+- **Preferences vs Settings semantics**: `ClientPreferencesCapability` is per-browser volatile (localStorage). `ClientSettingsCapability` is per-server durable (stored in the console `settings.json` `plugins` record; the server is the SSoT). Use preferences for transient display choices (e.g. renderer backend); use settings for durable configuration (e.g. font, feature toggles) that must survive browser changes and console restarts.
+- **Plugin settings safety**: Values written through `ClientSettingsCapability` must not contain secrets, tokens, credentials, or raw filesystem paths. The Token Boundary applies to plugin settings payloads the same as to all other browser-facing payloads. Model API keys persist through `@dotobokuri/fleet-infra` auth storage, not plugin settings.
 - The SDK contract is invariant. Host code may only extend capability implementations; it must not add new capability surface areas or require plugins to import core modules.
 
 ## Window System
@@ -157,6 +159,7 @@ Operation chrome (maximize, minimize, focus, and the Operations Left SideBar) is
 - `../fleet-plugins/terminal/` — the built-in Terminal plugin package. It provides the Shell and Agent browser panels, plugin route handlers, launch metadata, and absorbed shared/server-shared/client-shared helpers for the single `terminal` plugin.
 - `../fleet-plugins/diff/` — the built-in Diff plugin package. It owns git diff backend routes (`/plugins/diff/changed`, `/plugins/diff/file`), `isSafeGitRef` validation, and the Diff rail panel client. Server code (`server/`) and client code (`client/`) are self-contained; no git or file helpers live in `core/host/`.
 - `../fleet-plugins/file-explorer/` — the built-in File Explorer plugin package. It owns file listing (`/plugins/file-explorer/files/list`), file reading (`/plugins/file-explorer/files/read`), image serving (`/plugins/file-explorer/files/image`), symlink-aware containment, and the File Explorer rail panel client. Server code (`server/`) and client code (`client/`) are self-contained.
+- `../fleet-plugins/skills/` — the built-in Skills plugin package. It wraps the Vercel Labs `skills` CLI (pinned version, self-bootstrapped into the plugin data directory via `npm install --prefix --global=false --force=false` and executed directly as `node <…>/node_modules/skills/bin/cli.mjs` — never `npx`, whose multi-bin resolution breaks under non-default user npm configs) to provide skill list, install, update, remove, and SKILL.md preview routes under `/plugins/skills/*`, proxies the skills.sh registry search API, manages an in-memory job registry with 750ms cursor polling, and renders the Skills Activity Rail panel (Installed/Find tabs, inline install flow, reading overlay).
 - `tests/` — vitest suites for the reducer, SSE parser, store, terminal, and CLI lifecycle.
 
 ## Tech Stack (deliberate)
@@ -237,7 +240,7 @@ imports -> types/interfaces -> constants -> functions/components
 
 ## Build & Serve Contract
 
-- `pnpm --filter @dotobokuri/fleet-console build` runs tsup (`core/host/cli.ts` → `dist/cli.mjs`, `core/host/cli-bin.ts` → `dist/cli-bin.mjs`, `../fleet-plugins/terminal/routes.ts` → `dist/fleet-plugins/terminal/routes.mjs`, `../fleet-plugins/diff/routes.ts` → `dist/fleet-plugins/diff/routes.mjs`, `../fleet-plugins/file-explorer/routes.ts` → `dist/fleet-plugins/file-explorer/routes.mjs`) and Vite (`core/client/` → `dist/client/` with `base: "/console/"`). There is **no** embed step: the console backend serves its own `dist/client/` directly under `/console/` (loopback-only). Changing `base` or the output layout breaks the static-serving contract.
+- `pnpm --filter @dotobokuri/fleet-console build` runs tsup (`core/host/cli.ts` → `dist/cli.mjs`, `core/host/cli-bin.ts` → `dist/cli-bin.mjs`, `../fleet-plugins/terminal/routes.ts` → `dist/fleet-plugins/terminal/routes.mjs`, `../fleet-plugins/diff/routes.ts` → `dist/fleet-plugins/diff/routes.mjs`, `../fleet-plugins/file-explorer/routes.ts` → `dist/fleet-plugins/file-explorer/routes.mjs`, `../fleet-plugins/skills/routes.ts` → `dist/fleet-plugins/skills/routes.mjs`) and Vite (`core/client/` → `dist/client/` with `base: "/console/"`). There is **no** embed step: the console backend serves its own `dist/client/` directly under `/console/` (loopback-only). Changing `base` or the output layout breaks the static-serving contract.
 - This package **is** the HTTP server. The backend owns its own loopback server, lifecycle, and `/console/` serving; the CLI starts and stops that server rather than launching a separate daemon.
 - **npm publish contract**: tsup bundles every `@dotobokuri/*` workspace dependency and `@fleet-console/sdk` inline (`noExternal: [/^@dotobokuri\//, /^@fleet-console\/sdk(\/|$)/]`) so the published package is self-contained; only `node-pty` (native binding) and `ws` (dynamic `require`) stay external. `scripts/publish-fleet-console.mjs` drops `private`, replaces `dependencies` with just those two externals, and injects the `node-pty` `postinstall`. Do **not** add a statically-imported workspace package without confirming it bundles, and re-verify the published manifest with `npm pack` after touching `noExternal` or runtime deps — leaving a `workspace:*` dependency in the manifest breaks `npm install`.
 - **Plugin native/external module resolution**: a built-in plugin's server code that `require()`s a native or `external` module (`node-pty`, `ws`) must resolve it against the `@dotobokuri/fleet-console` package, not via a bare `createRequire(import.meta.url)`. Plugins load from an esbuild **cache bundle** (`node_modules/.cache/fleet-console-plugin-*`), so a `createRequire` rooted there can resolve a **stale copy from a parent-workspace `node_modules`** and fail at runtime with `posix_spawnp failed` — typecheck and build stay green, so only a runtime/e2e run catches it. The Terminal plugin's `server/shared/pty.ts` (`findConsolePackageRequire`) is the reference, guarded by a `launch.test.ts` regression test.