docs: add no-video demo proof path

Author: ithiria894

.github/workflows/intentprobe-action-smoke.yml

@@ -0,0 +1,48 @@
+name: IntentProbe action smoke
+
+on:
+  workflow_dispatch:
+  push:
+    branches: ["main"]
+    paths:
+      - "action.yml"
+      - ".github/workflows/intentprobe-action-smoke.yml"
+      - "docs/GITHUB_ACTION.md"
+      - "docs/DEMO_SCRIPT.md"
+      - "docs/V0_2_DEMO_PACK.md"
+  pull_request:
+    paths:
+      - "action.yml"
+      - ".github/workflows/intentprobe-action-smoke.yml"
+      - "docs/GITHUB_ACTION.md"
+      - "docs/DEMO_SCRIPT.md"
+      - "docs/V0_2_DEMO_PACK.md"
+
+jobs:
+  action-smoke:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Safe fixture passes
+        uses: ./
+        with:
+          paths: |
+            research/fixtures/scan_path/safe-weather-package
+          fail-on: block
+
+      - name: Poisoned fixture blocks
+        id: poisoned
+        uses: ./
+        continue-on-error: true
+        with:
+          paths: |
+            research/fixtures/scan_path/poisoned-skill
+          fail-on: block
+          local-files-only: "true"
+
+      - name: Assert poisoned fixture was blocked
+        if: steps.poisoned.outcome != 'failure'
+        run: |
+          echo "Expected poisoned fixture to fail with a block verdict."
+          exit 1

README.md

@@ -82,6 +82,9 @@ jobs:
 See [docs/GITHUB_ACTION.md](docs/GITHUB_ACTION.md) for target paths, inputs,
 and exit behavior.
 
+Want the quickest proof without a video? Run the
+[demo script](docs/DEMO_SCRIPT.md).
+
 ---
 
 ## How it works

ROADMAP.md

@@ -24,7 +24,7 @@ Backed by research: a 60-rule regex scanner catches **0 / 485** on the MCPTox be
 - [x] **10. Public launch hygiene.** Honest README with benchmark table, local privacy note, sample reporting guide, GitHub issue templates, SECURITY policy, package build gate, and Reddit launch draft.
 - [x] **11. CI gate preview.** Root `action.yml` lets a repo run IntentProbe from GitHub Actions with `uses: mcpware/IntentProbe@main`; docs live in `docs/GITHUB_ACTION.md`.
 - [ ] **12. First public feedback loop.** Post publicly, ask users to scan real MCP servers / skills / packages, triage missed detections and false positives into the next data curriculum.
-- [ ] **13. v0.2 demo pack.** Follow `docs/V0_2_DEMO_PACK.md`: demo repo, short scan video, runtime receipt demo, action verification, and buyer-grade evidence packet.
+- [ ] **13. v0.2 demo pack.** Follow `docs/V0_2_DEMO_PACK.md`: action smoke, no-video demo script, demo repo, runtime receipt demo, and buyer-grade evidence packet.
 
 ## Key technical facts (do not relearn these)
 
@@ -42,6 +42,7 @@ Backed by research: a 60-rule regex scanner catches **0 / 485** on the MCPTox be
 - Scanner runtime: `intentprobe/scanner/core.py`, `intentprobe/scanner/cli.py`, and `intentprobe/scanner/hook.py`.
 - Filesystem target extraction: `intentprobe/scanner/targets.py`.
 - GitHub Action metadata: `action.yml`.
+- No-video demo script: `docs/DEMO_SCRIPT.md`.
 - v0.2 demo pack living plan: `docs/V0_2_DEMO_PACK.md`.
 - Default shipped probe artifact: `intentprobe/scanner/artifacts/qwen-pooled-curated-core-l13-15-v2/`.
 - Research compatibility wrappers: `research/activation_scanner_core.py`, `research/activation_scanner_cli.py`, and `research/activation_scanner_hook.py`.

docs/DEMO_SCRIPT.md

@@ -0,0 +1,87 @@
+# Demo Script
+
+This is the no-video demo. It gives people the same proof a terminal video
+would show, but it is easier to reproduce and harder to dismiss as editing.
+
+## Local CLI demo
+
+```bash
+python3 -m pip install intentprobe
+git clone https://github.com/mcpware/IntentProbe.git
+cd IntentProbe
+```
+
+Scan the safe package fixture:
+
+```bash
+intentprobe scan-path research/fixtures/scan_path/safe-weather-package \
+  --format summary \
+  --fail-on block
+```
+
+Expected result: both candidate files are `allow`.
+
+Scan the poisoned skill fixture:
+
+```bash
+intentprobe scan-path research/fixtures/scan_path/poisoned-skill \
+  --format summary \
+  --fail-on block
+```
+
+Expected result: `SKILL.md` is `block`, and the command exits with code `2`.
+The evidence should mention both the activation score and static findings for
+private keys plus exfiltration.
+
+## GitHub Action demo
+
+Use this workflow in a repo that contains MCP configs, skills, or tool
+manifests:
+
+```yaml
+name: IntentProbe scan
+
+on:
+  pull_request:
+  workflow_dispatch:
+
+jobs:
+  scan-ai-tools:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: mcpware/IntentProbe@main
+        with:
+          paths: |
+            .
+          fail-on: block
+```
+
+For a narrower scan:
+
+```yaml
+          paths: |
+            .mcp.json
+            mcp.json
+            mcp/**/*.json
+            skills/**
+            packages/**/package.json
+```
+
+## What this proves
+
+- The scanner can be installed by a stranger.
+- Safe MCP-style package docs pass.
+- A poisoned skill that reads private keys and uploads them gets blocked.
+- The same scanner can run as a GitHub Action gate before a pull request
+  merges.
+- Scan targets and results stay inside the local machine or GitHub runner.
+
+## What this does not prove
+
+- It does not prove every poisoned tool will be caught.
+- It does not replace sandboxing, permissions, code review, or runtime controls.
+- It does not prove enterprise readiness without more deployment calibration.
+
+The point of v0.2 is product proof: CLI, CI gate, runtime hook, reproducible
+benchmarks, and a clean feedback loop for missed detections.

docs/V0_2_DEMO_PACK.md

@@ -33,24 +33,25 @@ Done:
 - Public README, FAQ, evidence packet, operator decision docs, and competitive
   landscape.
 - GitHub Action metadata and workflow docs added for CI gating.
+- No-video demo script added for copy-paste CLI and Action proof.
 
 Not done yet:
 
 - No broad external user feedback loop yet.
 - No public demo repo showing a poisoned MCP pull request being blocked.
-- No short video that a non-research person can understand in 60 seconds.
 - No GitHub Action Marketplace listing yet.
 - No calibrated enterprise policy pack for allow/warn/redact/block/review.
 - No public download or usage dashboard.
+- No short video yet. This is deliberately optional, not a v0.2 blocker.
 
 ## v0.2 milestones
 
 | Milestone | Status | Evidence target |
 |---|---|---|
 | M0. One-command install | Done | PyPI package installs and scans locally. |
 | M1. CI gate | In progress | `action.yml`, docs, and one green action run. |
-| M2. Demo repo | Next | A tiny MCP repo with one safe PR and one poisoned PR. |
-| M3. 60-second demo | Next | GIF/video: install, scan, block, JSON evidence. |
+| M2. No-video demo | In progress | `docs/DEMO_SCRIPT.md` plus action smoke workflow. |
+| M3. Demo repo | Next | A tiny MCP repo with one safe PR and one poisoned PR. |
 | M4. Runtime receipt demo | Next | `serve-jsonl` demo showing allow/warn/block receipts. |
 | M5. Public challenge loop | Open | Issues convert misses and false positives into labeled samples. |
 | M6. v0.2 release page | Open | Release notes with action usage, demo links, and benchmark links. |
@@ -59,21 +60,22 @@ Not done yet:
 ## Immediate build sequence
 
 1. Finish the GitHub Action and README/docs entrypoint.
-2. Push and verify the action metadata is visible from GitHub.
-3. Create a tiny demo repository or fixture workflow:
+2. Add and run an action smoke workflow:
+   safe fixture passes, poisoned fixture blocks.
+3. Push and verify the action metadata is visible from GitHub.
+4. Create a tiny demo repository or fixture workflow:
    `safe-weather-mcp` passes, `credential-health-check` blocks.
-4. Record the exact command/output as a short terminal demo.
-5. Add a `docs/DEMO_SCRIPT.md` that anyone can follow without knowing
-   activation probing.
+5. Record exact command/output in a text demo script anyone can follow without
+   knowing activation probing.
 6. Cut a v0.2 release once the action, demo script, and smoke evidence are all
    in one place.
 
 ## Next 72 hours
 
 - Make the CI install path copy-pasteable.
 - Add a "scan this repo in GitHub Actions" section to README.
-- Produce a 60-second demo: clone, install, scan safe, scan poisoned, show
-  block, show JSON.
+- Produce no-video proof: clone, install, scan safe, scan poisoned, show block,
+  show JSON, and link the green action smoke.
 - Reply to technical comments with concrete product behavior, not research
   abstraction.
 - Track every external comment, star burst, install question, and failure case
@@ -128,6 +130,11 @@ integration example.
 Do not spend a week polishing wording while the product surface stands still.
 The repo needs fresh proof more than perfect prose.
 
+Video is optional. For scanners, a terminal video is weaker than a runnable
+workflow because most scanner demos look the same. Prioritize reproducible proof
+first: green CI, expected block, expected allow, clear JSON, and public issue
+loop.
+
 ## Claim boundaries
 
 Safe to say:
@@ -151,3 +158,4 @@ Do not say:
 |---|---|---|
 | 2026-06-08 | Build GitHub Action before more posting. | CI turns IntentProbe from "try this CLI" into an admission gate people can wire into repos. |
 | 2026-06-08 | Keep the public pack framed as a demo/evidence pack. | It still serves the acquisition path, but reads better to users, partners, and buyers. |
+| 2026-06-08 | Defer video and prioritize runnable proof. | Security scanner videos are low-signal; action smoke, demo script, and reproducible commands create stronger trust. |