@skill-map/cli 0.68.1 → 0.70.0

package/dist/cli/tutorial/sm-tutorial/references/_manifest.yml

@@ -53,11 +53,11 @@ parts:
       - id: init            ; title: "Your first node (sm init, sm, the UI)" ; est_min: 2
       - id: kinds           ; title: "The other kinds appear"               ; est_min: 1
       - id: first-edit      ; title: "Your first edit (the watcher reacts)" ; est_min: 1
-      - id: connectors      ; title: "The connectors light up"             ; est_min: 2
+      - id: connectors      ; title: "The connectors light up"             ; est_min: 1
       - id: inspector       ; title: "The inspector and connections"       ; est_min: 1
-      - id: edit-link       ; title: "Edit a link, the topology changes"   ; est_min: 3
-      - id: workspace       ; title: "Navigate the workspace (files, search, isolate)" ; est_min: 2
-      - id: ignore          ; title: "Silence a file via .skillmapignore"  ; est_min: 2
+      - id: edit-link       ; title: "Edit a link, the topology changes"   ; est_min: 2
+      - id: workspace       ; title: "Navigate the workspace (files, search, isolate)" ; est_min: 1
+      - id: ignore          ; title: "Silence a file via .skillmapignore"  ; est_min: 1
 
   - id: basic-fundamentals
     order: 0
@@ -72,15 +72,15 @@ parts:
       - id: init            ; title: "Your first node (sm init, sm, the UI)" ; est_min: 2
       - id: kinds           ; title: "Skills and notes appear"             ; est_min: 1
       - id: first-edit      ; title: "Your first edit (the watcher reacts)" ; est_min: 1
-      - id: connectors      ; title: "Connect with references (markdown links)" ; est_min: 2
+      - id: connectors      ; title: "Connect with references (markdown links)" ; est_min: 1
       - id: inspector       ; title: "The inspector and connections"       ; est_min: 1
-      - id: edit-link       ; title: "Edit a link, the topology changes"   ; est_min: 3
-      - id: workspace       ; title: "Navigate the workspace (files, search, isolate)" ; est_min: 2
-      - id: ignore          ; title: "Silence a file via .skillmapignore"  ; est_min: 2
+      - id: edit-link       ; title: "Edit a link, the topology changes"   ; est_min: 2
+      - id: workspace       ; title: "Navigate the workspace (files, search, isolate)" ; est_min: 1
+      - id: ignore          ; title: "Silence a file via .skillmapignore"  ; est_min: 1
 
   - id: extend
-    order: 3
-    title: "Extend skill-map for the site"
+    order: 4
+    title: "Extend skill-map with plugins"
     # Spans three chapter libraries; dispatch by chapter-id prefix:
     #   settings-*  -> part-settings.md
     #   tour-*      -> part-plugins.md
@@ -97,10 +97,10 @@ parts:
     chapters:
       - id: settings-1-layers        ; title: "The config layers and `sm config list`" ; est_min: 3
       - id: settings-2-resolve       ; title: "Read, resolve, and set a value with `sm config`" ; est_min: 3
-      - id: settings-3-lens          ; title: "The active provider lens (`activeProvider`)" ; est_min: 4
-      - id: tour-1-intro             ; title: "How plugins work" ; est_min: 4
-      - id: tour-2-kinds             ; title: "The six extension kinds" ; est_min: 5
-      - id: tour-3-explore           ; title: "Explore one extension up close" ; est_min: 4
+      - id: settings-3-lens          ; title: "The active provider lens (`activeProvider`)" ; est_min: 3
+      - id: tour-1-intro             ; title: "How plugins work" ; est_min: 3
+      - id: tour-2-kinds             ; title: "The six extension kinds" ; est_min: 4
+      - id: tour-3-explore           ; title: "Explore one extension up close" ; est_min: 3
       - id: authoring-1-scaffold     ; title: "`sm plugins create extractor demo-highlight`" ; est_min: 2
       - id: authoring-2-anatomy      ; title: "Tour the scaffold (plugin.json + stubs + README)" ; est_min: 3
       - id: authoring-3-edit-setting ; title: "Edit a setting (string-list) and observe it in the UI" ; est_min: 3
@@ -108,8 +108,8 @@ parts:
       - id: authoring-5-doctor-author ; title: "Catch a manifest mistake with `sm plugins doctor`" ; est_min: 2
 
   - id: cli
-    order: 4
-    title: "The CLI in depth"
+    order: 3
+    title: "The CLI for you and your agent"
     step_file: part-cli.md
     pace: auto-advance
     preflight: seed            # self-seeds the Part 0 demo fixture
@@ -118,11 +118,11 @@ parts:
     track: both                # CLI verbs are lens-agnostic; prose notes lens-specific node counts
     status: active
     chapters:
-      - id: browse           ; title: "list / show / check" ; est_min: 3
-      - id: graph-export     ; title: "graph / export (query, formatters)" ; est_min: 3
-      - id: issues           ; title: "Issues and broken refs (--analyzers, --json)" ; est_min: 3
+      - id: browse           ; title: "list / show / check" ; est_min: 2
+      - id: graph-export     ; title: "graph / export (query, formatters)" ; est_min: 2
+      - id: issues           ; title: "Issues and broken refs (--analyzers, --json)" ; est_min: 2
       - id: annotations      ; title: "Annotations and the .sm consent prompt" ; est_min: 3
-      - id: reference-paths  ; title: "Validate links to folders outside the scan scope" ; est_min: 4
+      - id: reference-paths  ; title: "Validate links to folders outside the scan scope" ; est_min: 3
 
   # ----- the portfolio campaign (the spine's real project) -----
   # Each part builds on the prior one's accumulated harness. Run in
@@ -133,7 +133,7 @@ parts:
 
   - id: project-kickoff
     order: 1
-    title: "The project from zero"
+    title: "The harness from zero"
     step_file: part-project-kickoff.md
     pace: per-step
     preflight: portfolio-init   # lays the Express skeleton + AGENTS.md; clears the prologue demo fixture if present
@@ -144,10 +144,10 @@ parts:
       - id: kickoff     ; title: "Start the portfolio (sm init on the real skeleton)" ; est_min: 2
       - id: manual      ; title: "The handbook (AGENTS.md) and CLAUDE.md" ; est_min: 2
       - id: first-agent ; title: "The first harness agent (content-editor)" ; est_min: 2
-      - id: real-kinds  ; title: "The real kinds in context" ; est_min: 2
-      - id: check-links ; title: "The check-links skill" ; est_min: 2
-      - id: publish     ; title: "The /publish command invokes the skill" ; est_min: 3
-      - id: links       ; title: "Mentions (@) and references between assets" ; est_min: 3
+      - id: real-kinds  ; title: "The real kinds in context" ; est_min: 1
+      - id: check-links ; title: "The check-links skill" ; est_min: 1
+      - id: publish     ; title: "The /publish command invokes the skill" ; est_min: 2
+      - id: links       ; title: "Mentions (@) and references between assets" ; est_min: 2
       - id: confidence  ; title: "Connector confidence (opacity = certainty)" ; est_min: 2
 
   - id: daily-loop
@@ -162,11 +162,11 @@ parts:
     track: rich               # agent-driven page add + reserved command; basic track has its own counterpart
     status: active
     chapters:
-      - id: setup            ; title: "Make it yours and bring it up" ; est_min: 5
-      - id: add-page         ; title: "Add a page with your agent" ; est_min: 4
-      - id: broken-ref       ; title: "A rename breaks a link" ; est_min: 4
+      - id: setup            ; title: "Make it yours and bring it up" ; est_min: 4
+      - id: add-page         ; title: "Add a page with your agent" ; est_min: 3
+      - id: broken-ref       ; title: "A rename breaks a link" ; est_min: 3
       - id: reserved         ; title: "A reserved name collides" ; est_min: 2
-      - id: publish          ; title: "Ship it: run /publish for real" ; est_min: 4
+      - id: publish          ; title: "Ship it: run /publish for real" ; est_min: 3
       - id: stability        ; title: "Set a node's stability (and the `.sm` sidecar)" ; est_min: 3
       - id: golive           ; title: "Your website, live next to the graph" ; est_min: 3
 
@@ -177,7 +177,7 @@ parts:
 
   - id: basic-kickoff
     order: 1
-    title: "The project from zero"
+    title: "The harness from zero"
     step_file: part-basic-kickoff.md
     pace: per-step
     preflight: portfolio-init
@@ -189,10 +189,10 @@ parts:
       - id: manual       ; title: "The handbook (AGENTS.md) and an entry pointer" ; est_min: 2
       - id: first-skill  ; title: "The first harness skill (content-editor)" ; est_min: 2
       - id: real-kinds   ; title: "The kinds in context" ; est_min: 2
-      - id: check-links ; title: "The link checker" ; est_min: 3
-      - id: publish     ; title: "The publish skill references the harness" ; est_min: 4
-      - id: links       ; title: "The handbook becomes the hub (references)" ; est_min: 4
-      - id: confidence  ; title: "Connector confidence (opacity = certainty)" ; est_min: 3
+      - id: check-links ; title: "The link checker" ; est_min: 2
+      - id: publish     ; title: "The publish skill references the harness" ; est_min: 3
+      - id: links       ; title: "The handbook becomes the hub (references)" ; est_min: 3
+      - id: confidence  ; title: "Connector confidence (opacity = certainty)" ; est_min: 2
 
   - id: basic-daily
     order: 2
@@ -206,11 +206,11 @@ parts:
     track: basic
     status: active
     chapters:
-      - id: setup       ; title: "Make it yours and bring it up" ; est_min: 5
-      - id: add-page    ; title: "Add a page with your skill" ; est_min: 4
-      - id: broken-ref  ; title: "A rename breaks a link" ; est_min: 4
+      - id: setup       ; title: "Make it yours and bring it up" ; est_min: 4
+      - id: add-page    ; title: "Add a page with your skill" ; est_min: 3
+      - id: broken-ref  ; title: "A rename breaks a link" ; est_min: 3
       - id: reserved    ; title: "A reserved name collides" ; est_min: 2
-      - id: publish     ; title: "Ship it: run the publish skill for real" ; est_min: 4
+      - id: publish     ; title: "Ship it: run the publish skill for real" ; est_min: 3
       - id: stability   ; title: "Set a node's stability (and the `.sm` sidecar)" ; est_min: 3
       - id: golive      ; title: "Your website, live next to the graph" ; est_min: 3
 

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

@@ -40,8 +40,8 @@ fixtures-data/
 | `prologue` | the seven Part 0 demo nodes | Part 0 (progressive, `--only`), `prologue-built` seed |
 | `portfolio` | Express skeleton, handbook, `content-editor`, `docs/STYLE` + `DEPLOY` | Part 1 (`--only` boot, chapters lay the rest), `harness-connected` seed |
 | `harness` | `check-links` skill, `publish` command | Part 1 connect chapters, `harness-connected` seed |
-| `master` | `master-agent`, `master-skill`, `notes/ideas` | Part 3 `backstage-init` |
-| `cli-external` | `link-validation/hijoA` + `hijoB` | Part 4 `reference-paths` |
+| `master` | `master-agent`, `master-skill`, `notes/ideas` | Part 4 `backstage-init` |
+| `cli-external` | `link-validation/hijoA` + `hijoB` | Part 3 `reference-paths` |
 
 ## Edits (append fragments)
 
@@ -62,7 +62,7 @@ entered out of order.
 
 | Seed | Lays | Edits | Drops |
 |---|---|---|---|
-| `prologue-built` (Part 4) | `prologue` | `todo-connectors` | `notes/private-credentials.md` |
+| `prologue-built` (Part 3) | `prologue` | `todo-connectors` | `notes/private-credentials.md` |
 | `harness-connected` (Part 2) | `portfolio` + `harness` | `agents-hub`, `content-editor-style` | , |
 
 ## Footprints (what `clear` and `wipe` remove)

package/dist/cli/tutorial/sm-tutorial/references/part-authoring.md

@@ -1,6 +1,6 @@
-# Part 3 (c): Extend skill-map - build plugins (step library, `authoring-*` ids)
+# Part 4 (c): Extend skill-map - build plugins (step library, `authoring-*` ids)
 
-Step bodies for the plugin-authoring chapters of Part 3.
+Step bodies for the plugin-authoring chapters of Part 4.
 The SKILL.md orchestrator dispatches each `authoring-*` chapter id
 here; `settings-*` ids it dispatches to `part-settings.md`.
 
@@ -41,6 +41,7 @@ Created /<cwd>/.skill-map/plugins/demo-highlight
 Next:
   - Edit extractors/demo-highlight-extractor/index.js
   - Run sm plugins doctor to confirm it loads
+  - Run sm plugins trust demo-highlight to let its code run (project-local plugins are untrusted until you allow them)
   - sm plugins slots list: browse slots and input-types
 ```
 
@@ -48,6 +49,28 @@ Next:
 slashes, no uppercase. `demo-highlight` is fine, `demo/highlight`
 or `Demo-Highlight` are rejected.
 
+**Trust it before it can run.** A project-local plugin you just dropped
+into `.skill-map/plugins/` is discovered but its code does NOT run until
+you trust it on this machine, a security gate so cloning a repo never
+auto-executes its plugins behind your back. The plugin is yours (you just
+wrote it), so grant trust now; the next chapters need it to run. Tell the
+tester:
+
+> One more step before your plugin can run. skill-map found it but will
+> not execute its code until you **trust** it, your local consent that
+> this code may run on your machine. It is yours, so trust it:
+
+```bash
+sm plugins trust demo-highlight
+```
+
+> Two separate ideas, on purpose: **enable** says "this plugin is part of
+> the project" (shared, lives in the config), **trust** says "I let it run
+> on this machine" (local, never travels in a commit). A scaffolded plugin
+> is enabled by default, so trusting it is all it needs to run. You can
+> revoke later with `sm plugins untrust demo-highlight`, or use the
+> per-plugin Trust control in the Settings UI.
+
 Mark `authoring-1-scaffold: done`.
 
 ## Step `authoring-2-anatomy` - tour the scaffold (~3 min)
@@ -162,12 +185,6 @@ the browser, click `notes/ideas`, and find the chip in the card's
 **left footer** (it also shows in the inspector). It reads
 `🔍 kw 3`, one match per keyword.
 
-> Heads up: editing only the fixture (`notes/ideas.md`) updates
-> live through the watcher, but it recounts with the OLD keyword
-> set, so the chip would read `🔍 kw 2`. The new `XXX` keyword
-> lives in the plugin, and the plugin is read at boot, that is why
-> restarting `sm` is the step that takes the count to 3.
-
 > Three matches. The setting flowed from the extension's `settings`
 > through `ctx.settings.keywords` into the extractor, the extractor
 > counted them, the kernel persisted the contribution, and the UI

package/dist/cli/tutorial/sm-tutorial/references/part-basic-daily.md

@@ -101,6 +101,9 @@ inside the `> ` blockquote):
 > output; the harness on the canvas is Layer 1. Your nodes are not a diagram,
 > they are runnable, and you just ran one.
 >
+> If the new page is not showing, refresh the browser with F5, the site does
+> not reload on its own.
+>
 > See the new page on the site, and the Map unchanged?
 
 Wait for confirmation. Mark `add-page`: done. Auto-advance to `broken-ref`.
@@ -146,77 +149,127 @@ Wait for confirmation. The harness MUST be clean again before Act C. Mark
 
 ## Chapter `reserved` - A reserved name collides (~2 min)
 
-**Preparation**: `Write` `<provider_dir>/config/SKILL.md`:
+**Preparation**: `Write` `<provider_dir>/model/SKILL.md`:
 ```markdown
 ---
-name: config
+name: model
 description: |
   Scaffolds a new empty page in public/ from the shared template.
 ---
 
-# config
+# model
 
 Creates a blank page so you can start writing.
 ```
 
 The watcher picks up the new skill. Tell the tester:
 
-> I added a skill named `config`. Watch the **Map**: the new `config` skill node
-> appears, but flagged with a **warning** marker. Open its inspector: it reads
-> `name-reserved`, `config` shadows one of the agent runtime's own built-in verbs
-> (like `help`, `clear`, `model`), so the runtime would silently ignore your
-> skill, it never runs. The fix is a name the runtime does not own.
->
-> Rename it to `new-page`: first rename the folder `<provider_dir>/config/` to
-> `<provider_dir>/new-page/`. Then open `new-page/SKILL.md` and, at the top where
-> the frontmatter says `name: config`, change it to `name: new-page`. Save.
+> I added a skill named `model`. Watch the **Map**: the new `model` skill node
+> appears **clean, no warning**. On the open Agent Skills standard a skill is
+> activated by its `description`, not invoked by a `/` command, so a skill name
+> can never collide with a built-in command, there are NO reserved skill names.
+> Name your skills anything you like, even after a CLI built-in like `model` or
+> `help`.
 >
-> Watch the **Map** again: the warning clears and the node is now `new-page`, all
-> live. What cleared it was changing `frontmatter.name` (which for a skill must
-> match its folder, so you renamed both). Now `new-page` is yours and the runtime
-> will run it.
+> The one exception is a vendor that bolts `/`-invocation onto the standard:
+> Google's Antigravity invokes skills with `/<name>`, so under the Antigravity
+> lens a skill named after one of its built-in verbs (like `goal`) WOULD be
+> flagged `name-reserved`. The neutral open standard you are on reserves nothing.
 >
-> Did the warning clear after the rename?
+> See the `model` node land clean, with no warning?
 
 Wait for confirmation. Mark `reserved`: done. Auto-advance to `publish`.
 
+**Antigravity delta** (`tutorial.provider == antigravity`): skills ARE
+`/`-invoked here, so a built-in verb DOES collide. Name the skill `goal` (an
+Antigravity built-in) instead of `model`, narrate the `name-reserved`
+**warning** that appears, and have the tester clear it by renaming the folder +
+`frontmatter.name` to `new-page` (the warning clears live). That collision-and-
+fix beat is the Antigravity version; `agent-skills` gets the "names are free"
+lesson above.
+
 ---
 
 **Act C - Publish**
 
 ## Chapter `publish` - Ship it: run the publish skill for real (~4 min)
 
-**Preparation**: make sure the pages exist (`index`, `about`, `projects`). When
-the tester asks to publish, **execute the publish flow for real** by following
-`<provider_dir>/publish/SKILL.md`: run the `check-links` logic over every `.html`
-under `public/` (does each internal `href` resolve to a file that exists?); if
-any link is broken, hand it to the `content-editor` and re-run; then walk the
-deploy runbook. Do not role-play it.
+**Context**: the publish flow only earns its keep when something is actually
+wrong, so first you plant a real bug in the site, then watch the publish skill
+catch and fix it for real.
 
-Tell the tester:
+**Preparation**: make sure the pages exist (`index`, `about`, `projects`).
+
+This chapter has two beats: the tester breaks a link in the HTML first, then runs
+the publish skill so `check-links` catches the break. The split is required, the
+publish run cannot demonstrate the catch until the break is in place.
+
+**Beat 1, plant the bug (the tester breaks the HTML, their file).** Tell the
+tester:
+
+> Before we ship, let's break something on purpose. Open `public/index.html` in
+> your editor and find the **About** link in the top nav:
+>
+> ```html
+> <a href="/about.html">About</a>
+> ```
+>
+> Change the target to a typo that points at a page that does not exist, then
+> save:
+>
+> ```html
+> <a href="/abuot.html">About</a>
+> ```
+>
+> Now watch the **Map**. Nothing happens: no arrow moves, no red marker. Back in
+> the `broken-ref` chapter, breaking a link between your `.md` files lit up the
+> graph the instant you saved. This break is invisible to it, and that is
+> correct: skill-map maps your **harness** (the `.md` files, Layer 1), not the
+> HTML pages it produces (Layer 2, your `public/` folder, which is even in
+> `.skillmapignore`). A broken link inside your actual site never shows on the
+> graph. The one thing that catches it is your `check-links` skill, which is
+> exactly what the publish skill runs as its first step.
+>
+> Saved the typo, and the Map stayed unchanged?
+
+Wait for confirmation. The Map MUST stay unchanged; if a marker appeared they
+edited a `.md` by mistake, point them back at `public/index.html`.
+
+**Beat 2, run the publish skill for real.** Tell the tester:
+
+> Now ship it. Tell me to publish and I'll run your `publish` skill for real,
+> exactly as written. (You can read the skill anytime by clicking the `publish`
+> node on the Map, then opening its **Body** section.)
 
-> The site is ready. Tell me to publish and I'll run your `publish` skill for
-> real: I follow its steps, run the link check across your pages, fix anything
-> through the `content-editor`, and walk the deploy runbook, exactly what the
-> skill says to do. (You can read the skill's content anytime by clicking the
-> `publish` node on the Map, then opening its **Body** section.)
+When the tester asks to publish, **execute the publish flow for real** by
+following `<provider_dir>/publish/SKILL.md`: run the `check-links` logic over
+every `.html` under `public/` (does each internal `href` resolve to a file that
+exists?), which now finds the planted typo; per step 2, hand it to the
+`content-editor` to fix (point the link back at `/about.html`), re-run the check
+until it is clean, then walk the deploy runbook. Do not role-play it; `Read`
+`public/index.html` before and after the fix so the report is honest.
 
-After running the flow, report what actually happened (keep promises conditional
-on the real result):
+After running the flow, report what actually happened:
 
 > Here is what just ran, for real:
 >
 > - **check-links** walked every page under `public/` and followed each internal
->   link. Result: 0 broken links. (Had it found one, the next step would hand it
->   to `content-editor` to fix, then re-check.)
+>   link. It caught **1 broken link**: `/abuot.html` on `index.html`, the typo
+>   you planted. The graph never flagged it, but the skill did, because the skill
+>   reads your real pages.
+> - **step 2 kicked in**: I handed it to your `content-editor` to fix. It pointed
+>   the link back at `/about.html`, and a re-run of **check-links** came back
+>   clean: 0 broken links.
 > - the **deploy runbook** (`docs/DEPLOYMENT.md`) lists the ship steps:
->   regenerate the pages (done), run the link check (done), start the server
->   (next chapter).
+>   regenerate the pages (done), run the link check (done, now clean), start the
+>   server (next chapter).
 >
-> The link check came back clean and `publish` is wired correctly across your
-> pages. Shall we continue?
+> That is the whole point of the harness: you broke the site, the graph stayed
+> quiet because the HTML is its output and not its map, and your own publish
+> skill caught the break and fixed it before it shipped. Shall we continue?
 
-Wait for confirmation. Mark `publish`: done. Auto-advance to `stability`.
+Wait for confirmation. The site MUST be clean again (the typo fixed) before
+`golive`. Mark `publish`: done. Auto-advance to `stability`.
 
 ## Chapter `stability` - Set a node's stability (and the `.sm` sidecar) (~3 min)
 

package/dist/cli/tutorial/sm-tutorial/references/part-basic-fundamentals.md

@@ -251,8 +251,12 @@ each ends with its own confirmation. Do NOT prepend an intro line to a block.
 > `Search…`). Type `guideline`. Watch the tree narrow to the two
 > guideline nodes. The search matches a node's name, path, or
 > description, and filters live, no Enter needed. The **Map** stays
-> put: by default the search filters only the files list, not the map
-> (the tip below changes that).
+> put: by default the search filters only the files list, not the map.
+>
+> 💡 Tip: the map-icon button next to the search box controls whether
+> the search also filters the **Map** (off by default, which is why the
+> map stayed put while only the tree narrowed). Click it on if you want
+> a search to filter the map too.
 >
 > Now clear the box. All four nodes come back in the tree. Confirm you
 > saw it filter and then restore.
@@ -270,11 +274,6 @@ each ends with its own confirmation. Do NOT prepend an intro line to a block.
 > Map: there's a **Show all** button (an eye icon). Click it and all
 > four nodes return.
 >
-> 💡 Tip: the map-icon button next to the search box controls whether
-> the search also filters the **Map** (off by default, which is why the
-> map stayed put while only the tree narrowed). Click it on if you want
-> a search to filter the map too.
->
 > Did the map isolate and then restore?
 
 Leave the server running, the next chapter is the last that uses it. Mark
@@ -315,7 +314,7 @@ host-dependent rendering rule. Per Inviolable rule #2, the agent does NOT touch
 ├── .agents/skills/
 │   ├── demo-skill/SKILL.md
 │   └── sm-tutorial/SKILL.md   ← the tutorial you loaded
-├── .skill-map/              ← project DB + settings (managed)
+├── .skill-map/              ← project DB + settings
 ├── .skillmapignore          ← the file we're about to edit
 └── notes/
     ├── todo.md

package/dist/cli/tutorial/sm-tutorial/references/part-basic-kickoff.md

@@ -1,4 +1,4 @@
-# Part 1 (basic track): The project from zero (step library, `kickoff-*` ids)
+# Part 1 (basic track): The harness from zero (step library, `kickoff-*` ids)
 
 The campaign turns real here for the **basic track** (the open-standard family:
 `agent-skills`, `antigravity`). After the abstract prologue, the tester starts an

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

@@ -1,4 +1,4 @@
-# Part 4: The CLI in depth - step library
+# Part 3: The CLI for you and your agent - step library
 
 The deep-dive into the rest of the CLI: browsing verbs, ASCII graph + export, broken-ref issues, the `.sm` annotation consent prompt, and validating links to folders outside the scan scope. `pace: auto-advance` (walk straight into the next chapter's Announcement once one is marked done) and `preflight: seed` with the `prologue-built` snapshot: it self-seeds its own copy of the Part 0 demo fixture, so it works even if the campaign already replaced that fixture with the portfolio (see SKILL.md §Entering a part, the `cli` case). Shared conventions (tone, provider detection / substitution, the `> ` rendering rule, the per-step cycle) live in `_core.md`; do not restate them here.