@launchsecure/launch-kit 0.0.30 → 0.0.32

package/dist/deck-client/assets/stateDiagram-v2-QKLJ7IA2-4T4wMDXr.js

@@ -1 +0,0 @@
-import{s as t,b as r,a,S as s}from"./chunk-OYMX7WX6-C4KoTL5p.js";import{_ as i}from"./index-KsShfCV-.js";import"./chunk-55IACEB6-BZPUyZAZ.js";import"./chunk-EDXVE4YY-BWwNUK-l.js";var l={parser:a,get db(){return new s(2)},renderer:r,styles:t,init:i(e=>{e.state||(e.state={}),e.state.arrowMarkerAbsolute=e.arrowMarkerAbsolute},"init")};export{l as diagram};

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

@@ -1,134 +0,0 @@
----
-description: Render a Mermaid diagram (flowchart, sequence, ERD, state, gantt) via launch-deck. For ERDs, auto-derives tables and relations from launch-chart's db layer so the diagram matches the real schema. Files a chart-gap feedback comment to LS if the db layer is missing or empty.
----
-
-# /kit:diagram
-
-Push a Mermaid diagram to launch-deck. Five flavors:
-
-- **flowchart** — boxes-and-arrows for any process
-- **sequence** — request/response timing between actors
-- **erd** — entity-relationship diagram. Auto-pulled from chart `db` layer unless the user provides their own DSL.
-- **state** — state machine
-- **gantt** — timeline
-
-Parse `$ARGUMENTS`:
-- **kind** (required) — `flowchart` | `sequence` | `erd` | `state` | `gantt`. If absent, ask.
-- **subject** (required for non-erd) — what to diagram, e.g. "user login flow" or "OAuth handshake".
-- **--scope=<filter>** — for ERDs, limit to one module or table set (e.g. `--scope=auth` or `--scope=User,Org,Membership`). Default: all tables.
-- **--session=<id>** — deck session name. Default `diagram-<kind>-<subject-slug>`.
-- **--dsl=<raw-mermaid>** — bypass auto-generation; push the user's DSL verbatim.
-- **--feedback** — push in feedback mode and await response.
-
-Examples:
-- `/kit:diagram flowchart user login flow`
-- `/kit:diagram sequence OAuth handshake between client, gateway, idp`
-- `/kit:diagram erd --scope=work-items`
-- `/kit:diagram erd` → full project ERD
-- `/kit:diagram state work-item lifecycle: backlog → todo → in-progress → done`
-
-## Preflight
-
-1. Confirm `mcp__launch-deck__server_status` is running; start if not.
-2. For `erd`: confirm `mcp__launch-chart__chart_server_status` is up, then call `mcp__launch-chart__detect_project_stack` and check `db` is in the layers list.
-
-## Build the DSL
-
-### flowchart / sequence / state / gantt
-
-Translate the subject into Mermaid DSL based on what the user described. For sequence, infer actors from the subject (client/server/db are common defaults). Add concise labels — don't overload with prose.
-
-Example flowchart skeleton:
-
-```mermaid
-flowchart TD
-  Start([User opens app]) --> Auth{Session valid?}
-  Auth -- yes --> Home[Home]
-  Auth -- no --> Login[Login form]
-  Login -- success --> Home
-```
-
-If the user passed `--dsl=…`, skip generation — use their DSL.
-
-### erd
-
-Query the db layer to derive entities and edges:
-
-1. `mcp__launch-chart__read_graph(layer: "db", type: "table"[, module: <scope>])` — gets every table node.
-2. For each table, `mcp__launch-chart__inspect_node(node_id: <id>, fields: ["columns", "relations"])` to get fields and FK relations.
-3. Render Mermaid `erDiagram` DSL:
-
-```mermaid
-erDiagram
-  USER ||--o{ WORK_ITEM : owns
-  USER {
-    string id PK
-    string email
-    datetime createdAt
-  }
-  WORK_ITEM {
-    string id PK
-    string userId FK
-    string title
-    enum type
-  }
-```
-
-Rules:
-- Use `||--o{` for 1:N FK relations, `}o--o{` for many-to-many join tables.
-- Include PK + FK markers; include enum/scalar type for the first ~8 columns per table; truncate the rest with a `… (N more)` comment.
-- Cap at 25 tables to keep the diagram readable. If the project has more than 25 in scope, ask the user to narrow with `--scope=`.
-
-**Chart-gap detection** — file a feedback comment per the protocol below before stopping if:
-- the db layer is missing from `detect_project_stack`
-- `read_graph(layer: "db")` returns 0 nodes
-- the chart shows tables but `inspect_node` returns no `columns` (parser misconfiguration)
-
-## Push to deck
-
-Call `mcp__launch-deck__deck` with:
-- `session: <session>`
-- `mode: "show"` or `"feedback"` (+ `prompt: "Does this match the schema you expected?"` for ERDs)
-- `blocks: [{ type: "mermaid", label: <kind>-<subject>, content: <mermaid-dsl> }]`
-
-If `--feedback`, call `await_feedback` and surface the response.
-
-## Output
-
-```
-diagram pushed — deck session "<session>" — http://localhost:52829/?session=<session>
-kind: <kind>
-nodes: <N>  edges: <M>
-```
-
-For ERDs add `tables: <N>  relations: <M>  scope: <scope or "all">`.
-
-## Chart-gap protocol (shared)
-
-When the chart MCP returns less data than expected (db layer missing, 0 tables, empty columns), file ONE feedback comment in the project's Comm Hub via `mcp__launch-secure__communication_write` (cloud LS, not local) before stopping:
-
-```
-resource_type: "feedback"
-title: "launch-chart gap: <one-line>"
-body: |
-  Skill: /kit:diagram
-  Tool:  read_graph(layer="db", …) / inspect_node(...)
-  Returned: <tables_count> tables, <relations_count> relations
-  Expected: db layer present per detect_project_stack
-  Project stack: <one-line summary>
-fields:
-  severity: "low"
-  source: "kit-skill"
-  skill: "diagram"
-  tool: "read_graph"
-  response_summary: { layer, tables_count, error }
-```
-
-Then fall back: render a `flowchart` placeholder explaining "DB layer not available — re-run `npx launch-chart generate_graph` then retry" instead of the ERD.
-
-## Constraints
-
-- **MCP-first for ERDs.** Never grep `prisma/schema.prisma` to build the DSL — the chart has the parsed model.
-- **Cap entities at 25.** Past that, Mermaid wraps unreadably; ask the user to narrow scope.
-- **Mermaid only.** This skill does not draw raster images — Mermaid DSL is the deliverable.
-- **One block per push.**

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

@@ -1,83 +0,0 @@
----
-description: Recover a file/dir from launch-recall's shadow-git backup. Lists snapshot history for a path and (with explicit confirmation) restores a specific snapshot into the working tree. Read-only by default; restore is one-shot and prompts before overwriting.
----
-
-# /kit:recall
-
-Surface and restore deletions/modifications captured by the launch-recall watcher (the shadow git repo at `.recall/repo.git`). Use when something was accidentally deleted, overwritten, or auto-formatted away.
-
-Parse `$ARGUMENTS` — first token is the subcommand:
-
-- **status** — quick watcher liveness + last snapshot age.
-- **doctor** — fuller health check (shadow_repo / watcher_alive / recent_snapshot).
-- **history <path>** — `[--limit=N]` — list snapshots that touched the path. Default limit 20.
-- **show <path> <sha>** — display the file's content from that snapshot (no write).
-- **restore &lt;path&gt; &lt;sha&gt;** — `[--to=<target-path>]` — restore the file. Prompts before overwriting unless the path doesn't exist on disk.
-- **diff &lt;path&gt; &lt;sha&gt;** — show a unified diff vs current working-tree (or "(file deleted from working tree)" if absent).
-
-Examples:
-- `/kit:recall status`
-- `/kit:recall history src/server/comms/build-feed.ts`
-- `/kit:recall show src/server/comms/build-feed.ts a1b2c3d`
-- `/kit:recall diff src/server/comms/build-feed.ts a1b2c3d`
-- `/kit:recall restore src/server/comms/build-feed.ts a1b2c3d`
-- `/kit:recall restore prisma/schema.prisma a1b2c3d --to=prisma/schema.recovered.prisma`
-
-## Preflight
-
-Confirm the recall MCP is wired by attempting `mcp__launch-recall__recall_status`. If neither cloud nor local is callable, stop and tell the user: `"launch-recall MCP not wired in this project. Run \`npx @launchsecure/launch-kit refresh\` (or \`npx launch-recall init\` for the shadow repo)."` Per project memory, prefer the cloud namespace; this skill works with either.
-
-## Per-subcommand behavior
-
-### status
-
-`mcp__launch-recall__recall_status` → one line: `recall <alive/dead> pid <N> last snap <X ago>`.
-
-### doctor
-
-`mcp__launch-recall__recall_doctor` → render the checks as a 3-line report:
-
-```
-recall — health
-  shadow_repo     ✓ /Users/.../.recall/repo.git
-  watcher_alive   ✓ pid 12456
-  recent_snapshot ✓ 2m ago
-```
-
-### history
-
-`mcp__launch-recall__recall_history(path: <path>, limit: <limit>)` → one row per snapshot: `sha  age  message`. Render most-recent first.
-
-If the array is empty, say so verbatim and suggest cause: `"No snapshots touch <path>. Either the path was ignored by recall's config, or the file simply never changed during this watcher's lifetime."` Then offer to print `recall.report` for context.
-
-### show
-
-The recall MCP exposes history but not a `show` tool directly. Implement by:
-1. Read `mcp__launch-recall__recall_status` → `shadowRepoPath` (or read the config — `.recall/repo.git` is the default).
-2. Use `git --git-dir=<shadow> --work-tree=<repo> show <sha>:<path>` via Bash.
-3. Print the file content (truncate at 500 lines; surface the truncation explicitly).
-
-### diff
-
-Same as `show`, but `git --git-dir=<shadow> show <sha>:<path>` piped through `diff -u - <path>` (or print "file deleted from working tree" if missing). Cap diff at 500 lines.
-
-### restore
-
-This is the only write operation. Strict protocol — per project memory `feedback_no_dumb_reverts.md`, destructive ops require explicit confirmation.
-
-1. Resolve target path: `--to=<target>` if given, else the original `<path>`.
-2. If the target exists on disk:
-   - Print a side-by-side summary: `current size <N> bytes, snapshot size <M> bytes`.
-   - Show the first ~20 lines of the diff (current → snapshot).
-   - Ask: `"Overwrite <target>? (yes / show full diff / no)"` — wait for explicit `yes`.
-3. If the target does NOT exist on disk (file was deleted), restore without prompt but tell the user before writing: `"Restoring deleted file to <target> from snapshot <sha>."`
-4. Use `git --git-dir=<shadow> show <sha>:<path> > <target>` (or `git checkout <sha> -- <path>` against the shadow with `--work-tree=<repo>`).
-5. After restore, print: `"Restored. Recall just captured a new snapshot of the restore itself — your previous working-tree state is also recoverable (run \`/kit:recall history <target>\` to confirm)."`
-
-## Constraints
-
-- **Read-only by default.** Only `restore` writes; everything else reads.
-- **Restore requires confirmation** when overwriting an existing file. Never auto-overwrite even when the user passes the sha — per project memory, destructive ops need explicit `yes`.
-- **No `git reset`, no `git clean`, no `rm`.** Recall restores via `git show > file`; never run anything that could lose more than the one file requested.
-- **Don't suggest enabling recall for the user.** If recall isn't wired, point at refresh — don't auto-init.
-- **Quote both pieces of advice when the file is unchanged.** If `history` returns nothing AND the file exists on disk, say BOTH "path may be in recall's ignore list" AND "the file may simply have no churn" — don't guess which.