@commandgarden/cli 2.14.2 → 2.14.3

package/node_modules/@commandgarden/app/package.json

@@ -3,9 +3,6 @@
   "version": "0.1.0",
   "private": true,
   "type": "module",
-  "files": [
-    "dist"
-  ],
   "scripts": {
     "build": "vite build && tsc -p tsconfig.server.json",
     "dev": "concurrently \"vite\" \"tsx watch src/server/main.ts\"",

package/node_modules/@commandgarden/app/skills/cg/SKILL.md

@@ -0,0 +1,85 @@
+---
+name: cg
+description: "Run commandGarden connectors via `cg` to query enterprise data from authenticated browser sessions. Use when the user mentions `cg`, commandGarden, connectors, or wants to fetch timetracking, room availability, security news, or data behind SSO."
+---
+
+`cg` queries enterprise websites through **connectors** — declarative YAML pipelines executed via a Chrome extension using the user's live browser session. No credentials stored.
+
+## Workflow
+
+### 1. Verify readiness
+
+Run `cg daemon status`. Proceed only when output shows "Daemon: running" and "Extension: connected". If not running, run `cg up`.
+
+### 2. Discover
+
+Run `cg list` to see all installed connectors. Each connector has a key in `site/name` format (e.g. `timetracking/report`). Filter large output: `cg list | Select-String "keyword"` (PowerShell) or `cg list | grep -i "keyword"` (bash).
+
+### 3. Inspect
+
+Run `cg inspect <site/name>` before running any connector. Shows required arguments, defaults, output columns, and pipeline steps. Never guess argument names.
+
+### 4. Run
+
+```
+cg run <site/name> --format json [--arg value ...]
+```
+
+**Always `--format json`**. Output shape:
+
+```json
+{"ok": true, "connector": "site/name", "rowCount": N, "columns": [...], "data": [{...}, ...]}
+```
+
+### 5. Parse
+
+Read the `data` array from JSON output. Column names match `columns`. `rowCount` confirms expected cardinality.
+
+Errors return plain text starting with `Error:` — not JSON.
+
+## Connectors
+
+| Key | Description | Args |
+|-----|-------------|------|
+| `ado/git-commits` | ADO Git commits & PRs for a date range | `org`, `project`, `repo`, `fromDate`, `toDate`, `author` |
+| `gcs/kb-pages` | GCS Knowledge Base page index | — |
+| `gcs/kb-content` | Retrieve one GCS KB page as Markdown | `path` |
+| `jira/my-tickets` | Jira tickets assigned to user | `fromDate`, `toDate`, `assignee` |
+| `outlook/my-meetings` | User's Outlook Calendar for a day | `date` |
+| `saba/pending-training` | Pending mandatory training from Saba | — |
+| `socket/security-news` | Latest security news from Socket.dev | `tag` (optional) |
+| `teams/room-availability` | Room free/busy for one room | `room`, `date` |
+| `teams/rooms-availability` | Room free/busy for multiple rooms | `rooms`, `email`, `date` |
+| `timetracking/projects` | Available projects & activities | `month` |
+| `timetracking/report` | Monthly time-tracking report | `month` |
+| `tldrsec/newsletter` | tl;dr sec newsletter issues | — |
+| `tokenmaster/client-trustedby` | Clients that trust a given client | `clientid`, `region` |
+| `tokenmaster/clients-list` | Clients managed by current user | `region` |
+| `wiz/blog-security` | Wiz security blog posts | `tag` (optional) |
+
+## Errors
+
+| Output contains | Fix |
+|---|---|
+| "not running" / "No session token" | `cg up` |
+| "not connected" | Open Chrome with the extension loaded |
+| "not approved" | Add connector key to `security.approvedHighRisk` in `~/.commandgarden/config.yaml` |
+| "back/forward cache" | Retry the command |
+
+## Commands
+
+| Command | What it does |
+|---|---|
+| `cg up` / `cg down` | Start / stop all services |
+| `cg daemon status` | Health check (daemon + extension) |
+| `cg list` | All installed connectors |
+| `cg inspect <key>` | Connector args, columns, pipeline |
+| `cg run <key> --format json` | Execute a connector |
+| `cg validate <file>` | Validate a connector YAML file |
+| `cg audit list --since <dur>` | Recent audit events (e.g. `7d`, `1h`) |
+| `cg audit export --format json --since <dur>` | Export audit events as JSON |
+| `cg config show` | View current configuration |
+
+## Writing connectors
+
+Use the [connector-authoring skill](../connector-authoring/SKILL.md) for the full recon→scaffold→implement→debug→polish sequence. Reference docs: [`connector-authoring.md`](../../docs/connector-authoring.md) and [`pipeline-reference.md`](../../docs/pipeline-reference.md). Place new connector YAML files in `~/.commandgarden/connectors/`. Validate with `cg validate <file>` before use.

package/node_modules/@commandgarden/app/skills/connector-authoring/RECON-PLAYBOOK.md

@@ -0,0 +1,364 @@
+# Recon Playbook
+
+Ground-layer debugging for commandGarden connectors. Use when the audit log and basic probing (step 4 of SKILL.md) aren't enough to get data flowing.
+
+---
+
+## Network interception hierarchy
+
+From most visible (page JS) to most powerful (network stack):
+
+```
+window.fetch patch    →  Sees only page-initiated fetch() calls
+  ↓                      Invisible: SW-mediated, MCAS-wrapped, XHR
+CDP Network.enable    →  Sees per-target requests (tab OR SW, not both)
+  ↓                      Invisible: may miss timing-dependent SW events
+CDP Fetch.enable      →  Sees ALL requests at the network stack level
+                         Sees: SW-mediated, MCAS-wrapped, proxied — everything
+                         Caveat: response bodies may be base64-encoded
+```
+
+Always start at the top. Escalate down only when the higher level captures nothing.
+
+---
+
+## Technique 1: Strip the pipeline
+
+Remove steps from the end until data flows. Isolate which step breaks.
+
+```bash
+# Keep only: navigate + wait
+# Expected: ok: true, data: [], 0 rows — navigation works
+cg run <site>/<name> --format json
+
+# Add: fetch or extract
+# Expected: ok: true, data: [...], N rows — data source works
+cg run <site>/<name> --format json
+
+# Add: map
+# Check: field values aren't "undefined" — field names match
+cg run <site>/<name> --format json
+```
+
+If `navigate + wait` fails, the problem is auth (SSO redirect, wrong URL, page blocked).
+If `fetch` returns 0 rows, the problem is the API call (wrong URL, content type, wrapper object).
+If `map` produces `"undefined"`, the problem is field name casing.
+
+---
+
+## Technique 2: Inspect raw API responses
+
+For `fetch` connectors — remove the `map` step and examine raw output:
+
+```bash
+cg run <site>/<name> --format json
+```
+
+**0 rows, no error:**
+- API returned non-JSON → add `headers: { Accept: "application/json" }` to the `fetch` step.
+- API returned a wrapper object like `{ "items": [...] }` → add `dataPath: "items"`.
+- `fetch` ran on the wrong tab or URL → check the audit log `steps[]` for the fetch step's error/timing.
+
+**Data present but wrong shape:**
+- Field names are case-sensitive. Compare the raw JSON keys with your `map` expressions exactly.
+- Arrays in responses (e.g. `["ALICE", "BOB"]`) auto-join to `"ALICE,BOB"` in map expressions.
+
+---
+
+## Technique 3: Console logging in js_evaluate
+
+Add `console.log()` to the eval.js file. Output appears in the **target tab's** DevTools console (not the extension's service worker console).
+
+```js
+console.log('[cg] token:', token ? 'found (' + token.slice(0, 8) + '...)' : 'MISSING');
+console.log('[cg] API status:', resp.status);
+console.log('[cg] response preview:', JSON.stringify(data).slice(0, 300));
+console.log('[cg] row count:', rows.length);
+```
+
+After the debug session, remove all `[cg]` logs — they're visible to anyone with DevTools open.
+
+**DevTools not showing logs?** The eval.js runs in the page's MAIN world. Make sure you're looking at the correct tab's console, not the extension's background page.
+
+---
+
+## Technique 4: window.fetch interception
+
+Capture data from requests the page makes on its own — not your `fetch` step, but the page's own API calls triggered by UI interactions.
+
+```js
+// Install the interceptor BEFORE triggering the UI action
+if (!window.__rfb) {
+  window.__rfb = [];
+  const origFetch = window.fetch;
+  window.fetch = function() {
+    const args = arguments;
+    const url = (args[0]?.url || args[0] || '').toString();
+    const body = (args[1]?.body || '').toString();
+    return origFetch.apply(this, args).then(r => {
+      if (url.includes('YOUR_KEYWORD')) {
+        r.clone().text().then(t => {
+          window.__rfb.push({ url, reqBody: body, resBody: t });
+        }).catch(() => {});
+      }
+      return r;
+    });
+  };
+}
+```
+
+Then trigger the UI action (click a button, type in a field), wait, and read:
+
+```js
+await new Promise(r => setTimeout(r, 5000));
+const captured = window.__rfb;
+window.__rfb = [];
+if (!captured.length) throw new Error('No requests captured — check URL keyword');
+
+// Parse and process
+const data = JSON.parse(captured[0].resBody);
+```
+
+**Gotcha: timing.** The interceptor must be installed before the page makes the request. If the page fires requests on load, install the interceptor, then re-trigger (e.g., navigate, click a refresh button).
+
+**Gotcha: cloning.** Always use `r.clone().text()` — reading the original response body consumes it and breaks the page.
+
+---
+
+## Technique 5: CDP Fetch.enable
+
+When `window.fetch` interception captures nothing — the request uses a transport invisible to page-level JS.
+
+**Common causes:**
+- **MCAS proxy** (`*.mcas.ms`) — Microsoft Defender for Cloud Apps injects `js-wrapper.js` that handles requests outside `window.fetch`
+- **Service Worker** — SW intercepts and replays requests on a separate CDP target
+- **Custom XHR wrappers** — legacy apps using `XMLHttpRequest` with custom transport layers
+
+### How to verify the gap
+
+Widen the interceptor to log ALL fetch calls, not just your keyword:
+
+```js
+window.fetch = function() {
+  const url = (arguments[0]?.url || arguments[0] || '').toString();
+  console.log('[cg fetch]', url.slice(0, 120));
+  return origFetch.apply(this, arguments);
+};
+```
+
+If the request you're looking for doesn't appear in the console but the data renders in the UI → it's using a transport below `window.fetch`.
+
+### The fix: CDP Fetch domain
+
+Requires modifying `chrome/src/background/chrome-adapter.ts`. The `Fetch` CDP domain intercepts at the browser's network stack — below the SW and MCAS layers.
+
+```typescript
+// In attachDebugger():
+await chrome.debugger.sendCommand({ tabId }, 'Fetch.enable', {
+  patterns: [{ urlPattern: '*your-pattern*', requestStage: 'Response' }],
+});
+```
+
+Handle `Fetch.requestPaused` events:
+
+```typescript
+// 1. Read the response body
+const result = await chrome.debugger.sendCommand(
+  debuggee, 'Fetch.getResponseBody', { requestId }
+);
+const raw = result as { body: string; base64Encoded: boolean };
+
+// 2. Decode if base64 (MCAS proxied responses are always base64)
+const body = raw.base64Encoded ? atob(raw.body) : (raw.body || '');
+
+// 3. Check for your signal
+if (body.includes('yourKeyword')) {
+  // Inject into page context via chrome.scripting.executeScript
+  await chrome.scripting.executeScript({
+    target: { tabId },
+    world: 'MAIN',
+    func: (data) => { window.__rfb.push(data); },
+    args: [{ body }],
+  });
+}
+
+// 4. ALWAYS continue the request or the page hangs
+await chrome.debugger.sendCommand(
+  debuggee, 'Fetch.continueRequest', { requestId }
+).catch(() => {});  // swallow errors on detached targets
+```
+
+### Critical gotchas
+
+1. **base64 decoding** — `Fetch.getResponseBody` returns base64 for MCAS-proxied responses. Check the `base64Encoded` flag. Always `atob()` before string matching.
+
+2. **Must continue** — every `Fetch.requestPaused` must be followed by `Fetch.continueRequest`, `Fetch.fulfillRequest`, or `Fetch.failRequest`. Missing this hangs the page permanently. Use `.catch()` to swallow errors from detached targets.
+
+3. **TypeScript** — `atob` is available in the Chrome extension service worker at runtime but not typed. Add at file top:
+   ```typescript
+   declare function atob(data: string): string;
+   ```
+
+4. **Service Worker targets** — SW network events are on a separate CDP target. Attach to both the tab and the SW:
+   ```typescript
+   const targets = await chrome.debugger.getTargets();
+   const sw = targets.find(t =>
+     t.type === 'service_worker' && t.url.startsWith(origin)
+   );
+   if (sw?.id) {
+     await chrome.debugger.attach({ targetId: sw.id }, '1.3');
+     await chrome.debugger.sendCommand(
+       { targetId: sw.id }, 'Fetch.enable',
+       { patterns: [{ urlPattern: '*pattern*', requestStage: 'Response' }] }
+     );
+   }
+   ```
+
+5. **Chrome `debugger` permission** — the extension manifest needs:
+   ```json
+   { "permissions": ["debugger"] }
+   ```
+
+Full investigation writeup: `docs/teams-room-availability-fix.md`.
+
+---
+
+## Technique 6: Auth patterns
+
+### SSO/MFA redirect polling
+
+The first `navigate` triggers SSO. Build in wait time:
+
+```js
+// Poll for a signal that auth completed
+const deadline = Date.now() + 30000;
+while (Date.now() < deadline) {
+  // Signal: a DOM element that only renders when logged in
+  if (document.querySelector('.user-avatar')) break;
+  // Or: check if we're still on a login page
+  if (/login|oauth|signin|sso/i.test(location.href)) {
+    await new Promise(r => setTimeout(r, 2000));
+    continue;
+  }
+  break;
+}
+```
+
+### MSAL token extraction (Azure AD apps)
+
+Many Microsoft/enterprise apps store tokens in sessionStorage. See `connectors/lib/msal-token.js` for the canonical pattern:
+
+```js
+const deadline = Date.now() + 60000;
+let token;
+while (Date.now() < deadline) {
+  const key = Object.keys(sessionStorage).find(k => k.includes('accesstoken'));
+  if (key) {
+    try {
+      const data = JSON.parse(sessionStorage.getItem(key));
+      // Check token isn't about to expire (30s buffer)
+      if (Number(data.expiresOn) > Math.floor(Date.now() / 1000) + 30) {
+        token = data.secret;
+        break;
+      }
+    } catch (_) {}
+  }
+  await new Promise(r => setTimeout(r, 1000));
+}
+if (!token) throw new Error('No valid MSAL access token — log in and retry');
+```
+
+Use the token as a Bearer header:
+```js
+const resp = await fetch(apiUrl, {
+  headers: { Authorization: 'Bearer ' + token, Accept: 'application/json' }
+});
+```
+
+### Session cookies (fetch pattern)
+
+For `fetch` pattern connectors, session cookies are sent automatically — `fetchFromPage` uses `credentials: 'include'`. Just `navigate` to the domain first to establish the session through SSO.
+
+---
+
+## Technique 7: SPA rendering delays
+
+SPAs (React, Angular, Vue) render data after the initial page load. The `wait` step checks that a selector *exists* in the DOM — not that data has populated.
+
+### In eval.js — poll for content
+
+```js
+const deadline = Date.now() + 30000;
+while (Date.now() < deadline) {
+  const rows = document.querySelectorAll('.data-table tbody tr');
+  if (rows.length > 0) break;
+  await new Promise(r => setTimeout(r, 1000));
+}
+```
+
+### In YAML — chain wait + extract
+
+```yaml
+- step: wait
+  selector: ".data-table tbody tr"   # wait for actual rows, not just the table
+  timeout: 30000
+- step: extract
+  selector: ".data-table tbody tr"
+  fields:
+    name: "td:nth-child(1)"
+```
+
+---
+
+## Technique 8: Driving UI interactions in eval.js
+
+When you need to click buttons, type in fields, or navigate within an SPA — all from eval.js. See `connectors/teams-room-availability.eval.js` for a production example of all three.
+
+### Clicking by accessible name
+
+```js
+function clickByName(name) {
+  const els = Array.from(document.querySelectorAll('button, a, [role=button]'));
+  const el = els.find(e => {
+    if (!e.offsetParent) return false;  // skip hidden
+    const label = (e.getAttribute('aria-label') || '').trim();
+    const text = (e.textContent || '').replace(/\s+/g, ' ').trim();
+    return label === name || label.includes(name) || text.includes(name);
+  });
+  if (!el) return false;
+  el.scrollIntoView({ block: 'center' });
+  el.click();
+  return true;
+}
+```
+
+### Typing into React-controlled inputs
+
+React overrides the native `value` setter. Use the prototype setter to bypass:
+
+```js
+function typeText(selector, text) {
+  const el = document.querySelector(selector);
+  if (!el) throw new Error(`Element "${selector}" not found`);
+  el.focus();
+  const setter = Object.getOwnPropertyDescriptor(
+    window.HTMLInputElement.prototype, 'value'
+  ).set;
+  setter.call(el, text);
+  el.dispatchEvent(new Event('input', { bubbles: true }));
+  el.dispatchEvent(new Event('change', { bubbles: true }));
+}
+```
+
+### Waiting for a UI reaction
+
+After clicking or typing, poll for the expected outcome — never use fixed sleeps alone:
+
+```js
+clickByName('Submit');
+const deadline = Date.now() + 10000;
+while (Date.now() < deadline) {
+  if (document.querySelector('.results-loaded')) break;
+  await new Promise(r => setTimeout(r, 500));
+}
+```

package/node_modules/@commandgarden/app/skills/connector-authoring/SKILL.md

@@ -0,0 +1,160 @@
+---
+name: connector-authoring
+description: "Connector authoring for commandGarden. Use when creating a new connector YAML, adding a data source, or debugging why a connector returns 0 rows."
+---
+
+Build a new commandGarden connector from recon through polish. Each step has a checkable completion criterion.
+
+## Step 1: Recon the target site
+
+Open the target site in Chrome with DevTools. Goal: find where the data lives and which extraction pattern fits.
+
+**Check in this order (cheapest capability first):**
+
+1. **Network tab → XHR/Fetch** — filter requests while using the UI. JSON API responses → **`fetch → map`** (capabilities: `navigate`, `cookie_read`). Safest pattern — prefer it.
+
+2. **Elements tab → DOM** — repeating elements (table rows, cards) → **`extract`** (`navigate`, `dom_read`). Nested tree (sidebar nav) → **`extract_tree`** (add `dom_write` if collapsed sections need `click_all`).
+
+3. **Network tab → page-initiated requests** — data from requests the page makes on its own (GraphQL, polling) → **`intercept`** step with `urlPattern` (`navigate`, `intercept_response`). Middle ground between `fetch` and `js_evaluate`.
+
+4. **Source tab → `<script id="__NEXT_DATA__">`** or `__remixContext` — framework-embedded page data → **`js_evaluate`** parsing the script tag.
+
+5. **Console → `sessionStorage`** — MSAL/OAuth tokens needed as Bearer for API calls → **`js_evaluate`** polling sessionStorage then calling fetch with the token.
+
+6. **Network tab → invisible transports** — requests missing from `window.fetch` interception (MCAS proxy, Service Workers) → **`js_evaluate`** with fetch interception, potentially requiring CDP `Fetch.enable`. Read [`RECON-PLAYBOOK.md`](RECON-PLAYBOOK.md) technique 5 before going this route.
+
+**Record during recon:**
+- Exact hostname(s) → `domains`
+- API endpoint or DOM selectors
+- Response shape (field names, types) → `columns`
+- Auth mechanism (SSO redirect, MFA, token polling, session cookies)
+- Proxy layers (MCAS `*.mcas.ms`, Cloudflare, etc.)
+
+**Completion:** You can name the pattern and have the target URL, data shape, and auth mechanism documented.
+
+---
+
+## Step 2: Scaffold the YAML
+
+Create the `.yaml` file in `~/.commandgarden/connectors/` for rapid iteration (daemon loads this directory without rebuild).
+
+```yaml
+site: <sitename>
+name: <command-name>
+version: "1.0"
+description: "<what data this connector returns>"
+access: read
+
+domains:
+  - "<exact hostname from recon>"
+capabilities:
+  - navigate
+  # add others based on chosen pattern
+
+args:
+  - name: <argname>
+    type: string
+    required: true
+    help: "<what this arg does>"
+    # optional: pattern, enum, default
+
+columns:
+  - name: <fieldname>
+    type: string  # or number, boolean
+
+pipeline: []
+```
+
+The full connector schema is defined in `shared/src/connector.ts` (Zod). Validation rules:
+- Every hostname in `navigate`/`fetch`/`cookie` URLs must appear in `domains`.
+- Every pipeline step's required capability must appear in `capabilities`.
+- `js_evaluate` steps require either `code` or `file`.
+
+Run `cg validate <path>` — it should report only the empty-pipeline error, nothing else.
+
+**Completion:** `cg validate` reports only the pipeline-length schema error.
+
+---
+
+## Step 3: Implement the pipeline
+
+Fill in `pipeline` based on the pattern from recon.
+
+Read [`docs/connector-authoring.md`](../../docs/connector-authoring.md) for pattern templates (fetch→map, extract, extract_tree, js_evaluate, __NEXT_DATA__) and [`docs/pipeline-reference.md`](../../docs/pipeline-reference.md) for the full step reference.
+
+**Key rules for `js_evaluate` eval.js files:**
+
+- **No IIFE wrapper.** The runner wraps code in `new AsyncFunction()`. A `return` inside `(function(){ ... })()` exits the inner function — the outer function gets `undefined` and the pipeline silently produces 0 rows.
+- **`await` works** at the top level.
+- **Template variables** `${{ args.name }}` are interpolated before execution. Quote them: `const x = '${{ args.date }}'`.
+- **Return** an array of objects to set pipeline data. Or use `as:` on the step to store a single value as a variable.
+- **Poll for auth** — SSO redirects take time. Poll `sessionStorage` or a DOM signal in a loop with a 30–60s deadline.
+
+Create the `.eval.js` file **next to** the YAML. See existing examples in `connectors/` for each pattern.
+
+**Completion:** `cg validate <path>` passes clean. If using `js_evaluate`, the `.eval.js` file exists.
+
+---
+
+## Step 4: Debug loop
+
+The loop: **run → read audit → probe → fix → repeat.**
+
+### First run
+
+```bash
+# Approve if using js_evaluate
+cg config set security.approvedHighRisk <site>/<name>
+
+cg run <site>/<name> --format json
+```
+
+### Read the audit log (always do this first)
+
+```bash
+cg audit export --format json --since 5m
+```
+
+Check `steps[]` — per-step timing and errors. See the symptom→cause table in [`docs/connector-authoring.md` § Debugging Connectors](../../docs/connector-authoring.md#debugging-connectors).
+
+### When the audit log isn't enough
+
+Read [`RECON-PLAYBOOK.md`](RECON-PLAYBOOK.md) for ground-layer probing:
+
+- **Strip the pipeline** — remove steps from the end until data flows, add back one at a time.
+- **Raw output** — remove `map` step, run with `--format json` to see actual field names.
+- **Console injection** — `console.log()` in eval.js, watch in DevTools.
+- **window.fetch interception** — capture requests the page makes on its own.
+- **CDP Fetch.enable** — when `window.fetch` misses requests (MCAS, Service Workers).
+
+### Reload cycle
+
+The daemon caches eval.js contents at startup via `ConnectorRegistry.resolveFileRefs()`.
+
+| What changed | Minimum reload |
+|---|---|
+| WIP YAML/eval.js in `~/.commandgarden/connectors/` | Restart daemon: `cg down && cg up` |
+| Source YAML only (in `connectors/`) | `npm run build -w daemon && cg down && cg up` |
+| Source YAML + eval.js | `npm run build -w daemon && cg down && cg up` |
+| Extension code (chrome-adapter.ts) | `npm run build && cg down && cg up` + reload at `chrome://extensions` |
+
+**Fastest path:** Put WIP connector in `~/.commandgarden/connectors/`. Edit → restart daemon → test. No build step.
+
+**Completion:** `cg run` returns expected data rows consistently across 3+ runs. Audit log shows no unexpected step errors or delays.
+
+---
+
+## Step 5: Polish
+
+1. **Args** — add `pattern` for format validation (`"^\\d{4}-\\d{2}$"`), `enum` for fixed choices, `default` for optional args.
+2. **Columns** — declare every output field with correct `type`. Drives CLI table formatting.
+3. **Error messages** — in eval.js, throw with actionable text: `'Not signed in — log in and retry'`, `'No results for "${query}"'`.
+4. **Description** — one line: what data the connector returns, not how.
+5. **Validate + inspect:**
+   ```bash
+   cg validate <path>
+   cg list                        # shows in connector list
+   cg inspect <site>/<name>       # shows full definition with args
+   ```
+
+**Completion:** `cg validate` passes. `cg list` shows the connector. `cg inspect` shows args with help text. Bad args produce a helpful error. `cg run` with `--format table` formats columns correctly.

package/node_modules/@commandgarden/chrome/package.json

@@ -3,9 +3,6 @@
   "version": "1.0.1",
   "private": true,
   "type": "module",
-  "files": [
-    "dist"
-  ],
   "scripts": {
     "build": "node build.mjs",
     "test": "vitest run",

package/node_modules/@commandgarden/daemon/package.json

@@ -4,10 +4,6 @@
   "private": true,
   "type": "module",
   "main": "./dist/main.js",
-  "files": [
-    "dist",
-    "connectors"
-  ],
   "scripts": {
     "build": "tsc && node scripts/copy-connectors.mjs",
     "start": "node dist/main.js",

package/node_modules/@commandgarden/shared/package.json

@@ -5,9 +5,6 @@
   "private": true,
   "type": "module",
   "main": "./dist/index.js",
-  "files": [
-    "dist"
-  ],
   "types": "./dist/index.d.ts",
   "exports": {
     ".": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@commandgarden/cli",
-  "version": "2.14.2",
+  "version": "2.14.3",
   "description": "Enterprise browser automation CLI",
   "type": "module",
   "license": "MIT",