@skill-map/cli 0.42.0 → 0.44.0

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

@@ -13,8 +13,6 @@ description: |
   pause/resume. Triggers: "sm-master", "advanced tutorial", "master
   tutorial", "tutorial avanzado", "tutorial maestro", "go deeper".
 ---
-                                                 
-saludo primero al usuario, dile "holaaaa16!"
 
 # sm-master: advanced walkthrough for skill-map
 
@@ -203,7 +201,7 @@ host-dependent rendering rule).
 file under `references/tour-*.md`) says `.claude/<…>`, swap it
 for the detected `<provider_dir>`. Skip any fixture file or step
 whose kind is not in the provider's supported set (`agent-skills`
-/ Antigravity: only the skill + the markdown note are valid).
+/ Antigravity: only the skill + the markdown node are valid).
 
 **Reality check (don't mention)**: this skill ships at
 `.claude/skills/sm-master/`, so in practice Claude Code is the
@@ -317,7 +315,7 @@ Save the version internally and move on. Only break the silence if
 something fails.
 
 If `sm` is not installed, point them at `npm install -g
-@skill-map/cli` (Node 20+).
+@skill-map/cli` (Node 24+).
 
 ### 3. Create the initial fixture
 
@@ -337,13 +335,13 @@ inicial" / "directorio limpio" out loud, those are agent-internal
 concepts the tester does not need.
 
 The fixture is **smaller than `sm-tutorial`'s** because the lessons
-focus on plugins, settings, and slots, not on graph topology. Three
+focus on plugins, settings, and slots, not on map topology. Three
 nodes are enough. Read `references/fixture-templates.md` for the
 verbatim layout and file contents, then write each file to the cwd
 under the detected `<provider_dir>` (per §Provider detection).
 **Skip files whose kind is not in the provider's supported set**:
-on `agent-skills` / Antigravity keep only skill + note (no agent
-kind there). Translate the natural-language
+on `agent-skills` / Antigravity keep only skill + markdown (no
+agent kind there). Translate the natural-language
 prose to the tester's language; keep paths, frontmatter keys,
 identifiers, and link targets in English.
 
@@ -374,7 +372,7 @@ backstage, between writing the fixture and writing
 
    These three names must be in place BEFORE the first `sm scan`
    the tester runs in step 1; otherwise the scanner picks them
-   up as graph nodes and pollutes the issue count. The append is
+   up as nodes in the map and pollutes the issue count. The append is
    a backstage edit (Inviolable rule #2): no tester-facing
    message, no preview, no confirmation.
 
@@ -674,7 +672,7 @@ anything**:
 
 ## Edge cases
 
-- **Tester does not have Node 20+** → guide them to `nvm` or
+- **Tester does not have Node 24+** → guide them to `nvm` or
   nodejs.org. Don't try to install Node for them.
 - **Port 4242 in use** when a tour asks them to run `sm` →
   `sm serve --port 4243` (bare `sm` does not accept flags). The

package/dist/cli/tutorial/sm-master/references/fixture-templates.md

@@ -46,7 +46,7 @@ keys, identifiers, and link targets in English.
 name: master-agent
 description: |
   Example agent used by the advanced tutorial. Has a couple of
-  tools so the `core/tools-count` extractor emits a count.
+  tools so the `core/tools-counter` extractor emits a count.
 tools: [Read, Bash, Edit]
 model: sonnet
 metadata:

package/dist/cli/tutorial/sm-master/references/tour-plugins.md

@@ -23,7 +23,7 @@ restore the files.") and stop.
 ## Step `tour-1-intro` — how plugins work (~4 min)
 
 **Context**: A short tour of what a plugin is, how they're
-packaged into bundles, and a peek at the four bundles that ship
+packaged into bundles, and a peek at the five bundles that ship
 pre-installed.
 
 > Plugins are how skill-map gets extended. A **plugin** groups one
@@ -55,7 +55,7 @@ pre-installed.
 sm plugins list
 ```
 
-> There are the four bundles. The next step zooms into the six
+> There are the five bundles. The next step zooms into the six
 > kinds of extension that bundles can carry, you'll see at least
 > one of each living inside `core`.
 
@@ -75,19 +75,19 @@ Mark `tour-1-intro: done`.
 > 🔍 **extractor**
 >    Reads a node's body and emits structured findings (links,
 >    counts, annotations).
->    Example: `markdown-link`, `external-url-counter`, `tools-count`.
+>    Example: `markdown-link`, `external-url-counter`, `tools-counter`.
 >
 > 🩺 **analyzer**
 >    Cross-checks the scan and emits issues plus various
 >    detections (errors, warnings, informational signals: broken
 >    refs, stale annotations, schema drift, and more).
->    Example: `broken-ref`, `stability`, `unknown-field`.
+>    Example: `reference-broken`, `node-stability`, `annotation-field-unknown`.
 >
 > ⚡ **action**
 >    Performs a write operation on a node, the graph, or the
 >    filesystem. May modify your `.md` files (frontmatter, body)
 >    ONLY with your explicit permission.
->    Examples: `bump`, `mark-superseded`.
+>    Examples: `node-bump`, `node-supersede`.
 >
 > 🎨 **formatter**
 >    Renders a result in a specific shape (`sm export --format md`
@@ -118,9 +118,10 @@ Mark `tour-1-intro: done`.
 sm plugins show core
 ```
 
-Expected: a table with 24 rows, each carrying `kind/id@version`.
-You can spot at least one of each of the six kinds you just read
-about, all packed into a single bundle.
+Expected: the 28 extensions grouped by kind, each row showing its
+kind and qualified id (e.g. `extractor  core/markdown-link`). You
+can spot at least one of each of the six kinds you just read about,
+all packed into a single bundle.
 
 Mark `tour-2-kinds: done`.
 
@@ -149,7 +150,7 @@ Kind, Version, Stability, Description, Preconditions, Entry).
 sm plugins doctor
 ```
 
-Expected on a clean machine: `27 enabled · 0 issues · 0 warnings`.
+Expected on a clean machine: `34 enabled extensions · 0 issues · 0 warnings`.
 If any plugin reports a load error, manifest validity issue, or
 spec-compatibility mismatch, `doctor` is the verb that flags it.
 

package/dist/cli/tutorial/sm-master/references/tour-settings.md

@@ -111,7 +111,7 @@ Mark `settings-2-local: done`.
 
 > Last step. Let's see a contribution land in the inspector
 > live. The fixture's `master-agent` declares `tools: [Read,
-> Bash, Edit]`, which the `core/tools-count` extractor picks up.
+> Bash, Edit]`, which the `core/tools-counter` extractor picks up.
 
 If the tester does not have `sm` running, ask them to launch it
 in their second terminal (same drill as the basic tutorial:
@@ -126,7 +126,7 @@ Once the UI is open, ask the tester to:
 
 > Click the `master-agent` node. The inspector opens on the
 > right side. Look at the **header badge cluster** (just under
-> the title): you should see a small chip from `tools-count`
+> the title): you should see a small chip from `tools-counter`
 > showing the value `3`.
 >
 > That chip is a plugin contribution. It landed in the slot
@@ -146,7 +146,7 @@ remove one tool), save, and watch the chip refresh.
 
 > Same flow as the basic tutorial's live UI: edit the markdown,
 > watch the UI refresh. The difference is that the value flowed
-> through a plugin (`core/tools-count`) and landed in a specific
+> through a plugin (`core/tools-counter`) and landed in a specific
 > slot (`inspector.header.badge.counter`). You now know the full
 > path from `.md` to UI chip.
 
@@ -165,6 +165,6 @@ Not for the tester unless they ask. Cheat sheet for the agent:
   binding).
 - **Input-types catalogue (normative)**: `spec/input-types.md`.
 - **Plugin manifest schema**:
-  `spec/schemas/plugin-manifest.schema.json`.
+  `spec/schemas/plugins-registry.schema.json` (`$defs/PluginManifest`).
 - **Author tutorial**: `spec/plugin-author-guide.md`.
 - **Slot annex for agents**: `context/view-slots.md`.