@skill-map/cli 0.68.0 → 0.68.1

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

@@ -44,7 +44,7 @@ prefix when a part spans several files: `settings-*` →
 > For the tester this is a single guided session, never a course
 > catalogue. Refer to a chapter by its tester-facing `section.chapter`
 > number plus its friendly title (`_core.md` §Numbering); never expose
-> the internal `order` index ("Part 4", off by one from the menu), a
+> the internal `order` index ("Part 3", off by one from the menu), a
 > raw "chapter id", or tour jargon ("the settings tour").
 
 ## Pre-flight (run once, silent on success)
@@ -214,9 +214,10 @@ for the data layout and the verb surface.
 
 - **Fixture sets** (laid by `fixtures.js lay <set>` / `seed <snap>`):
   `universal` (the two files above), `prologue` (the Part 0 demo),
-  `portfolio` (Part 1 boot + harness members), `harness` (the Part 2
-  additions), `master` (Part 4), `cli-external` (Part 5
-  reference-paths). The script resolves the `__PROVIDER__` token,
+  `portfolio` (Part 1 boot + harness members), `harness` (the connect
+  chapters, now folded into Part 1), `master` (Part 3 Extend),
+  `cli-external` (Part 4 reference-paths). The script resolves the
+  `__PROVIDER__` token,
   skips kinds the provider does not claim, and reports `nodeCount` +
   `skipped` for you to narrate.
 - **Footprints** (the on-disk reach of each fixture, including files a
@@ -277,7 +278,7 @@ the `__PROVIDER__` token and skip kinds the provider does not claim.
   parts use `preflight: seed`; `portfolio-init` is Part 1's flavour,
   handling the Part 0 to Part 1 transition.)
 
-- **`backstage-init`** (Part 4 `extend`): teaches plugins on its own
+- **`backstage-init`** (Part 3 `extend`): teaches plugins on its own
   **master fixture**. On entry, silently:
   1. Clear whatever prior fixture is present (each a no-op when absent),
      then drop the DB: `fixtures.js clear prologue --provider <provider>`,
@@ -285,10 +286,10 @@ the `__PROVIDER__` token and skip kinds the provider does not claim.
   2. `sm init --no-scan` (the pre-flight `.skillmapignore` stays).
   3. `fixtures.js lay master --provider <provider> --lang <lang>`.
 
-  On a Part 4 re-entry where the master fixture is already in place the
+  On a Part 3 re-entry where the master fixture is already in place the
   clears + lay are idempotent; just `sm scan`.
 
-- **`seed: prologue-built`** (Part 5 `cli`): reads the Part 0 demo
+- **`seed: prologue-built`** (Part 4 `cli`): reads the Part 0 demo
   fixture, NOT the portfolio. On entry:
   1. If the portfolio is present, clear it + drop the DB:
      `fixtures.js clear portfolio --provider <provider>`, `rm -rf .skill-map`.
@@ -301,15 +302,13 @@ the `__PROVIDER__` token and skip kinds the provider does not claim.
   3. `sm init` (single `.claude/` marker, no lens prompt), then `sm scan`.
      If `.skill-map/` already exists, skip the init and just `sm scan`.
 
-- **`seed`** (campaign parts `connect-harness`, `daily-loop`): builds
-  on the accumulating portfolio, but the tester may have jumped here.
-  Run `state.js status`; if every predecessor up the `prereq` chain is
-  `done`, the harness is already on disk, just `sm scan`. Otherwise
-  **fast-forward, silently**:
+- **`seed`** (campaign part `daily-loop`): builds on the accumulating
+  portfolio, but the tester may have jumped here. Run `state.js status`;
+  if every predecessor up the `prereq` chain is `done`, the harness is
+  already on disk, just `sm scan`. Otherwise **fast-forward, silently**:
   1. If the prologue ran first here, `fixtures.js clear prologue --provider <provider>`.
-  2. Seed: `fixtures.js seed <harness-built|harness-connected> --provider <provider> --lang <lang>`
-     (`harness-built` for `connect-harness`, `harness-connected` for
-     `daily-loop`).
+  2. Seed: `fixtures.js seed harness-connected --provider <provider> --lang <lang>`
+     (the wired harness that `daily-loop` builds on).
   3. Provision the lens: the seeded portfolio carries the scaffold
      marker (`.claude/` on the rich track, `.agents/` on the basic
      track), so a plain `sm init` resolves the matching lens with no

package/dist/cli/tutorial/sm-tutorial/fixtures-data/manifest.json

@@ -82,9 +82,6 @@
       "edits": ["todo-connectors"],
       "drop": ["notes/private-credentials.md"]
     },
-    "harness-built": {
-      "lay": ["portfolio"]
-    },
     "harness-connected": {
       "lay": ["portfolio", "harness"],
       "edits": ["agents-hub", "content-editor-style"]

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

@@ -20,7 +20,7 @@ Two numbering systems coexist; keep them apart:
 
 - **Internal (authoring only)**: the `order` field in `_manifest.yml`
   and the `# Part N` file headers, 0-based (Part 0 the prologue …
-  Part 5 the CLI deep-dive; `mcp` at Part 6 is parked / hidden). Use it
+  Part 4 the CLI deep-dive; `mcp` at Part 5 is parked / hidden). Use it
   in `**Context**:` blocks and author
   notes; NEVER say it to the tester, it is off by one from what they
   see.

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

@@ -136,6 +136,26 @@
           "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": "confidence",
+          "title": "Connector confidence (opacity = certainty)",
+          "est_min": 2
         }
       ]
     },
@@ -169,53 +189,7 @@
           "id": "real-kinds",
           "title": "The kinds in context",
           "est_min": 2
-        }
-      ]
-    },
-    {
-      "id": "connect-harness",
-      "order": 2,
-      "title": "Connect the harness",
-      "status": "active",
-      "preflight": "seed",
-      "seed": "harness-built",
-      "prereq": "project-kickoff",
-      "pace": "auto-advance",
-      "track": "rich",
-      "chapters": [
-        {
-          "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": "confidence",
-          "title": "Connector confidence (opacity = certainty)",
-          "est_min": 2
-        }
-      ]
-    },
-    {
-      "id": "basic-connect",
-      "order": 2,
-      "title": "Connect the harness",
-      "status": "active",
-      "preflight": "seed",
-      "seed": "harness-built",
-      "prereq": "basic-kickoff",
-      "pace": "auto-advance",
-      "track": "basic",
-      "chapters": [
         {
           "id": "check-links",
           "title": "The link checker",
@@ -240,12 +214,12 @@
     },
     {
       "id": "daily-loop",
-      "order": 3,
+      "order": 2,
       "title": "The daily loop (add, improve, publish)",
       "status": "active",
       "preflight": "seed",
       "seed": "harness-connected",
-      "prereq": "connect-harness",
+      "prereq": "project-kickoff",
       "pace": "auto-advance",
       "track": "rich",
       "chapters": [
@@ -281,19 +255,19 @@
         },
         {
           "id": "golive",
-          "title": "Your portfolio, live next to the graph",
+          "title": "Your website, live next to the graph",
           "est_min": 3
         }
       ]
     },
     {
       "id": "basic-daily",
-      "order": 3,
+      "order": 2,
       "title": "The daily loop (add, improve, publish)",
       "status": "active",
       "preflight": "seed",
       "seed": "harness-connected",
-      "prereq": "basic-connect",
+      "prereq": "basic-kickoff",
       "pace": "auto-advance",
       "track": "basic",
       "chapters": [
@@ -329,14 +303,14 @@
         },
         {
           "id": "golive",
-          "title": "Your portfolio, live next to the graph",
+          "title": "Your website, live next to the graph",
           "est_min": 3
         }
       ]
     },
     {
       "id": "extend",
-      "order": 4,
+      "order": 3,
       "title": "Extend skill-map for the site",
       "status": "active",
       "preflight": "backstage-init",
@@ -404,7 +378,7 @@
     },
     {
       "id": "cli",
-      "order": 5,
+      "order": 4,
       "title": "The CLI in depth",
       "status": "active",
       "preflight": "seed",
@@ -442,12 +416,12 @@
     },
     {
       "id": "mcp",
-      "order": 6,
+      "order": 5,
       "title": "MCP",
       "status": "planned",
       "preflight": "seed",
       "seed": "harness-connected",
-      "prereq": "connect-harness",
+      "prereq": "project-kickoff",
       "pace": "auto-advance",
       "track": "rich",
       "chapters": [

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

@@ -79,7 +79,7 @@ parts:
       - id: ignore          ; title: "Silence a file via .skillmapignore"  ; est_min: 2
 
   - id: extend
-    order: 4
+    order: 3
     title: "Extend skill-map for the site"
     # Spans three chapter libraries; dispatch by chapter-id prefix:
     #   settings-*  -> part-settings.md
@@ -108,7 +108,7 @@ parts:
       - id: authoring-5-doctor-author ; title: "Catch a manifest mistake with `sm plugins doctor`" ; est_min: 2
 
   - id: cli
-    order: 5
+    order: 4
     title: "The CLI in depth"
     step_file: part-cli.md
     pace: auto-advance
@@ -145,31 +145,19 @@ parts:
       - 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: connect-harness
-    order: 2
-    title: "Connect the harness"
-    step_file: part-connect-harness.md
-    pace: auto-advance
-    preflight: seed
-    seed: harness-built     # fast-forward to here if project-kickoff is not done
-    prereq: project-kickoff
-    track: rich             # /publish command + @mentions; basic track connects via references
-    status: active
-    chapters:
       - 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: confidence  ; title: "Connector confidence (opacity = certainty)" ; est_min: 2
 
   - id: daily-loop
-    order: 3
+    order: 2
     title: "The daily loop (add, improve, publish)"   # the campaign finale
     step_file: part-daily-loop.md
     pace: auto-advance
     preflight: seed
-    seed: harness-connected   # fast-forward to here if the earlier parts are not done
-    prereq: connect-harness
+    seed: harness-connected   # fast-forward to here if project-kickoff is not done
+    prereq: project-kickoff
     fixture: portfolio        # reuses the wired harness; lays the pretty site (style.css + pages) as taught steps
     track: rich               # agent-driven page add + reserved command; basic track has its own counterpart
     status: active
@@ -180,7 +168,7 @@ parts:
       - id: reserved         ; title: "A reserved name collides" ; est_min: 2
       - id: publish          ; title: "Ship it: run /publish for real" ; est_min: 4
       - id: stability        ; title: "Set a node's stability (and the `.sm` sidecar)" ; est_min: 3
-      - id: golive           ; title: "Your portfolio, live next to the graph" ; est_min: 3
+      - id: golive           ; title: "Your website, live next to the graph" ; est_min: 3
 
   # ----- the basic-track campaign (open-standard family: agent-skills / antigravity) -----
   # Mirrors the rich campaign arc with skill + markdown only, connected by
@@ -201,31 +189,19 @@ 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: basic-connect
-    order: 2
-    title: "Connect the harness"
-    step_file: part-basic-connect.md
-    pace: auto-advance
-    preflight: seed
-    seed: harness-built
-    prereq: basic-kickoff
-    track: basic
-    status: active
-    chapters:
       - 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: basic-daily
-    order: 3
+    order: 2
     title: "The daily loop (add, improve, publish)"
     step_file: part-basic-daily.md
     pace: auto-advance
     preflight: seed
     seed: harness-connected
-    prereq: basic-connect
+    prereq: basic-kickoff
     fixture: portfolio
     track: basic
     status: active
@@ -236,17 +212,17 @@ parts:
       - 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: stability   ; title: "Set a node's stability (and the `.sm` sidecar)" ; est_min: 3
-      - id: golive      ; title: "Your portfolio, live next to the graph" ; est_min: 3
+      - id: golive      ; title: "Your website, live next to the graph" ; est_min: 3
 
   # ----- parked: MCP returns later as its own iteration (body kept in part-mcp.md) -----
   - id: mcp
-    order: 6
+    order: 5
     title: "MCP"
     step_file: part-mcp.md
     pace: auto-advance
     preflight: seed
     seed: harness-connected
-    prereq: connect-harness
+    prereq: project-kickoff
     track: rich               # MCP tool declaration sits on an agent/command body
     status: planned           # temporarily disabled, hidden from the menu. Body exists; re-enable when MCP returns.
     chapters:

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

@@ -38,10 +38,10 @@ fixtures-data/
 |---|---|---|
 | `universal` | `.skillmapignore`, `findings.md` | pre-flight |
 | `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-*` seeds |
-| `harness` | `check-links` skill, `publish` command | Part 2 chapters, `harness-connected` seed |
-| `master` | `master-agent`, `master-skill`, `notes/ideas` | Part 4 `backstage-init` |
-| `cli-external` | `link-validation/hijoA` + `hijoB` | Part 5 `reference-paths` |
+| `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` |
 
 ## Edits (append fragments)
 
@@ -62,9 +62,8 @@ entered out of order.
 
 | Seed | Lays | Edits | Drops |
 |---|---|---|---|
-| `prologue-built` (Part 5) | `prologue` | `todo-connectors` | `notes/private-credentials.md` |
-| `harness-built` (Part 2) | `portfolio` | , | , |
-| `harness-connected` (Part 3) | `portfolio` + `harness` | `agents-hub`, `content-editor-style` | , |
+| `prologue-built` (Part 4) | `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 4 (c): Extend skill-map - build plugins (step library, `authoring-*` ids)
+# Part 3 (c): Extend skill-map - build plugins (step library, `authoring-*` ids)
 
-Step bodies for the plugin-authoring chapters of Part 4.
+Step bodies for the plugin-authoring chapters of Part 3.
 The SKILL.md orchestrator dispatches each `authoring-*` chapter id
 here; `settings-*` ids it dispatches to `part-settings.md`.
 

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

@@ -1,4 +1,4 @@
-# Part 3 (basic track): The daily loop (step library, `daily-loop`)
+# Part 2 (basic track): The daily loop (step library, `daily-loop`)
 
 The campaign's payoff and finale, basic track. The tester operates the harness
 they built the way they would on any normal day, **for real**. Three acts:
@@ -35,13 +35,14 @@ has NO `sm scan` / `sm check` steps: the watcher re-scans on every save.
 ## Chapter `setup` - Make it yours and bring it up (~5 min)
 
 **Context**: the harness is wired. Now put it to work on a real day. First make
-the site yours and give it a look you would share, then serve it. The HTML and
+the site yours, about whatever you like, then serve it. The HTML and
 CSS are Layer 2 (the harness's output); skill-map maps the harness (Layer 1, the
 `.md` files), so the site landing on disk does NOT move the graph.
 
 **Preparation**:
-1. Ask the tester, in one short exchange: what the site should be called and one
-   line about what it is for. If they do not care, offer defaults ("My Portfolio"
+1. Ask the tester the two questions straight, with no "before we build, let's
+   make it yours" lead-in: what the site should be called and one line about what
+   it is for. If they do not care, offer defaults ("My Portfolio"
    / "Small, sturdy things on the web"). Persist both with
    `node .claude/skills/sm-tutorial/scripts/state.js set-identity --name "<name>" --tagline "<tagline>"`.
 2. Backstage, `Write` `public/style.css`, `public/index.html`, and
@@ -69,10 +70,6 @@ node server.js
 > Open `http://localhost:3000`: there is your site, named after you. Click
 > **About** and back to **Home**.
 >
-> Now glance at the Map: it did not move. What you watched grow is your harness
-> (Layer 1, the `.md` files and their references). The pages and stylesheet are
-> Layer 2, what the harness produces. Two layers, one project.
->
 > Does the site load and look clean?
 
 Wait for confirmation. If `node server.js` reports `Cannot find module
@@ -81,11 +78,6 @@ Wait for confirmation. If `node server.js` reports `Cannot find module
 
 ## Chapter `add-page` - Add a page with your skill (~4 min)
 
-**Context**: the daily move. You want a new page, so you ask your
-`content-editor` to write it, the first time it runs **for real**. It reads
-`docs/STYLE.md` and the shared stylesheet and writes a new page into `public/`.
-The graph does not move (HTML is Layer 2).
-
 Tell the tester:
 
 > Your turn to delegate, the way you would on a real day. Tell me what page to
@@ -119,13 +111,17 @@ Wait for confirmation. Mark `add-page`: done. Auto-advance to `broken-ref`.
 
 ## Chapter `broken-ref` - A rename breaks a link (~4 min)
 
-**Context**: real reorganizing breaks things, and this is where skill-map earns
-its keep. You rename a doc, and a link that pointed at the old name goes stale.
-skill-map catches it the moment the watcher re-scans.
+**Context**: the daily safety net, and where skill-map earns its keep: rename and
+move things freely, and skill-map shows you exactly what you forgot to update
+before it ships broken.
 
 **Preparation**: none (the tester drives). Everything is watched live.
 
-Tell the tester to rename the deploy runbook (their file):
+Tell the tester to free the third terminal, then rename the deploy runbook
+themselves (their file):
+
+> In your **third terminal** (the one running `node server.js`), press
+> **Ctrl+C** to stop the site server, then rename the deploy runbook there:
 
 ```bash
 mv docs/DEPLOY.md docs/DEPLOYMENT.md
@@ -141,9 +137,7 @@ mv docs/DEPLOY.md docs/DEPLOYMENT.md
 > and point the deploy-runbook link at `docs/DEPLOYMENT.md` (the new name). Save.
 >
 > Watch the **Map** again: the arrow snaps back, solid, and the red marker
-> clears, all live. That is the daily safety net: rename and move things freely,
-> and skill-map shows you exactly what you forgot to update before it ships
-> broken.
+> clears, all live.
 >
 > Did the broken marker appear and then clear?
 
@@ -152,10 +146,6 @@ Wait for confirmation. The harness MUST be clean again before Act C. Mark
 
 ## Chapter `reserved` - A reserved name collides (~2 min)
 
-**Context**: you add a quick helper skill and, without thinking, name it
-`config`, a name the agent runtime already owns for its own built-in slash verb.
-skill-map warns you before the runtime silently ignores your skill.
-
 **Preparation**: `Write` `<provider_dir>/config/SKILL.md`:
 ```markdown
 ---
@@ -179,13 +169,12 @@ The watcher picks up the new skill. Tell the tester:
 >
 > 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`; also change
-> the H1 to `# new-page`. Save.
+> the frontmatter says `name: config`, change it to `name: new-page`. Save.
 >
 > Watch the **Map** again: the warning clears and the node is now `new-page`, all
-> live. Notice what cleared it: changing the **name** (`frontmatter.name`), which
-> for a skill must match its folder, so you rename both. Now `new-page` is yours
-> and the runtime will actually run it.
+> 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.
 >
 > Did the warning clear after the rename?
 
@@ -197,12 +186,6 @@ Wait for confirmation. Mark `reserved`: done. Auto-advance to `publish`.
 
 ## Chapter `publish` - Ship it: run the publish skill for real (~4 min)
 
-**Context**: the harness is a set of instructions, and the `publish` skill ties
-them together. You run it **for real**: it runs the link checker over your pages,
-hands off to the `content-editor` if anything needs a fix, then follows the
-deploy runbook. Same Layer 1 / Layer 2 split, the pages are output, so the Map
-stays put while the pipeline runs.
-
 **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`
@@ -215,7 +198,8 @@ Tell the tester:
 > 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.
+> 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.)
 
 After running the flow, report what actually happened (keep promises conditional
 on the real result):
@@ -229,9 +213,6 @@ on the real result):
 >   regenerate the pages (done), run the link check (done), start the server
 >   (next chapter).
 >
-> And the Map did not move while the pipeline ran: the pages are Layer 2 output;
-> the harness on the canvas is Layer 1.
->
 > The link check came back clean and `publish` is wired correctly across your
 > pages. Shall we continue?
 
@@ -239,24 +220,17 @@ Wait for confirmation. Mark `publish`: done. Auto-advance to `stability`.
 
 ## Chapter `stability` - Set a node's stability (and the `.sm` sidecar) (~3 min)
 
-**Context**: real maintenance includes marking how mature each piece is. skill-map
-lets you tag a node's **stability** from the inspector. That is skill-map's own
-metadata, so it lands in a co-located **`.sm` sidecar** next to the file (the
-vendor file stays untouched), and the first `.sm` write asks for your consent.
-
 This chapter is lens-agnostic: follow the `stability` chapter in the rich
-daily-loop (`part-daily-loop.md`) verbatim, marking the `AGENTS` handbook node
-`stable` from the inspector, confirming the consent dialog, and watching the
-`stable` badge plus the `AGENTS.sm` sidecar appear. Nothing here depends on the
+daily-loop (`part-daily-loop.md`) verbatim, setting the `AGENTS` handbook node's
+stability from the inspector, confirming the consent dialog, and watching the
+stability badge plus the `AGENTS.sm` sidecar appear. Nothing here depends on the
 lens.
 
 Mark `stability`: done. Auto-advance to `golive`.
 
-## Chapter `golive` - Your portfolio, live next to the graph (~3 min)
+## Chapter `golive` - Your website, live next to the graph (~3 min)
 
-**Context**: the climax. Serve the finished multi-page site and click through it,
-ending with the running portfolio on one side and the full harness graph on the
-other. Lens-agnostic: follow the `golive` chapter in the rich daily-loop
+Lens-agnostic: follow the `golive` chapter in the rich daily-loop
 (`part-daily-loop.md`) verbatim (the serve commands and the closing congratulation
 are identical), except when you name the harness pieces on the graph, say "the
 handbook, the content-editor, the style guide, the publish skill, the link

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

@@ -155,11 +155,8 @@ Tell the tester:
 > the link finds the real file and draws a solid arrow. Same kind of
 > note, one `.md` apart: one resolves, the other does not.
 >
-> One word on solidity: skill-map draws each connector's **confidence**
-> as opacity. Both drawn arrows are fully solid (1.00) because each
-> lands on a real file; the broken one would read 0.50 (a penalty, not
-> "half sure") and is not drawn at all. The exact per-link numbers live
-> in the inspector, next chapter.
+> 💡 Tip: if the nodes are crowded, the map toolbar has a **Re-arrange
+> layout** button that tidies things up.
 >
 > Confirm when you see the two arrows plus the broken-reference marker
 > on the hub. If an arrow is missing, refresh the browser and let me
@@ -175,9 +172,6 @@ by hand in `edit-link`). If an arrow is missing, do not advance. Mark
 The canvas only draws the resolved arrows; the full per-link breakdown,
 including the broken one, lives in the Inspector. Open it on the hub.
 
-> 💡 Tip: if the nodes are crowded, the map toolbar has a **Re-arrange
-> layout** button that tidies things up.
->
 > 🆕 Open the Inspector for **Demo TODO list** (click the node). Find
 > the **Connections** section: **Outgoing** and **Incoming**.
 > Demo TODO list lists **3 links** under Outgoing (the canvas drew two
@@ -192,6 +186,10 @@ including the broken one, lives in the Inspector. Open it on the hub.
 > Open `demo-guideline` and it shows **0**: the broken link never landed
 > on it. Three outgoing links on the hub, but only two reach a node.
 >
+> 💡 Tip: skill-map draws each connector's **confidence** as opacity.
+> Both drawn arrows are solid (1.00) because each lands on a real file;
+> the broken one is flagged instead of drawn.
+>
 > Let me know when you see it.
 
 Mark `inspector`: done.
@@ -250,17 +248,19 @@ each ends with its own confirmation. Do NOT prepend an intro line to a block.
 > Tell me when the tree is open.
 
 > At the top of the sidebar there's a search box (placeholder
-> `Search…`). Type `guideline`. Watch both halves: the tree narrows to
-> the two guideline nodes and the **Map** drops every node except those
-> two. The search matches a node's name, path, or description, and
-> filters live, no Enter needed.
+> `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).
 >
-> Now clear the box. All four nodes come back, in both the tree and the
-> Map. Confirm you saw it filter and then restore.
+> Now clear the box. All four nodes come back in the tree. Confirm you
+> saw it filter and then restore.
 
-> Last one. In the tree, find the **Demo TODO list** row: at its right
-> edge there's a small **sitemap** icon (tooltip "Isolate this node and
-> its direct links on the map"). Click it.
+> Last one. In the tree, find the `notes/todo` row (the **Demo TODO
+> list** hub, the tree labels rows by file name): at its right edge
+> there's a small **sitemap** icon (tooltip "Isolate this node and its
+> direct links on the map"). Click it.
 >
 > The Map collapses to **Demo TODO list** plus only the nodes it draws
 > an arrow to (`demo-skill`, `demo-guideline2`). That's how you focus on
@@ -271,8 +271,9 @@ each ends with its own confirmation. Do NOT prepend an intro line to a block.
 > four nodes return.
 >
 > 💡 Tip: the map-icon button next to the search box controls whether
-> the search also filters the **Map** (on by default). Click it to
-> filter only the files list, leaving the map in place.
+> 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?