@launchsecure/launch-kit 0.0.30 → 0.0.31

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.