@launchsecure/launch-kit 0.0.29 → 0.0.30

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@launchsecure/launch-kit",
-  "version": "0.0.29",
+  "version": "0.0.30",
   "description": "LaunchSecure toolkit — launch-pod (pipeline), launch-chart (project graph MCP), launch-deck (visual playground MCP), launch-kit-beacon (feedback Web Component), launch-recall (file-watcher backup).",
   "license": "MIT",
   "author": "LaunchSecure - AutomateWithUs",
@@ -56,23 +56,6 @@
     "launch-course": "./dist/server/course-entry.js",
     "launch-beacon": "./dist/server/beacon-monitor-entry.js"
   },
-  "scripts": {
-    "build": "pnpm build:client && pnpm build:chart-client && pnpm build:deck-client && pnpm build:council-client && pnpm build:beacon && pnpm build:server",
-    "build:beacon": "vite build --config vite.beacon.config.ts && tsc -p tsconfig.beacon.json --emitDeclarationOnly --outDir dist/beacon/types",
-    "test:beacon": "vitest run --config vite.beacon.config.ts",
-    "test:radar": "vitest run --config vite.radar.config.ts",
-    "test:chart": "vitest run --config vite.chart.test.config.ts",
-    "build:deck-client": "vite build --config vite.deck.config.ts",
-    "build:council-client": "vite build --config vite.council.config.ts",
-    "build:client": "vite build",
-    "build:chart-client": "vite build --config vite.chart.config.ts",
-    "build:server": "esbuild src/server/cli.ts src/server/fb-wizard.ts src/server/graph-mcp-entry.ts src/server/chart-serve.ts src/server/deck-mcp-entry.ts src/server/deck-serve.ts src/server/council-entry.ts src/server/council-serve.ts src/server/recall-entry.ts src/server/init-entry.ts src/server/orbit-entry.ts src/server/course-entry.ts src/server/beacon-monitor-entry.ts src/server/parse-worker-entry.ts --bundle --platform=node --target=node18 --outdir=dist/server --external:node-pty --external:ws --external:typescript --external:web-tree-sitter --external:tree-sitter-typescript --external:cloudflared --external:pg --external:pg-native && rm -rf dist/server/public && cp -r ../claude-code-web/src/public dist/server/public && rm -rf dist/server/graph/queries && mkdir -p dist/server/graph && cp -r src/server/graph/queries dist/server/graph/queries",
-    "dev:client": "vite",
-    "dev:chart": "pnpm build:server && pnpm build:chart-client && node dist/server/graph-mcp-entry.js serve",
-    "dev:server": "pnpm build:server && node dist/server/cli.js",
-    "dev": "pnpm build:server && concurrently -k -n client,server -c cyan,magenta \"vite\" \"node dist/server/cli.js\"",
-    "prepublishOnly": "pnpm build"
-  },
   "files": [
     "dist",
     "prompts",
@@ -84,6 +67,7 @@
     "html-to-image": "^1.11.13",
     "node-pty": "^1.2.0-beta.12",
     "pg": "^8.13.0",
+    "pgsql-parser": "^17.9.15",
     "tree-sitter": "^0.21.1",
     "tree-sitter-typescript": "^0.23.2",
     "typescript": "^5.5.0",
@@ -92,8 +76,6 @@
     "ws": "^8.18.0"
   },
   "devDependencies": {
-    "@launchsecure/claude-code-web": "workspace:*",
-    "@launchsecure/ui": "workspace:*",
     "@types/node": "^20.0.0",
     "@types/pg": "^8.11.10",
     "@types/react": "^18.3.12",
@@ -117,6 +99,24 @@
     "react-router-dom": "^6.28.0",
     "tailwindcss": "^3.4.19",
     "vite": "^5.4.11",
-    "vitest": "^1.6.0"
+    "vitest": "^1.6.0",
+    "@launchsecure/claude-code-web": "0.0.1",
+    "@launchsecure/ui": "0.0.1"
+  },
+  "scripts": {
+    "build": "pnpm build:client && pnpm build:chart-client && pnpm build:deck-client && pnpm build:council-client && pnpm build:beacon && pnpm build:server",
+    "build:beacon": "vite build --config vite.beacon.config.ts && tsc -p tsconfig.beacon.json --emitDeclarationOnly --outDir dist/beacon/types",
+    "test:beacon": "vitest run --config vite.beacon.config.ts",
+    "test:radar": "vitest run --config vite.radar.config.ts",
+    "test:chart": "vitest run --config vite.chart.test.config.ts",
+    "build:deck-client": "vite build --config vite.deck.config.ts",
+    "build:council-client": "vite build --config vite.council.config.ts",
+    "build:client": "vite build",
+    "build:chart-client": "vite build --config vite.chart.config.ts",
+    "build:server": "esbuild src/server/cli.ts src/server/fb-wizard.ts src/server/graph-mcp-entry.ts src/server/chart-serve.ts src/server/deck-mcp-entry.ts src/server/deck-serve.ts src/server/council-entry.ts src/server/council-serve.ts src/server/recall-entry.ts src/server/init-entry.ts src/server/orbit-entry.ts src/server/course-entry.ts src/server/beacon-monitor-entry.ts src/server/parse-worker-entry.ts --bundle --platform=node --target=node18 --outdir=dist/server --external:node-pty --external:ws --external:typescript --external:web-tree-sitter --external:tree-sitter-typescript --external:cloudflared --external:pg --external:pg-native --external:pgsql-parser --external:libpg-query && rm -rf dist/server/public && cp -r ../claude-code-web/src/public dist/server/public && rm -rf dist/server/graph/queries && mkdir -p dist/server/graph && cp -r src/server/graph/queries dist/server/graph/queries",
+    "dev:client": "vite",
+    "dev:chart": "pnpm build:server && pnpm build:chart-client && node dist/server/graph-mcp-entry.js serve",
+    "dev:server": "pnpm build:server && node dist/server/cli.js",
+    "dev": "pnpm build:server && concurrently -k -n client,server -c cyan,magenta \"vite\" \"node dist/server/cli.js\""
   }
-}
+}

package/scaffolds/ls-marketplace/plugins/kit/skills/beacon-array.md

@@ -0,0 +1,107 @@
+---
+description: Show the array of launch-beacon monitor sessions via the launch-beacon MCP — which is most recent, how many events each has, last event time, suspected liveness. Use to confirm a session is being recorded, find an old session to inspect, or audit disk usage. Read-only.
+---
+
+# /kit:beacon-array
+
+Liveness + inventory across every `launch-beacon monitor` session this repo has recorded — one row per beacon in the array.
+
+Parse `$ARGUMENTS` as space-separated tokens, in any order:
+- `full` — expanded report. Empty → terse one-line-per-session summary.
+- `--worktree=<slug>` — orbit worktree slug. Forwarded to MCP as the `worktree` arg.
+- `--project_root=<path>` — explicit project root (absolute, or relative to cwd). Forwarded as `project_root`. Takes precedence over `--worktree`.
+
+Examples:
+- `/kit:beacon-array` → terse one-line-per-session summary
+- `/kit:beacon-array full` → expanded report
+- `/kit:beacon-array --worktree=beacon_rewrite` → enumerate sessions captured in that worktree
+- `/kit:beacon-array full --worktree=beacon_rewrite` → expanded report for that worktree
+
+## Enumerate sessions
+
+Call `mcp__local-launch-beacon__beacon_sessions`, forwarding `worktree` / `project_root` if supplied. Returns an array of per-session summaries: token, event count, kind breakdown, first/last seq, last event timestamp.
+
+If the response is `{sessions: []}` OR `{error: ...}`, **alert the user with the exact MCP error string**, then walk the fallback below — do NOT silently `ls`.
+
+**Fallback when the MCP returns nothing:**
+1. If the user did NOT pass `--worktree` / `--project_root` and `launch-orbit` has worktrees registered for this repo, suggest re-running with `--worktree=<slug>` before falling back to the filesystem.
+2. Look for `.launchsecure/beacon-*.ndjson` in cwd, then in up to 2 parent dirs. Use the `Read` tool — never `ls`, `find`, or globbing as the primary path.
+3. If files are found at an alternative path, tell the user the path mismatch explicitly: `"MCP scans <root>/.launchsecure/ but sessions live at <found-path>. Reading directly."`
+4. If nothing is found anywhere, stop with: `"No beacon sessions found in .launchsecure/. Start one with: npx launch-beacon monitor"`.
+
+## Per-session facts
+
+For each session the MCP returns:
+- **token** — session id
+- **events** — total event count
+- **last_ts** — last event timestamp (epoch ms)
+- **last_kind** — kind of the last event (read from the kind breakdown's most-recent entry, or call `beacon_event(seq: last_seq)` for certainty)
+- **kinds** — kind breakdown map (`{click: 142, fetch: 71, …}`)
+- **first_seq / last_seq** — bounds
+
+Compute **age** from `last_ts` (current epoch minus `last_ts`):
+- < 5s → "just now"
+- < 60s → "Ns ago"
+- < 1h → "Nm ago"
+- < 24h → "Nh ago"
+- else → "Nd ago"
+
+## Liveness heuristic
+
+- **active** — `last_ts` is within the last 5 seconds (matches the receiver's batch-flush interval)
+- **idle** — between 5 seconds and 30 minutes
+- **stale** — older than 30 minutes (the receiver enforces a 30-min cap)
+
+## Default output (no arguments)
+
+```
+.launchsecure/
+  ● 8f3c2a91     247 events    click (just now)        ACTIVE
+    a1b2c3d4      89 events    error (12m ago)         idle
+    2557799f   1,247 events    route (2h ago)          stale
+
+3 sessions, 1 active.
+```
+
+Rules:
+- Glyph: `●` (filled) for active, blank for idle/stale.
+- Columns: token (8 chars) — events (right-aligned, thousands-separated) — last event "kind (age)" — status word.
+- Sort newest-first by `last_ts`.
+- Summary line: total count + how many active.
+- Plain text, monospace alignment.
+
+## Full output (`/kit:beacon-array full`)
+
+Same per-session block as default, then expand each:
+
+```
+● 8f3c2a91 — ACTIVE
+   events:      247
+   last event:  2026-05-26T12:20:51Z (just now)
+   last kind:   click
+   kinds:       click 142, fetch 71, route 12, error 3, dialog 9, probe 10
+   seq range:   1–247
+   started:     2026-05-26T12:12:33Z (8m ago)
+
+  a1b2c3d4 — idle
+   ...
+```
+
+For the `started` timestamp, call `mcp__local-launch-beacon__beacon_event` with `seq: <first_seq>, session: <token>` (and forward the same `worktree` / `project_root` args you used on `beacon_sessions`) and read its `ts`. Only do this for the full view — skip in the default view to keep it sub-second.
+
+`kinds:` formatted as `kind1 N1, kind2 N2, …` sorted by count desc, comma-separated.
+
+End with the same summary line as default.
+
+## File size
+
+The `beacon_sessions` summary does NOT include byte size. Both default and full views omit it — size isn't load-bearing for diagnosis. If the user explicitly asks ("how big is this file?"), fall back to `Read`-then-count or `wc -c` for that single file and tell them so: `"MCP doesn't expose byte size — falling back to wc -c."`.
+
+## Constraints
+
+- **MCP-first.** Use `beacon_sessions` and `beacon_event` — never `ls`, `wc`, `stat`, `tail`, `sed` as the primary path.
+- **Alert on fallback.** If the MCP can't answer, say so verbatim before reading the files directly.
+- **Read-only.** No deletion, no rotation, no auto-cleanup.
+- **Fast.** Default view should be sub-second even with many sessions.
+- **Plain text.** No markdown tables, no fenced blocks in the actual output.
+- **Don't suggest cleanup.** That's `/kit:beacon-clear`'s job. Stale sessions are informational, not an error.

package/scaffolds/ls-marketplace/plugins/kit/skills/beacon-clear.md

@@ -0,0 +1,94 @@
+---
+description: Soft-delete launch-beacon monitor session NDJSON files. Default clears only the latest session (so you can start a clean repro); pass `all` to clear every `.launchsecure/beacon-*.ndjson`. Always shows what will be cleared and asks for confirmation. Recoverable from `.launchsecure/.trash/<ts>/`.
+---
+
+# /kit:beacon-clear
+
+Clean slate before a fresh repro. The receiver appends to the same NDJSON file across reconnects of the same session, so an existing file accumulates noise from earlier attempts — clearing first makes the new stream easier to reason about.
+
+Parse `$ARGUMENTS` as space-separated tokens, in any order:
+- empty → clear the most recent session file only
+- `all` → clear every `.launchsecure/beacon-*.ndjson` in the target dir
+- a specific token or filename → clear that one file (must match a real path)
+- `--worktree=<slug>` — orbit worktree slug. Forwarded to MCP as the `worktree` arg; the soft-delete acts on the worktree's `.launchsecure/`.
+- `--project_root=<path>` — explicit project root (absolute, or relative to cwd). Forwarded as `project_root`. Takes precedence over `--worktree`.
+
+Examples:
+- `/kit:beacon-clear` → clear the most recent session in cwd's `.launchsecure/`
+- `/kit:beacon-clear all` → clear every session in cwd's `.launchsecure/`
+- `/kit:beacon-clear all --worktree=beacon_rewrite` → clear every session in that worktree's `.launchsecure/`
+
+## Enumerate candidates
+
+Call `mcp__local-launch-beacon__beacon_sessions`, forwarding `worktree` / `project_root` if supplied. Use `token`, `last_ts`, `events`, and `path` (absolute) from the response. **The filesystem operations below MUST use `path` from this response — never reconstruct paths from `.launchsecure/beacon-<token>.ndjson` relative to cwd**, because with `--worktree` / `--project_root` the real directory is elsewhere.
+
+If the response is `{sessions: []}` OR `{error: ...}`, **alert the user with the exact MCP error string**, then walk the fallback below — do NOT silently `ls`.
+
+**Fallback when the MCP returns nothing:**
+1. If the user did NOT pass `--worktree` / `--project_root` and `launch-orbit` has worktrees registered for this repo, suggest re-running with `--worktree=<slug>` before falling back to the filesystem.
+2. Look for `.launchsecure/beacon-*.ndjson` in cwd, then in up to 2 parent dirs. Use the `Read` tool — never `ls`, `find`, or globbing as the primary path.
+3. If files are found at an alternative path, tell the user the path mismatch and ASK before proceeding — the user may not want to clear files at an unexpected location.
+4. If nothing is found anywhere, stop with: `"No beacon sessions found in .launchsecure/. Nothing to clear."`.
+
+## Decide target set
+
+- empty → most-recent session (highest `last_ts`)
+- `all`  → every session the MCP returned
+- otherwise → resolve `$ARGUMENTS` to a single token: try the literal arg first as a session id, then strip a `.ndjson` suffix, then try matching against the filename portion of a path containing `beacon-<token>.ndjson`. Refuse with a clear message if none match.
+
+## Refusal rules
+
+Refuse with a clear message if:
+- the target set is empty
+- any target resolves outside `.launchsecure/` (defence against `..` injection from `$ARGUMENTS` — even if the user passes an absolute path)
+- the active session is being written *right now* (`last_ts` within the last 5 seconds) — print a one-line warning and ask the user to stop the monitor first:
+  ```
+  ⚠ .launchsecure/beacon-8f3c2a91.ndjson was last written 2s ago — looks active.
+    Stop the receiver (Ctrl+C in the launch-beacon monitor terminal) and re-run /kit:beacon-clear.
+  ```
+  The user can still force by passing the token explicitly — but never silently nuke an actively-written file.
+
+## Confirmation
+
+Print what's about to be moved and ask before doing it.
+
+```
+About to soft-delete 1 file:
+  .launchsecure/beacon-a1b2c3d4.ndjson   89 events, 12m ago
+
+Recoverable from .launchsecure/.trash/<UTC-timestamp>/ until manually purged.
+
+Confirm? (y/N)
+```
+
+For `all`, list every file with event count + age. Don't truncate.
+
+Wait for explicit `y`/`yes`. Anything else → abort with `Cancelled. No files were moved.`
+
+## Soft-delete (move, don't rm)
+
+Create `<sessionDir>/.trash/<UTC-ISO-timestamp>/` and `mv` each target into it, where `<sessionDir>` is `dirname(path)` from the `beacon_sessions` response — NOT a hard-coded `.launchsecure/`. This matters when `--worktree` or `--project_root` was passed, because the dir is then the worktree's `.launchsecure/`, not cwd's. **Never `rm`.** This is the mitigation for the recall coverage gap — recall doesn't snapshot `.launchsecure/*` today (tracked in LS work item #144). Soft-delete preserves the option to recover within the same machine.
+
+```bash
+SESSION_DIR=$(dirname "<path-from-beacon_sessions>")  # e.g. /repo/.claude/worktrees/foo/.launchsecure
+TRASH="$SESSION_DIR/.trash/$(date -u +%Y%m%dT%H%M%SZ)"
+mkdir -p "$TRASH"
+mv "$SESSION_DIR/beacon-<token>.ndjson" "$TRASH/"
+```
+
+After the move, print:
+
+```
+✓ moved 1 file to .launchsecure/.trash/20260526T142233Z/ (89 events archived).
+  Recover with: mv .launchsecure/.trash/20260526T142233Z/beacon-a1b2c3d4.ndjson .launchsecure/
+```
+
+For `all`, print the count and the trash dir once; don't list every recovery command.
+
+## Constraints
+
+- **MCP-first for enumeration.** Use `beacon_sessions` — never `ls` as the primary path.
+- **Destructive — always confirm.** Even if `$ARGUMENTS` is `all`, ask first.
+- **Scope-locked to the session dir.** The session dir is `dirname(path)` from `beacon_sessions` (typically `.launchsecure/`, but `<worktree>/.launchsecure/` when `--worktree`/`--project_root` is passed). Reject any target outside the dir the MCP told you about, even if the user passes an absolute path. We never touch files we didn't write.
+- **Soft-delete only.** Never `rm` — always `mv` into `.launchsecure/.trash/<ts>/`. The trash dir is not auto-pruned; cleaning it up is a deliberate user action.
+- **Don't stop the monitor server.** This command only moves files. The receiver keeps running and will reopen the same file on its next write — which is fine, the file just starts empty again.

package/scaffolds/ls-marketplace/plugins/kit/skills/beacon-pulse.md

@@ -0,0 +1,82 @@
+---
+description: Show the most recent failure from the active launch-beacon monitor session, plus the N events that preceded it (default 10). Answers "what was happening when it broke" without scrolling through the full stream. Read-only.
+---
+
+# /kit:beacon-pulse
+
+The "what happened just before this failure" command — a single pulse, freezing the moment the beacon caught a failure. When a bug fires, the actual story is usually the chain of events leading up to it: the click that triggered a state change, the failed fetch that left auth in a bad state, the route change that mounted the wrong component.
+
+A "failure" here is anything `mcp__local-launch-beacon__beacon_failures` returns — window errors, unhandled rejections, fetch/xhr with status ≥ 400 or thrown, and clicks where overlay interception blocked the intended target. Broader than just `kind=error`; matches what users mean when they say "something broke."
+
+Parse `$ARGUMENTS` as space-separated tokens, in any order:
+- An optional **integer** — the count of preceding events to include. Default 10. Cap at 50 (the `beacon_correlate.before` tool limit).
+- `--worktree=<slug>` — orbit worktree slug. Forwarded to every MCP call as the `worktree` arg.
+- `--project_root=<path>` — explicit project root (absolute, or relative to cwd). Forwarded as `project_root`. Takes precedence over `--worktree`.
+
+Examples:
+- `/kit:beacon-pulse` → 10 events before the latest failure
+- `/kit:beacon-pulse 25` → 25 events before
+- `/kit:beacon-pulse --worktree=beacon_rewrite` → query a worktree's session
+
+## Locate the most recent failure
+
+Call `mcp__local-launch-beacon__beacon_failures` with `limit: 1` (and `worktree` / `project_root` if the user supplied them). The tool implicitly targets the most recent session.
+
+If the response is `{error: "no session found"}` OR an empty failures array, **alert the user with the exact MCP error string**, then walk the fallback below — do NOT silently grep. The MCP can come up empty for two non-bug reasons: (a) no session has been started, (b) the session NDJSON lives outside the MCP's watch root (e.g. inside an orbit worktree the user didn't name).
+
+**Fallback when the MCP returns nothing:**
+1. If the user did NOT pass `--worktree` / `--project_root` and `launch-orbit` has worktrees registered for this repo, suggest re-running with `--worktree=<slug>` before falling back to the filesystem.
+2. Look for `.launchsecure/beacon-*.ndjson` in cwd, then in up to 2 parent dirs. Use the `Read` tool to inspect the most-recently-modified matching file — do NOT use `grep`, `find`, or `ls` as the primary path.
+3. If files are found at an alternative path, tell the user the path mismatch explicitly: `"MCP scans <root>/.launchsecure/ but the session lives at <found-path>. Reading directly."`
+4. If nothing is found anywhere, stop with: `"No beacon sessions found. Start one with: npx launch-beacon monitor"`.
+
+Capture the failure's `seq`, `kind`, `ts`, and message.
+
+## Pull the context window
+
+Call `mcp__local-launch-beacon__beacon_correlate` with `seq: <failure.seq>`, `before: N`, `after: 0`, plus the same `worktree` / `project_root` args you used on `beacon_failures`. The tool returns event summaries directly — no JSON parsing required.
+
+If a context event's summary is missing detail you need for analysis (truncated stack, missing response body, selector chain), call `mcp__local-launch-beacon__beacon_event` with that event's specific `seq` for the full JSON — and forward the same root args. Only do this when the summary is insufficient — not unconditional.
+
+## Output
+
+Render a **timeline** with the failure visually separated at the bottom:
+
+```
+session: <token>
+window:  N events before failure at seq <seq>
+
+12:34:51  click       button.submit-btn
+12:34:51  fetch       POST 401 /api/sessions (120ms)  FAILED
+12:34:51  fetch       GET 401 /api/me (45ms)  FAILED
+12:34:52  route       /login → /dashboard (pushState)
+...
+
+╴╴╴╴ FAILURE ╴╴╴╴
+12:34:53  error       Cannot read properties of undefined (reading 'orgSlug')
+              at apps/Console.tsx:42:18
+              stack: Console.render
+                     React.renderWithHooks
+                     React.beginWork
+```
+
+Format rules:
+- One line per event, same SUMMARY format as `/kit:beacon-scan`.
+- The failure block at the end gets the message + (truncated) stack frames if present. For fetch/xhr failures, include method + status + url + response body summary.
+- Separator above the failure is the visual cue.
+
+After the timeline, write **one short paragraph** of analysis: what does the chain *look* like? Common patterns:
+- 401s → error referencing user/org → "auth expired or org context missing"
+- click → no observable effect → click again → error → "first click handler crashed silently; second click landed on something else"
+- route change → error → "component on the new route blew up during initial render"
+- repeated 400s on the same endpoint → "request shape mismatch — check the server's Zod schema against the client payload"
+
+Don't dive into a fix — name the suspected proximate cause, suggest one concrete next step (which file to read, which probe to add, which `/kit:beacon-scan <kind>` to drill into).
+
+## Constraints
+
+- **MCP-first.** Use `beacon_failures`, `beacon_correlate`, `beacon_event` — never `grep`, `find`, `ls`, `sed`, `cut`, or `tail` as the primary path.
+- **Alert on fallback.** If the MCP can't answer, say so verbatim before reading the file directly.
+- **Read-only.**
+- **Most recent failure only.** For an earlier one, clear the session (`/kit:beacon-clear`) and reproduce, or use `/kit:beacon-scan error` / `/kit:beacon-scan fetch` to browse.
+- **Plain text.** Same monospace conventions as `/kit:beacon-scan`.

package/scaffolds/ls-marketplace/plugins/kit/skills/beacon-scan.md

@@ -0,0 +1,66 @@
+---
+description: Scan recent events from the active launch-beacon monitor session via the launch-beacon MCP. Defaults to last 50 events across all kinds; pass a kind (`error`, `click`, `fetch`, `route`, `dialog`, `probe`, etc.) to filter, and/or a numeric limit. Read-only.
+---
+
+# /kit:beacon-scan
+
+Recent runtime events captured by a `launch-beacon monitor` session. Use this as the first step when investigating something that just happened in the browser — clicks, failed network calls, errors, route changes, probe() calls, dialog mount/unmount.
+
+Parse `$ARGUMENTS` as space-separated tokens, in any order:
+- A **kind filter**: one of `error`, `unhandledrejection`, `fetch`, `xhr`, `click`, `mousedown`, `route`, `dialog`, `submit`, `probe`. Anything else that doesn't parse as an integer or a known `--flag` is treated as an explicit session token.
+- A **limit**: integer. Default 50. Hard cap 500 (the `beacon_recent.limit` tool ceiling).
+- An explicit **session token** (8-char hex like `8f3c2a91`) — passed straight through as the `session` MCP arg.
+- `--worktree=<slug>` — orbit worktree slug (from `launch-orbit create`). Forwarded to the MCP as the `worktree` arg so a Claude session pinned to the main repo can read sessions captured inside a worktree.
+- `--project_root=<path>` — explicit project root (absolute, or relative to cwd). Forwarded to the MCP as `project_root`. Takes precedence over `--worktree`.
+
+Examples:
+- `/kit:beacon-scan` → last 50 events of any kind from the latest session
+- `/kit:beacon-scan error` → last 50 errors only
+- `/kit:beacon-scan click 20` → last 20 click events
+- `/kit:beacon-scan 100` → last 100 events of any kind
+- `/kit:beacon-scan fetch 50 8f3c2a91` → last 50 fetches from a specific session
+- `/kit:beacon-scan fetch --worktree=beacon_rewrite` → last 50 fetches captured in that worktree
+
+## Scan
+
+Call `mcp__local-launch-beacon__beacon_recent` with `kind: <kind?>`, `limit: <limit>`, `session: <session?>`, plus `worktree: <slug?>` and `project_root: <path?>` if the user supplied them. The tool defaults to the most-recent session and returns one compact summary line per event.
+
+If the response is `{error: "no session found"}` OR an empty events array, **alert the user with the exact MCP error string**, then walk the fallback below — do NOT silently grep.
+
+**Fallback when the MCP returns nothing:**
+1. If the user did NOT pass `--worktree` / `--project_root` and the cwd is the main repo of a project that has worktrees registered with `launch-orbit`, suggest re-running with `--worktree=<slug>` before falling back to the filesystem — that's usually the actual fix and avoids a wrong-directory scan.
+2. Look for `.launchsecure/beacon-*.ndjson` in cwd, then in up to 2 parent dirs. Use the `Read` tool to inspect the most-recently-modified matching file — do NOT use `grep`, `find`, or `ls` as the primary path.
+3. If files are found at an alternative path, tell the user the path mismatch explicitly: `"MCP scans <root>/.launchsecure/ but the session lives at <found-path>. Reading directly."`
+4. If nothing is found anywhere, stop with: `"No beacon sessions found. Start one with: npx launch-beacon monitor"`.
+
+## Output
+
+Group events by **time** (most recent last — chronological matches user intuition for "what happened"). For each event, render one line:
+
+```
+HH:MM:SS  KIND     SUMMARY
+```
+
+Where SUMMARY is a one-liner pulled from the event body:
+- **error / unhandledrejection** → `message` (truncate ≤ 80 chars)
+- **fetch / xhr** → `METHOD status url (durationMs)` — flag `FAILED` if `failed:true`
+- **click / mousedown** → `target.selector` and, when `hitMatchesTarget === false`, also append `(occluded by <hitTarget.selector>)` — that's exactly the diagnostic the user is here for
+- **route** → `from → to (via)`
+- **dialog** → `<action> <selector>` (e.g. `mount dialog#xyz` or `unmount section[role=dialog]`)
+- **submit** → `<form selector> (preventDefault?)`
+- **probe** → `<label>: <truncated JSON>`
+
+If a summary line is missing detail you need (truncated response body, full selector chain, stack frames), call `mcp__local-launch-beacon__beacon_event` with that event's `seq` for the full JSON — and forward the same `worktree` / `project_root` args you used on `beacon_recent`. Only on demand — not unconditional.
+
+After the timeline, if anything looks suspicious (clusters of failed network calls, a click followed by no observable effect, a `hitMatchesTarget:false` event, an unhandled rejection), call it out in **one short paragraph** at the end. Don't analyze every event — only surface the standouts.
+
+If the buffer is empty after filtering, say so: `No events match that filter in <session>.`
+
+## Constraints
+
+- **MCP-first.** Use `beacon_recent` / `beacon_event` — never `grep`, `find`, `ls`, `tail`, `head` as the primary path.
+- **Alert on fallback.** If the MCP can't answer, say so verbatim before reading the file directly.
+- **Read-only.** Never delete, modify, or write to the NDJSON file. Wiping is `/kit:beacon-clear`.
+- **Always use the latest session by default.** Pass an explicit token as the third arg only when the user wants a specific older session.
+- **Plain text output.** Monospace alignment beats markdown tables here.
+- **Don't speculate on root cause.** Surface anomalies; let the user direct the next query (often: `/kit:beacon-pulse` for context around the latest failure).

package/scaffolds/ls-marketplace/plugins/kit/skills/blast-radius.md

@@ -0,0 +1,101 @@
+---
+description: Build a blast radius for a file/table/endpoint via launch-chart and push it to launch-deck as an interactive radial graph. Use to assess "what breaks if I change X" before refactors, schema migrations, or API contract changes. Chart-first; on chart gaps (no nodes, missing layer, empty edges) files a feedback comment to LaunchSecure so the gap is monitored.
+---
+
+# /kit:blast-radius
+
+Calculate the reverse-dependency blast radius for a target node and visualise it as an interactive radial graph in launch-deck. The graph centres on the target and rings out by hop distance across all project layers (db / api / ui / static / etc.).
+
+Parse `$ARGUMENTS`:
+- **target** (required) — a node id from the project graph (file path like `lib/permissions/types.ts`, table name like `User`, endpoint id like `POST /api/work-items`). If absent, ask the user.
+- **hops=N** — max traversal depth. Default 2.
+- **layer=<id>** — restrict to one layer when the same name exists in multiple layers (e.g. `layer=db`).
+- **--session=<id>** — deck session name. Default `blast-<target-slug>`.
+- **--mode=feature** — render with feature rings (modify / create / ripple) instead of the default structural rings (hop1 / hop2). Use when the radius represents planned change scope rather than pure structural reachability.
+
+Examples:
+- `/kit:blast-radius lib/permissions/types.ts`
+- `/kit:blast-radius User layer=db hops=3`
+- `/kit:blast-radius POST /api/work-items --mode=feature`
+
+## Preflight
+
+1. Confirm both MCPs are wired — `mcp__launch-chart__chart_server_status` and `mcp__launch-deck__server_status`. If either is missing, stop and tell the user to run `npx @launchsecure/launch-kit refresh` (or `npx launch-deck` for the deck server).
+2. Run `mcp__launch-chart__detect_project_stack` once. Cache the returned `layers` for the bug-report fallback below.
+
+## 1. Compute the blast points
+
+Call `mcp__launch-chart__blast_points` with `node_id: <target>`, `hops: <hops>`, `direction: "reverse"`, and `layer` if supplied. The tool returns affected nodes (with hop, type, layer, module) plus a summary.
+
+**Chart-gap detection** — if any of these are true, file a feedback comment per the shared `chart-gap` protocol below before stopping:
+- `error` is set
+- `nodes` is empty AND the user explicitly named a node id that exists on disk (verify by `Read`-ing the path)
+- `summary.byLayer` covers fewer layers than `detect_project_stack` reported as available
+
+## 2. Build the manifest
+
+Translate the blast_points result into the deck `blast-radius` block manifest shape. Reuse layer ids/icons/colors from `detect_project_stack` so the visual matches the project's conventions; fall back to:
+- db → `database`, `#172554`
+- api → `server`, `#1e3a5f`
+- ui → `layout-dashboard`, `#0c4a6e`
+- static → `file-text`, `#374151`
+- shared → `puzzle`, `#4338ca`
+- middleware → `shield`, `#1f2937`
+- config → `cog`, `#52525b`
+
+Rings:
+- structural mode (default): `[{id:"hop1",name:"Direct",color:"#f97316"},{id:"hop2",name:"Indirect",color:"#eab308"}]`
+- feature mode: `[{id:"modify",name:"Modify",color:"#f97316"},{id:"create",name:"Create",color:"#22c55e"},{id:"ripple",name:"Ripple",color:"#eab308"}]`
+
+Centre node: `{ name: <target>, description: "<N> direct, <M> indirect (<hops> hops)" }`.
+
+Nodes: map each blast result row to `{ id, name, layer, ring: hop===1 ? "hop1" : "hop2", path, type }`.
+
+Edges: connect the centre to every hop=1 node; connect each hop=2 node to one hop=1 ancestor from its dependency chain (read from `blast_points` `via` field if present, otherwise pick any hop=1 node in the same layer).
+
+## 3. Push to deck
+
+Call `mcp__launch-deck__deck` with `session: <session>`, `mode: "show"`, `blocks: [{ type: "blast-radius", label: <target>, manifest: <built-manifest> }]`.
+
+If the deck server isn't running, call `mcp__launch-deck__start_server` first, then retry. Report the deck URL back to the user.
+
+## Output
+
+After the push, print a terse summary:
+
+```
+blast-radius for <target> — <N> direct, <M> indirect (<hops> hops)
+  by layer: db 4, api 7, ui 12
+  pushed to deck session "<session>" — http://localhost:52829/?session=<session>
+```
+
+## Chart-gap protocol (shared)
+
+When the chart MCP returns less data than expected, file ONE feedback comment in the project's Comm Hub (cloud LS by default per project memory — use `mcp__launch-secure__communication_write`, not the local variant) before stopping:
+
+```
+resource_type: "feedback"
+title: "launch-chart gap: <one-line>"
+body: |
+  Skill: /kit:blast-radius
+  Tool:  blast_points(node_id=<id>, hops=<n>, layer=<layer?>)
+  Returned: <nodes_count> nodes, layers=<layers_seen>
+  Expected: <what-was-expected, e.g. "node exists at <path>" or "layer X should appear">
+  Project stack: <one-line summary from detect_project_stack>
+fields:
+  severity: "low"
+  source: "kit-skill"
+  skill: "blast-radius"
+  tool: "blast_points"
+  args: { node_id, hops, layer }
+  response_summary: { nodes_count, layers_seen, error }
+```
+
+Do NOT spam — file at most one comment per skill invocation. After filing, tell the user "Filed chart-gap report to LS (id: …). Falling back to read_graph + Read." and continue with a degraded path: try `mcp__launch-chart__read_graph` with `search: <target>` to confirm the node exists in any layer; if so, do the blast-radius math from `include_edges: true` results manually; otherwise stop and surface the gap to the user.
+
+## Constraints
+
+- **MCP-first.** Never grep the filesystem to build the manifest — use `blast_points` and `read_graph`.
+- **Idempotent on re-run.** Re-pushing to the same session overwrites the previous render — that's fine, just tell the user.
+- **Single bug-file per run.** Don't file a comment for every gap; bundle into one report.
+- **Plain text output.** No markdown tables, no fenced blocks in the human-facing summary.

package/scaffolds/ls-marketplace/plugins/kit/skills/brief.md

@@ -0,0 +1,112 @@
+---
+description: Create or update a repo-backed Brief in the LaunchSecure Comm Hub per the LS Briefs framework — Discovery-plane document (docCategory=features) authored as a comment that's also synced to a markdown file in the repo. Use to capture an idea before promoting it to an Epic.
+---
+
+# /kit:brief
+
+A **Brief** is an LS Discovery-plane artefact: a long-form description of a problem/opportunity, authored as a comment in the project's Comm Hub AND backed by a markdown file in the repo (`docs/requirements/features/<slug>.md` by convention). It's the structured alternative to a free-form Discussion when the idea has enough shape to write down. Briefs get promoted to Epics on the Roadmap once they're DECIDED.
+
+Parse `$ARGUMENTS`:
+- **subcommand** (required) — `new` | `update` | `list` | `show`.
+- For **new**: `<title>` (required), `--from=discussion:<id>` to seed body from an existing discussion thread, `--module=<slug>` to tag.
+- For **update**: `<brief-id-or-slug>` and either a body description (re-generates body) or `--append=<text>` to add a section.
+- For **list**: `[--module=<slug>] [--status=open|decided|declined]`.
+- For **show**: `<brief-id-or-slug>`.
+
+Examples:
+- `/kit:brief new "Channels for Comm Hub" --module=communication`
+- `/kit:brief new "Roadmap nav" --from=discussion:cmt_abc123`
+- `/kit:brief list --status=open`
+- `/kit:brief show channels-for-comms`
+- `/kit:brief update channels-for-comms --append="Resolved: use the Slack metaphor not Teams."`
+
+## Preflight
+
+1. Confirm `mcp__launch-secure__ping` works (the cloud LS MCP must be wired). If only `mcp__local-launch-secure__*` is wired, ask the user whether to post to local or cloud — default per project memory is CLOUD.
+2. For `new`, sanity-check that no existing brief with the same slug already exists — call `mcp__launch-secure__communication_read` filtered by `resourceType=comment` and search the title. If a match is found, ask whether to update instead.
+
+## The Brief shape
+
+Per the LS Briefs framework (`docs/requirements/work-items/roadmap-and-hierarchy.md`):
+
+- **resourceType**: `comment` (Briefs are comments)
+- **docCategory**: `features` (this is what file-backed sync watches)
+- **title**: the human-friendly name; the slug is derived
+- **body**: the long-form markdown — sections below
+- **file_links**: not used here; the FileBackedEntity link is created by LS server-side on first save
+- **tags**: optional module tag, plus a `brief` tag for filtering
+
+### Body template
+
+When generating a NEW brief, use this skeleton (markdown body):
+
+```markdown
+# <Title>
+
+**Status**: PROPOSED  
+**Owner**: <user-mention or "unassigned">  
+**Module**: <module slug or "-">
+
+## Problem
+
+<1-2 paragraphs — what's broken or missing, who feels it, why now>
+
+## Proposed direction
+
+<1-3 paragraphs — the shape of the solution, not the implementation>
+
+## Out of scope
+
+- <bullets — what this brief deliberately does NOT cover>
+
+## Open questions
+
+- [ ] <bullets — what we still need to decide before this can become an Epic>
+
+## Success looks like
+
+<1-2 sentences — observable outcome, not "ship X">
+
+## References
+
+- <link to existing code via launch-chart node id (use mcp__launch-chart__read_graph to find the right nodes; cite them as `lib/foo/bar.ts:42`)>
+- <related comments by id>
+```
+
+The body is plain markdown — Comm Hub renders it. Use launch-chart to add real code references (don't invent file paths).
+
+## Write paths
+
+### new
+
+1. Build the body from the template + the user's description (or the `--from=discussion:<id>` seed — fetch via `communication_read` and weave the relevant points into the Problem/Proposed-direction sections).
+2. Call `mcp__launch-secure__communication_write` with:
+   - `title: <user-supplied>`
+   - `body: <generated-markdown>`
+   - `resource_type: "comment"`
+   - `fields: { docCategory: "features", briefStatus: "PROPOSED" }`
+   - `tag_ids: <module tag id + "brief" tag id>` (call `mcp__launch-secure__tags_list` first to resolve names → ids; if either tag doesn't exist, surface the missing tag(s) and proceed without)
+3. Print the returned comment id + URL.
+4. Tell the user: "LS server-side file-backed sync will materialize `docs/requirements/features/<slug>.md` on the next default-branch push that includes this brief — pull the branch to see it locally."
+
+### update
+
+1. Resolve `<brief-id-or-slug>` via `communication_read(resourceType: "comment", search: <slug>)`. If multiple match, list them and stop.
+2. If `--append=<text>`, fetch the current body, append the text under a `## Update <ISO-date>` heading, and call `mcp__launch-secure__communication_update` with the new body.
+3. If a fresh description was passed, regenerate the body from the template + new description, ask the user to confirm (show the diff briefly), then update.
+
+### list
+
+`mcp__launch-secure__communication_read` filtered by `resourceType=comment`, narrow on `docCategory=features` if the API supports it (otherwise pull a wider set and filter client-side by tag/status). Render one line per brief: `id  status  title  module  updated`.
+
+### show
+
+Fetch via `communication_read` and print the body as-is, no transformation.
+
+## Constraints
+
+- **Plain markdown body.** Per project memory `feedback_comms_plain_text.md`, comms posts are plain — no HTML, no emojis unless the user wrote them.
+- **One brief, one comment.** Don't fragment a brief across multiple comments — append via `--append` to keep the document continuous.
+- **Cloud LS by default.** Per memory `feedback_post_to_cloud_ls_default.md`. Local LS only when the user explicitly says "local".
+- **Cite real code.** Use launch-chart node ids in the References section — don't invent file paths.
+- **Don't auto-promote to Epic.** A Brief → Epic is a deliberate human action (project memory: bucket transitions are deliberate, not derived). Surface a hint at the end: "When DECIDED, run `/work-items create epic --from-brief=<id>` to promote."