loadout-ai 0.9.1 → 0.9.2

package/docs/USER_TEST_GUIDE.md

@@ -419,7 +419,7 @@ cleanup deliberately deletes Loadout's snapshots, so it is the last lifecycle te
 ## Troubleshooting and recovery
 
 - **`loadout` is not found after installation:** confirm `npm install --global
-loadout-ai@0.9.0` completed, run `hash -r`, and confirm npm's global binary
+loadout-ai@0.9.2` completed, run `hash -r`, and confirm npm's global binary
   directory is on `PATH`. For a source checkout, run `npm run build` and `npm link`.
 - **A preview asks for `--approve-risk`:** read the reported scripts, domains,
   credentials, binaries, or instruction findings. If you accept that specific plan,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "loadout-ai",
-  "version": "0.9.1",
+  "version": "0.9.2",
   "private": false,
   "license": "MIT",
   "description": "The package manager for AI coding agent extensions",

package/docs/DEMO_SCRIPT.md

@@ -1,152 +0,0 @@
-# Loadout demo and voiceover
-
-Target length: **2:35 to 2:50**. Record the real CLI, cut fetch waits and typing, and do
-not show the retired dashboard. The final YouTube upload must be public.
-
-## Before recording
-
-1. Close terminals that show tokens, private paths you do not want public, or unrelated
-   work. Increase terminal font size and use a window about 120 columns wide.
-2. Confirm the release and product health:
-
-   ```bash
-   npm install --global loadout-ai@0.9.0
-   hash -r
-   loadout --version
-   loadout health
-   ```
-
-3. Finish the remaining founder acceptance path before recording. Keep the useful
-   successful output in terminal history, but start the recording from a clean prompt.
-4. Rehearse the voiceover once. Use macOS Screenshot (`Shift-Command-5`) with your
-   microphone, OBS, or another recorder. Record at normal speed; speed the final cut
-   to 1.1x only if necessary.
-
-## Shot list and exact narration
-
-### 0:00 to 0:15: the problem
-
-**Screen:** README hero, then a terminal showing `loadout --version`.
-
-**Say:**
-
-> AI coding extensions are scattered across GitHub. You find a skill on X, an MCP
-> server on Reddit, copy it into one agent, and later have no idea where it came from
-> or how to undo it. I built Loadout: one local CLI to discover, inspect, install,
-> update, and roll back agent extensions across Codex, Claude Code, and other agents.
-
-### 0:15 to 0:50: one safe install
-
-**Screen:** Run the preview, then apply. Cut the fetch wait, not the result.
-
-```bash
-loadout setup --mode stable --agents codex,claude-code --api-access none
-loadout setup --mode stable --agents codex,claude-code --api-access none --yes
-```
-
-**Say:**
-
-> Stable selects thirty useful skill directories per agent from four pinned public
-> sources. The first run is a preview: it shows the sources, targets, credentials, and
-> safety findings without changing agent files. When I approve it, Loadout applies one
-> transaction and gives me a rollback snapshot. My ChatGPT and Claude subscriptions
-> are not treated as API keys, and normal skill setup does not need one.
-
-### 0:50 to 1:12: see what changed and undo it
-
-**Screen:**
-
-```bash
-loadout scan
-loadout status
-loadout rollback --list
-loadout rollback --snapshot <stable-snapshot-id>
-```
-
-**Say:**
-
-> Scan separates Loadout-managed skills from files I already had. Status keeps source
-> and version ownership, and rollback restores the exact pre-install snapshot while
-> preserving unrelated skills. I use the exact snapshot ID shown by the install, so
-> there is no ambiguity. Complete uninstall is available too.
-
-### 1:12 to 1:42: broad catalog, focused project
-
-**Screen:** Show the profile choices, catalog coverage, and a real project
-recommendation. These commands are read-only and do not require a prepared Maximum
-library.
-
-```bash
-loadout profiles
-loadout catalog --coverage
-loadout recommend --project . --agent codex
-```
-
-**Say:**
-
-> Loadout has three useful levels. Stable installs a bounded daily set. Power is
-> broader. Maximum keeps a large screened library disabled instead of dumping every
-> skill into every prompt. For this TypeScript CLI, the project recommender proposes
-> tools for documentation, testing, security, and MCP work without changing anything.
-
-### 1:42 to 2:05: MCP, tools, and custom skills
-
-**Screen:**
-
-```bash
-loadout mcp-recipe --credential-free
-loadout mcp-recipe playwright --agent codex
-loadout tool graphify --agents codex,claude-code
-loadout install --mode custom --package humanizer --agents codex
-```
-
-**Say:**
-
-> MCP servers and executable tools are never hidden inside a profile. Playwright is a
-> separately previewed MCP recipe; Graphify is a pinned runtime tool; and a catalog
-> skill such as Humanizer can be installed directly through Custom mode. Each path
-> discloses permissions and credentials before approval.
-
-### 2:05 to 2:28: hand work from Claude Code to Codex
-
-**Screen:**
-
-```bash
-loadout skills install loadout-handoff --yes
-loadout handoff codex "write tests for the auth module" --context "see src/auth.ts"
-loadout handoff
-```
-
-**Say:**
-
-> Loadout also gives Claude Code and Codex a tiny shared handoff log. Claude can leave
-> a bounded task with context, and Codex sees it when the next session checks its
-> inbox. It is intentionally a local file workflow—not a background service or a live
-> chat channel.
-
-### 2:28 to 2:48: close
-
-**Screen:** Return to the README hero and the handoff row in the workflow image.
-
-**Say:**
-
-> Loadout stays local and does not require an LLM API key to manage skills. One CLI
-> gives your coding agents a setup you can inspect, improve, pass work through, and
-> undo. Agent extensions, under control.
-
-## Final edit and upload
-
-- Remove loading screens, typing pauses, repeated commands, notifications, and secrets.
-- Keep terminal output readable at 1080p; do not use a synthetic dashboard or mock data.
-- Add a small title card: **Loadout: Agent extensions, under control.**
-- Export under three minutes and upload publicly to YouTube.
-- Watch the uploaded video once, confirm audio and text are legible, then paste the
-  exact public URL into the README.
-
-## Submission checklist
-
-- [ ] Public YouTube video is under three minutes and its URL opens signed out.
-- [ ] Voiceover shows preview, rollback, and Claude Code ↔ Codex handoff.
-- [ ] Repository and npm links open in a signed-out browser.
-- [ ] README installation and user-test paths match the published version.
-- [ ] No terminal frame exposes tokens, usernames, or private repository names.