@skill-map/cli 0.16.3 → 0.16.4

package/README.md

@@ -37,7 +37,7 @@ claude                       # open Claude Code in the same dir
 ejecutá @sm-tutorial.md
 ```
 
-Claude loads the SKILL.md and runs the demo (~10 min): fixture, `sm init`, live UI, five sub-steps that show the watcher in action, plus the `.skillmapignore` hide-a-file flow. An optional deep-dive (~30-40 min) covers the rest of the CLI surface (`list`, `graph`, `export`, `check`, `plugins`).
+Claude loads the SKILL.md and runs the demo (~10 min): fixture, `sm init`, live UI, five sub-steps that show the watcher in action, plus the `.skillmapignore` hide-a-file flow. An optional deep-dive (~20-30 min) covers the rest of the CLI surface (`list`, `graph`, `export`, `check`, `plugins`).
 
 The verb `sm tutorial` writes a single self-contained file; the SKILL.md ships inside this package, so no extra install needed.
 

package/dist/cli/tutorial/sm-tutorial.md

@@ -6,7 +6,7 @@ description: |
   starts with a quick demo (~10 min) that showcases the live UI — the
   tester runs `sm`, opens the browser, and watches the UI update as
   the agent edits `.md` files — and at the end offers an optional
-  deep-dive (~30-40 min) covering the rest of the CLI with flags and
+  deep-dive (~20-30 min) covering the rest of the CLI with flags and
   advanced verbs. The skill is invoked from an empty directory and
   lays the fixture and tutorial files there directly (no wrapper).
   State persists in `tutorial-state.yml` for pause/resume. Triggers:
@@ -24,7 +24,7 @@ type, and wait for the tester to run them and confirm.
 
 **Internal structure (do NOT mention this to the tester)**: the tutorial
 has a short first phase (~10 min) that demonstrates the live UI, and an
-optional second phase (~30-40 min) covering the rest of the CLI.
+optional second phase (~20-30 min) covering the rest of the CLI.
 
 > ⚠️ For the tester this is **a single continuous flow**. Never use
 > "short path", "long path", "route", "phase 1" / "phase 2", or
@@ -73,7 +73,7 @@ optional second phase (~30-40 min) covering the rest of the CLI.
   meta-narration of your own plumbing. Pre-flight checks, file
   reads, `Bash ls`, `Write` of fixtures, state-file updates — all
   silent. The tester only hears from you when (a) you need them to
-  do something, (b) a reveal landed and you want a confirm, or
+  do something, (b) a sub-step landed and you want a confirm, or
   (c) something failed and they need to know. Between those
   moments, work without commentary.
 - **Explain technical terms in parentheses the first time you
@@ -292,12 +292,26 @@ permissions issue. Suggest `node --version` and walk them through it.
 
 ### 3. Create the initial fixture (one node only)
 
+Before you lay anything down, give the tester a one-shot heads-up.
+**This is not interactive** — do NOT wait for a confirmation, do
+NOT ask permission per file, do NOT enumerate the files. The
+tester just needs to know scaffolding is starting so they're not
+surprised when files appear; details (file list, cleanup) come
+later when they're relevant. Keep it to a single short sentence:
+
+> Quick heads-up before we start: I'm about to set up the
+> tutorial scenario in this directory — that means creating a
+> handful of files. Hold on while I finish.
+
+Then proceed straight to the writes below — no pause, no "ready?"
+prompt.
+
 The tutorial builds the graph **progressively** in five sub-steps during
 Step 2 (Live UI). Right now, in pre-flight, you only create **one
 file** — a single agent — so the tester's first look at the UI
 shows exactly one node. The other four kinds (skill, command, hook,
 note) and the connectors between all five are added later, one
-reveal at a time.
+sub-step at a time.
 
 ```
 <cwd>/
@@ -309,7 +323,7 @@ reveal at a time.
 ```
 
 `.claude/agents/demo-agent.md` (no cross-fixture links yet — those
-arrive in the third reveal):
+arrive in Step 2.4):
 ```markdown
 ---
 name: demo-agent
@@ -568,7 +582,7 @@ Create these four files (with `Write`), exactly in this order:
    # demo-skill
 
    This skill walks a file and returns a report. Will be wired up
-   to the rest of the demo fixture in the next reveal.
+   to the rest of the demo fixture in the next sub-step.
 
    ## Steps
    1. Read the `target`.
@@ -596,7 +610,7 @@ Create these four files (with `Write`), exactly in this order:
    # demo-command
 
    Quick keyboard entry point for running the demo flow on a
-   target file. Connectors land in the next reveal.
+   target file. Connectors land in the next sub-step.
    ```
 
 3. `.claude/hooks/demo-hook.md` (kind: hook — **don't skip this
@@ -627,7 +641,7 @@ Create these four files (with `Write`), exactly in this order:
    description: |
      Live list of things to review in the demo. Will become the
      hub between skill / agent / command / hook in the next
-     reveal.
+     sub-step.
    tags: [notes, demo]
    metadata:
      version: "1.0.0"
@@ -851,7 +865,7 @@ Mark `2-ui-live: done`.
 >
 > If you want, **we can keep going deeper**: I'll walk you through
 > the CLI verbs and flags (`list`, `graph`, `export`, `orphans`,
-> `plugins`, `db ops`, etc.). About ~30-40 min more, pausable
+> `plugins`, `db ops`, etc.). About ~20-30 min more, pausable
 > whenever.
 >
 > 1. **Yes, let's continue**
@@ -870,7 +884,7 @@ If they say **1**:
 
 ---
 
-## DEEP-DIVE (~30-40 min) — opt-in
+## DEEP-DIVE (~20-30 min) — opt-in
 
 Strictly new steps. Does not re-expand demo steps.
 

package/dist/cli.js

@@ -7374,7 +7374,7 @@ import { Command as Command8, Option as Option8 } from "clipanion";
 // package.json
 var package_default = {
   name: "@skill-map/cli",
-  version: "0.16.3",
+  version: "0.16.4",
   description: "skill-map reference implementation \u2014 kernel + CLI + adapters.",
   license: "MIT",
   type: "module",
@@ -7425,6 +7425,10 @@ var package_default = {
     typecheck: "tsc --noEmit",
     lint: "eslint .",
     "lint:fix": "eslint . --fix",
+    pretest: "tsup",
+    "pretest:ci": "tsup",
+    "pretest:coverage": "tsup",
+    "pretest:coverage:html": "tsup",
     test: "tsc --noEmit && node --import tsx --test --test-reporter=spec 'test/**/*.test.ts' 'built-in-plugins/**/*.test.ts' 'kernel/**/*.test.ts'",
     "test:ci": "tsc --noEmit && node --import tsx --test 'test/**/*.test.ts' 'built-in-plugins/**/*.test.ts' 'kernel/**/*.test.ts'",
     "test:coverage": "tsc --noEmit && SKILL_MAP_SKIP_BENCHMARK=1 node --experimental-default-config-file --import tsx --test --experimental-test-coverage 'test/**/*.test.ts' 'built-in-plugins/**/*.test.ts' 'kernel/**/*.test.ts'",
@@ -14577,7 +14581,12 @@ import { Command as Command22, Option as Option22 } from "clipanion";
 // cli/i18n/tutorial.texts.ts
 var TUTORIAL_TEXTS = {
   // Success — written to stdout after `<cwd>/sm-tutorial.md` is created.
-  written: 'Done. sm-tutorial.md created at {{cwd}}. Open Claude Code here and tell it "run @sm-tutorial.md" to start the interactive tutorial.\n',
+  // Multi-line layout: the two trigger phrases (English / Spanish) are
+  // indented and labelled so they're the most visible part of the
+  // output. The reminder above them surfaces the SKILL's language
+  // policy: the first message the tester writes to Claude sets the
+  // tutorial language for the rest of the session.
+  written: "Done. sm-tutorial.md created at {{cwd}}\n\nOpen Claude Code here. Write to it in the language you want the tutorial in \u2014 the first message sets the language for the rest of the session:\n\n    English:  run @sm-tutorial.md\n    Espa\xF1ol:  ejecut\xE1 @sm-tutorial.md\n",
   // Refusal — `sm-tutorial.md` already exists and `--force` was not set.
   // Goes to stderr, exit code 2 (operational error per spec § Exit codes).
   alreadyExists: "sm tutorial: sm-tutorial.md already exists at {{cwd}}. Pass `--force` to overwrite.\n",