@launchsecure/launch-kit 0.0.29 → 0.0.30

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

@@ -1,92 +0,0 @@
----
-description: Show the array of launch-beacon monitor sessions in `.launchsecure/` — 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.
-
-`$ARGUMENTS` may be `full` for an expanded report. Empty → terse one-line-per-session summary.
-
-## Preflight
-
-List the NDJSON files. If none, say so plainly:
-
-```bash
-ls -t .launchsecure/beacon-*.ndjson 2>/dev/null || { echo "No beacon sessions found in .launchsecure/. Start one with: npx launch-beacon monitor"; exit 0; }
-```
-
-If the listing is empty (the command above succeeded but produced no output because `2>/dev/null` swallowed the error and no files matched), check explicitly:
-
-```bash
-SESSIONS=$(ls -t .launchsecure/beacon-*.ndjson 2>/dev/null)
-test -n "$SESSIONS" || { echo "No beacon sessions found in .launchsecure/. Start one with: npx launch-beacon monitor"; exit 0; }
-```
-
-## Per-session facts to collect
-
-For each session file (newest first), gather:
-- **token** — slice between `beacon-` and `.ndjson` in the filename
-- **events** — `wc -l < <file>`
-- **last_ts** — parse the last JSON line's `.ts` field (epoch ms). Use a one-liner like:
-  ```bash
-  tail -n 1 "$F" | sed -n 's/.*"ts":\([0-9]*\).*/\1/p'
-  ```
-- **last_kind** — same trick on `.kind` from the last line
-- **mtime** — `stat -f "%m" "$F"` on macOS or `stat -c "%Y" "$F"` on Linux. Use whichever your shell supports; fall back to `ls -lt` parse if neither.
-- **size** — file size in bytes (`stat` again; or `wc -c < "$F"`)
-
-Use the mtime to compute **age** ("just now", "2m ago", "1h ago"). Do the arithmetic yourself (current epoch minus mtime); don't shell out for time formatting.
-
-## Liveness heuristic
-
-Mark a session as **active** if its mtime is within the last 5 seconds — that's the maximum interval the receiver flushes batches. Otherwise **idle**. Sessions older than 30 minutes are **stale** (the receiver enforces a 30-min cap, so anything older is from a previous monitor run).
-
-## 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) — last event "kind (age)" — status word.
-- Summary line: total count + how many active.
-- Plain text, monospace alignment.
-
-## Full output (`/kit:beacon-array full`)
-
-Same per-session block as default, but expand each into a block with extra fields:
-
-```
-● 8f3c2a91 — ACTIVE
-   file:        .launchsecure/beacon-8f3c2a91.ndjson
-   size:        42.1 KB
-   events:      247
-   started:     2026-05-21T07:12:33Z (8m ago)
-   last event:  2026-05-21T07:20:51Z (just now)
-   last kind:   click
-   kinds:       click 142, fetch 71, route 12, error 3, dialog 9, probe 10
-
-  a1b2c3d4 — idle
-   file:        .launchsecure/beacon-a1b2c3d4.ndjson
-   ...
-```
-
-`kinds:` is a histogram from `grep -oE '"kind":"[a-z]+"' <file> | sort | uniq -c | sort -rn`. Format as `kind1 N1, kind2 N2, …` newest-first by count.
-
-`started:` = first line's `.ts`; `last event:` = last line's `.ts`.
-
-End with the same summary line as default.
-
-## Constraints
-
-- **Read-only.** No deletion, no rotation, no auto-cleanup.
-- **Fast.** Default view should be sub-second even with many session files. Don't full-parse JSON — line counts + first/last line sed is enough.
-- **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/commands/beacon-clear.md

@@ -1,68 +0,0 @@
----
-description: Wipe launch-beacon monitor session NDJSON files. Default clears only the latest session (so you can start a clean repro); pass `all` to remove every `.launchsecure/beacon-*.ndjson`. Always shows what will be deleted and asks for confirmation. Destructive.
----
-
-# /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`:
-- empty → clear the most recent session file only
-- `all` → clear every `.launchsecure/beacon-*.ndjson`
-- a specific token or filename → clear that one file (must match a real path)
-
-## Preflight
-
-List candidate files. If none, say so and stop:
-
-```bash
-SESSIONS=$(ls -t .launchsecure/beacon-*.ndjson 2>/dev/null)
-test -n "$SESSIONS" || { echo "No beacon sessions found in .launchsecure/. Nothing to clear."; exit 0; }
-```
-
-Decide the **target set** based on `$ARGUMENTS`:
-- empty → first line of `$SESSIONS` (the newest)
-- `all`  → all lines of `$SESSIONS`
-- otherwise → resolve to a single path (try `.launchsecure/beacon-<arg>.ndjson` first, then the literal arg). If it doesn't exist or isn't inside `.launchsecure/`, refuse with a clear message.
-
-## Refusal rule
-
-Refuse with a clear message if:
-- the target set is empty
-- any target path resolves outside `.launchsecure/` (defence against `..` injection from `$ARGUMENTS`)
-- the active monitor session is being written *right now* (mtime within the last 5 seconds) — print a one-line warning and ask the user to stop the monitor first, e.g.:
-  ```
-  ⚠ .launchsecure/beacon-8f3c2a91.ndjson was 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 as the argument — but never silently nuke an actively-written file.
-
-## Confirmation
-
-Print what's about to be deleted and ask before doing it.
-
-```
-About to delete 1 file:
-  .launchsecure/beacon-a1b2c3d4.ndjson   89 events, 12m ago
-
-Confirm? (y/N)
-```
-
-For `all`, list every file with its size + age. Don't truncate the list — the user should see all of it.
-
-Wait for explicit `y`/`yes`. Anything else → abort with `Cancelled. No files were deleted.`
-
-## Delete
-
-`rm` each target. After deletion, print a one-line summary:
-
-```
-✓ deleted 1 file (89 events freed).
-```
-
-## Constraints
-
-- **Destructive — always confirm.** Even if `$ARGUMENTS` is `all`, ask first.
-- **Scope-locked to `.launchsecure/`.** Reject anything outside that directory, even if the user passes an absolute path. We never delete files we didn't write.
-- **No undo.** NDJSON is local-only; we don't ship recall integration for it (recall is for source files). Be explicit in the confirmation message.
-- **Don't stop the monitor server.** This command only clears 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/commands/beacon-pulse.md

@@ -1,80 +0,0 @@
----
-description: Show the most recent error 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 error" 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.
-
-Parse `$ARGUMENTS` as one optional integer — the count of preceding events to include. Default 10. Cap at 100.
-
-## Preflight
-
-Same as `/kit:beacon-scan` — find the latest NDJSON; if none, stop:
-
-```bash
-LATEST=$(ls -t .launchsecure/beacon-*.ndjson 2>/dev/null | head -1)
-test -n "$LATEST" || { echo "No beacon sessions found. Start one with: npx launch-beacon monitor"; exit 0; }
-```
-
-## Locate the most recent error
-
-Errors are events with `"kind":"error"` or `"kind":"unhandledrejection"`. Find the line number of the LAST such line in the file:
-
-```bash
-ERR_LINE=$(grep -nE '"kind":"(error|unhandledrejection)"' "$LATEST" | tail -1 | cut -d: -f1)
-test -n "$ERR_LINE" || { echo "No errors in the current session. Use /kit:beacon-scan to browse all events."; exit 0; }
-```
-
-## Pull the window
-
-`N` is the user-supplied count (default 10). Read the file lines from `max(1, ERR_LINE-N)` through `ERR_LINE`:
-
-```bash
-N="${1:-10}"
-START=$(( ERR_LINE - N ))
-[ "$START" -lt 1 ] && START=1
-sed -n "${START},${ERR_LINE}p" "$LATEST"
-```
-
-That's your input. The error itself is the last line; everything before is context.
-
-## Output
-
-Render a **timeline** with the error visually separated at the bottom:
-
-```
-session: .launchsecure/beacon-<token>.ndjson
-window:  10 events before error at line 247
-
-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)
-...
-
-╴╴╴╴ ERROR ╴╴╴╴
-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 error block at the end gets the message + (truncated) stack frames if present.
-- Separator above the error 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"
-
-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
-
-- **Read-only.**
-- **Most recent error only.** If the user wants an earlier one, they can clear the session (`/kit:beacon-clear`) and reproduce, or grep manually.
-- **Plain text.** Same monospace conventions as `/kit:beacon-scan`.

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

@@ -1,62 +0,0 @@
----
-description: Scan recent events from the active launch-beacon monitor session. 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. Reads `.launchsecure/beacon-*.ndjson` — the file written by `launch-beacon monitor`. 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 up to two tokens (space-separated):
-- A **kind filter**: one of `error`, `unhandledrejection`, `fetch`, `xhr`, `click`, `mousedown`, `route`, `dialog`, `probe`. Anything else is treated as a limit.
-- A **limit**: integer. Default 50.
-
-Examples:
-- `/kit:beacon-scan` → last 50 events of any kind
-- `/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
-
-## Preflight
-
-Find the most recent NDJSON file via Bash. If none exist, say so plainly and stop — there's nothing to scan.
-
-```bash
-LATEST=$(ls -t .launchsecure/beacon-*.ndjson 2>/dev/null | head -1)
-test -n "$LATEST" || { echo "No beacon sessions found in .launchsecure/. Start one with: npx launch-beacon monitor"; exit 0; }
-echo "session: $LATEST"
-```
-
-## Scan
-
-If no kind filter, `tail -n <limit> "$LATEST"`.
-
-If a kind filter is set, `grep '"kind":"<kind>"' "$LATEST" | tail -n <limit>`. The events are NDJSON, one per line — `grep` over the literal `"kind":"X"` substring is safe because the `kind` field is always the first or near-first key serialised by the beacon client.
-
-Capture the raw JSON lines as the input to your analysis.
-
-## Output
-
-Group events visually by **time** (most recent last — chronological order matches the user's 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]`)
-- **probe** → `<label>: <truncated JSON>`
-
-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
-
-- **Read-only.** Never delete, modify, or write to the NDJSON file. Wiping is `/kit:beacon-clear`.
-- **Always use the latest session by default.** If the user wants a specific session, they'll pass it as a third token — accept any of `<token>`, `<filename>`, or absolute path, and resolve to a valid `.launchsecure/beacon-*.ndjson` path before scanning. Reject with a clear error if it doesn't exist.
-- **Plain text output.** Monospace alignment beats markdown tables here. The user is reading this fast during a debug loop.
-- **Don't speculate on root cause.** Surface anomalies; let the user direct the next query (often: `/kit:beacon-pulse` for context around the latest error).