@skill-map/cli 0.53.1 → 0.53.3

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

@@ -5,8 +5,8 @@ starts an actual project: a tiny personal **portfolio website**,
 fully static, served by a ~15-line Express server, plus the
 `.claude/` **harness** that maintains it. skill-map maps the harness
 (the `.md` assets and how they reference each other); the site itself
-is plain HTML the harness produces (Part 5 generates it and runs the
-server). `pace: per-step`, `preflight: portfolio-init`. Shared
+is plain HTML the harness produces (Part 3 runs it, Part 6 ships it).
+`pace: per-step`, `preflight: portfolio-init`. Shared
 conventions live in `_core.md`.
 
 The orchestrator's `portfolio-init` pre-flight (backstage, silent)
@@ -125,7 +125,7 @@ Wait for confirmation. Mark `first-agent`: done.
 **Context**: the prologue showed the four kinds on abstract demo
 nodes. Now name them on the real project, and add the two markdown
 docs the harness references later (the style guide and the deploy
-runbook), so Part 3's maintenance beats have something to point at.
+runbook), so Part 4's maintenance beats have something to point at.
 
 `Write` two docs (markdown kind):
 
@@ -171,16 +171,14 @@ Tell the tester:
 > - **agent**: `content-editor` (does work on your behalf).
 > - **markdown**: `AGENTS.md`, `CLAUDE.md`, the two docs (plain notes
 >   and manuals).
-> - **skill** and **command**: coming in the next part, when we add
->   the link checker and the publish command and wire everything
->   together.
+> - **skill** and **command**: you add these (the link checker and
+>   the publish command) in a later part.
 >
-> Your handbook now has a real harness around it. Next we connect it:
-> the agent reaching the style guide, the command invoking the
-> skill, the whole graph lighting up.
+> Your handbook now has a real harness around it: a `content-editor`
+> agent plus its docs, all on the map.
 >
-> Ready to connect the harness?
+> See the agent and the docs in the map?
 
-Wait for confirmation. Mark `real-kinds`: done. This closes Part 1;
-the orchestrator returns to the ToC menu (Part 2, "Connect the
-harness", is next on the spine).
+Wait for confirmation. Mark `real-kinds`: done. Last chapter of the
+part: apply §Closing a part (the close names the part by its title and
+routes back to the menu; do NOT lead into the next part from here).

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

@@ -0,0 +1,155 @@
+# Part 3: Run the harness (your site, live) (step library, `generate` + `serve`)
+
+The first payoff: the harness you built and wired in the earlier parts
+finally does its job and you see a real site running, without waiting
+for the finale. Pace `auto-advance`, preflight `seed` (`harness-connected`,
+so a tester can jump straight here). Two chapters, in order:
+`generate` (the agent writes the HTML pages) then `serve` (the tester
+runs the site and sees it next to the graph). This is a deliberately
+simple, working pass: maintenance, MCP and the full publish pipeline
+come in the parts after it. Shared conventions live in `_core.md`.
+
+These two HTML pages are the canonical site fixture: the full
+publish finale (`live-site`) lays the same `public/index.html` and
+`public/about.html` from here before adding its own extra page, so keep
+them in sync here only.
+
+## Chapter `generate` - The agent generates the HTML in public/ (~3 min)
+
+**Context**: the `content-editor` agent exists to write the site's
+pages, so now you (playing that agent) generate the actual HTML into
+`public/`. The honest beat the tester must hear: writing HTML does NOT
+move the skill-map graph. The graph is Layer 1, the `.md` harness that
+builds the site; the HTML is Layer 2, the harness's OUTPUT, and
+skill-map does not map it (HTML is not `.md`). So the Map will sit
+still while real files land on disk, and that is correct, not a bug.
+Keep the markup plain per the style guide: no framework, no client JS,
+one H1 per page, every page links back home.
+
+**Preparation**: `Write` two static pages into `public/`. The
+pre-flight already left a placeholder `public/index.html`; this
+overwrites it with the real home page and adds an about page. Keep the
+markup plain.
+
+`public/index.html`:
+```html
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1" />
+    <title>My Portfolio</title>
+  </head>
+  <body>
+    <h1>My Portfolio</h1>
+    <p>Hi, I build small, sturdy things on the web.</p>
+    <nav>
+      <a href="/">Home</a> ·
+      <a href="/about.html">About</a>
+    </nav>
+  </body>
+</html>
+```
+
+`public/about.html`:
+```html
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1" />
+    <title>About</title>
+  </head>
+  <body>
+    <h1>About</h1>
+    <p>A short page about the person behind the portfolio.</p>
+    <nav>
+      <a href="/">Home</a>
+    </nav>
+  </body>
+</html>
+```
+
+```bash
+# Nothing for you to run yet. Look at both halves of your screen.
+```
+
+Tell the tester:
+
+> Your `content-editor` agent just did its real job: it wrote the
+> actual web pages. Two HTML files landed in your project under
+> `public/`: the home page (`public/index.html`) and an about page
+> (`public/about.html`), plain static markup that follows the style
+> guide you set up earlier.
+>
+> Now glance at the Map. It did not change, and that is exactly
+> right. Everything you watched grow on the canvas is your harness:
+> the `.md` files and how they reference each other (call that
+> Layer 1). The HTML pages are Layer 2, what the harness PRODUCES.
+> skill-map maps the harness, not the pages it outputs (HTML is not
+> `.md`), so writing real site files leaves the graph untouched. Two
+> layers, one project: the graph that builds the site, and the site
+> itself.
+>
+> Ready to see the site running?
+
+Wait for confirmation. Mark `generate`: done. Auto-advance to `serve`.
+
+## Chapter `serve` - node server.js: your portfolio, live next to the graph (~3 min)
+
+**Context**: the tester installs the single dependency (Express) and
+starts the tiny server that the pre-flight already left in
+`server.js`, then opens the site in the browser. They end with two
+things side by side: the real portfolio they can click through, and
+the skill-map graph of the harness that built it. Express runs on
+Node, which the tester has from pre-flight (Node 24+), so no new
+install beyond `npm install`. This chapter is one of the few where the
+tester runs a non-`sm` command themselves (`npm install`,
+`node server.js`); guide them, do not run it for them.
+
+**Preparation**: none. `server.js` and `package.json` already exist
+from the kickoff pre-flight; the pages exist from the `generate`
+chapter. The tester runs everything in this chapter.
+
+```bash
+npm install
+node server.js
+```
+
+Tell the tester:
+
+> You have the pages; now let's serve them. In your terminal, run
+> these two commands:
+>
+> The first, `npm install`, downloads the one small library the
+> server needs (Express, a tiny web server). It runs on Node, which
+> you already installed at the very start, so there is nothing new to
+> set up.
+>
+> The second, `node server.js`, starts the server. It prints a line
+> telling you it is listening, something like `Listening on
+> http://localhost:3000`.
+>
+> Open `http://localhost:3000` in your browser. There it is: your
+> portfolio, live. Click the **About** link, then the **Home** link
+> to come back. Those are the very pages your harness produced.
+>
+> Take a second to look at both halves: on one side the running site
+> you can click through, on the other the skill-map graph of the
+> harness that built it. You built the harness, wired it, and now you
+> have run it once end to end.
+>
+> Does the site load, and can you click between Home and About?
+
+Wait for confirmation. The tester runs the commands; do not run them
+for them. If `npm install` fails, check they are in the project root
+(the cwd they have used all along) and that Node is on PATH (`node
+--version` should print 24 or higher). If the port is busy, they can
+stop the server with Ctrl+C and the edge case for ports applies the
+same as elsewhere. Remind them they can leave the server running or
+stop it with Ctrl+C; either way the next parts do not need it.
+
+Mark `serve`: done. Last chapter of the part: apply §Closing a part
+(the close names the part by its title and routes back to the menu;
+this is a mid-campaign payoff, NOT the campaign finale, so do not
+sign the campaign off here).

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

@@ -1,6 +1,6 @@
-# Parte 6 (a): Extender skill-map - settings (step library, `settings-*` ids)
+# Part 7 (a): Extend skill-map - settings (step library, `settings-*` ids)
 
-Step bodies for the settings chapters of Part 6 (config layers, the
+Step bodies for the settings chapters of Part 7 (config layers, the
 `sm config` verbs, the active provider lens), plus the shared step
 `settings-6-contributions` that the plugin-authoring chapters reuse.
 The SKILL.md orchestrator dispatches each `settings-*` chapter id

package/dist/cli.js

@@ -1,6 +1,6 @@
 // cli/entry.ts
 
-!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="dd2e1877-e17a-5d0b-86e5-6416814d7a78")}catch(e){}}();
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="542dae21-a4ed-50bb-ad3c-62e84e47b380")}catch(e){}}();
 import { existsSync as existsSync33 } from "fs";
 import { Builtins, Cli as Cli2 } from "clipanion";
 
@@ -246,7 +246,7 @@ function bucketByKind(kind, instance, bag) {
 // package.json
 var package_default = {
   name: "@skill-map/cli",
-  version: "0.53.1",
+  version: "0.53.3",
   description: "skill-map reference implementation \u2014 kernel + CLI + adapters.",
   license: "MIT",
   type: "module",
@@ -30251,4 +30251,4 @@ function resolveBareDefault() {
   process.exit(ExitCode.Error);
 }
 //# sourceMappingURL=cli.js.map
-//# debugId=dd2e1877-e17a-5d0b-86e5-6416814d7a78
+//# debugId=542dae21-a4ed-50bb-ad3c-62e84e47b380

package/dist/index.js

@@ -1,6 +1,6 @@
 // kernel/i18n/registry.texts.ts
 
-!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="5755b8d3-0320-507b-8287-e7141109764a")}catch(e){}}();
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="89adb52b-2657-5932-aa07-61e08ebbf98b")}catch(e){}}();
 var REGISTRY_TEXTS = {
   duplicateExtension: "Extension already registered: {{kind}}:{{qualifiedId}}",
   unknownKind: "Unknown extension kind: {{kind}}",
@@ -102,7 +102,7 @@ import { Tiktoken as Tiktoken2 } from "js-tiktoken/lite";
 // package.json
 var package_default = {
   name: "@skill-map/cli",
-  version: "0.53.1",
+  version: "0.53.3",
   description: "skill-map reference implementation \u2014 kernel + CLI + adapters.",
   license: "MIT",
   type: "module",
@@ -3632,4 +3632,4 @@ export {
   runScanWithRenames
 };
 //# sourceMappingURL=index.js.map
-//# debugId=5755b8d3-0320-507b-8287-e7141109764a
+//# debugId=89adb52b-2657-5932-aa07-61e08ebbf98b

package/dist/kernel/index.js

@@ -1,6 +1,6 @@
 // kernel/i18n/registry.texts.ts
 
-!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="c1e3d822-fab9-519a-9e3e-3ad2f7070d52")}catch(e){}}();
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="eda01250-1ec1-5934-9fb3-c95548eccf56")}catch(e){}}();
 var REGISTRY_TEXTS = {
   duplicateExtension: "Extension already registered: {{kind}}:{{qualifiedId}}",
   unknownKind: "Unknown extension kind: {{kind}}",
@@ -102,7 +102,7 @@ import { Tiktoken as Tiktoken2 } from "js-tiktoken/lite";
 // package.json
 var package_default = {
   name: "@skill-map/cli",
-  version: "0.53.1",
+  version: "0.53.3",
   description: "skill-map reference implementation \u2014 kernel + CLI + adapters.",
   license: "MIT",
   type: "module",
@@ -3632,4 +3632,4 @@ export {
   runScanWithRenames
 };
 //# sourceMappingURL=index.js.map
-//# debugId=c1e3d822-fab9-519a-9e3e-3ad2f7070d52
+//# debugId=eda01250-1ec1-5934-9fb3-c95548eccf56