@skill-map/cli 0.68.0 → 0.68.1

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

@@ -5,9 +5,13 @@ 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 (the daily loop, Part 3, runs and ships it).
-`pace: per-step`, `preflight: portfolio-init`. Shared
-conventions live in `_core.md`.
+is plain HTML the harness produces (the daily loop, Part 2, runs and ships it).
+This part runs end to end: it boots the project and grows its harness
+members (the `kickoff` to `real-kinds` chapters), then wires them into a
+connected graph, a link checker, a publish command, the handbook turned
+hub, and a close-up on connector confidence (the `check-links` to
+`confidence` chapters). `pace: per-step`, `preflight: portfolio-init`.
+Shared conventions live in `_core.md`.
 
 The orchestrator's `portfolio-init` pre-flight (backstage, silent)
 has already laid the bare project skeleton before the tester runs
@@ -33,7 +37,9 @@ The chapters grow the harness from there.
 - `real-kinds`: Codex's kinds are `agent` (TOML) + `skill` + `markdown`, there is
   no `command`. Lay only `docs/DEPLOY.md` here (STYLE landed in `first-agent`),
   and name the kinds as agent + skill + markdown (the skill + the publish piece
-  arrive in Part 2 as skills).
+  arrive later in this part as skills).
+- `publish`: Codex has no `command` kind, so the tester creates a **skill** at `.agents/skills/publish/SKILL.md` instead of `.claude/commands/publish.md`. The body is the Codex one (same `/check-links` + `@content-editor` + deploy reference); fetch it with `fixtures.js cat harness --file "__PROVIDER__/skills/publish/SKILL.md" --provider codex --lang <lang>`. Tell the tester they are creating a `skill` (one node, three connectors, same as the claude command). The fixture lays no `publish` for codex in this chapter (the tester authors it), so the `cat` is the source.
+- `links`: the `content-editor-style` reference is baked into the Codex content-editor's TOML (`developer_instructions`) at lay time, so the `edit content-editor-style` step is a no-op on Codex, the `content-editor -> docs/STYLE.md` arrow is already drawn from earlier in this part. Run only `edit agents-hub` and narrate the two `AGENTS.md` arrows; mention the style-guide arrow as already present.
 
 ## Chapter `kickoff` - Start the portfolio (~2 min)
 
@@ -106,8 +112,7 @@ then render it in the fenced block the tester copies:
 > as a file pointer (the same `@name.md` reference you met in the
 > prologue), and since the handbook is right there
 > the link resolves with full confidence. It tells anyone (and
-> skill-map) that `CLAUDE.md` defers to the handbook. This is exactly
-> how this tool's own repo is wired.
+> skill-map) that `CLAUDE.md` defers to the handbook.
 >
 > Did the connector light up?
 
@@ -126,8 +131,8 @@ Tell the tester:
 
 > I added the first real member of your harness: an agent called
 > `content-editor` (its job is to write the site's pages). A new
-> `agent` node appeared on the map. Right now it stands alone; in the
-> next part we wire it to the handbook and the style guide.
+> `agent` node appeared on the map. Right now it stands alone; later in
+> this part we wire it to the handbook and the style guide.
 >
 > 💡 Tip: I create these harness files for you. If you'd like to see
 > what's inside, open `<provider_dir>/agents/content-editor.md` in your
@@ -162,14 +167,166 @@ 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**: you add these (the link checker and
->   the publish command) in a later part.
+> - **skill** and **command**: you add these later in this part (the
+>   link checker and the publish command).
 >
 > Your handbook now has a real harness around it: a `content-editor`
 > agent plus its docs, all on the map.
 >
 > See the agent and the docs in the map?
 
-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).
+Wait for confirmation. Mark `real-kinds`: done.
+
+## Chapter `check-links` - The link checker (~3 min)
+
+**Context**: the harness needs a guard that runs before publishing, a skill that checks the site's internal links resolve before it ships. We only create the `skill` node here; the `publish` command in the next chapter is its caller.
+
+Lay the `check-links` skill (its content + translation live in
+`fixtures-data/`; this kind exists on every provider, so no skip).
+Backstage (silent):
+
+```
+node .claude/skills/sm-tutorial/scripts/fixtures.js lay harness --only "__PROVIDER__/skills/check-links/SKILL.md" --provider <provider> --lang <lang>
+```
+
+Tell the tester:
+
+> So I added that guard: a skill called `check-links`. A new `skill`
+> node appeared on the **Map**, alone for now; the next chapter gives
+> it a caller.
+>
+> See the new skill node?
+
+Wait for confirmation. Mark `check-links`: done.
+
+## Chapter `publish` - The publish command (~4 min)
+
+**Context**: this is the chapter where the graph comes alive. The `/publish` command ties three pieces together in one body: it invokes the link checker, mentions the content editor, and references the deploy runbook. Three connectors light up from a single new node, one per link syntax.
+
+Tell the tester to create the file themselves (it is their project's file, Inviolable rule #2). Substitute `<provider_dir>` per `_core.md` in the path you give them. Backstage, get the content: `node .claude/skills/sm-tutorial/scripts/fixtures.js cat harness --file "__PROVIDER__/commands/publish.md" --provider <provider> --lang <lang>`, then render it as a **top-level fenced code block**: at column 0, NOT inside the `> ` blockquote and with NO leading indentation, so the tester's copy keeps every line flush left. The frontmatter fences (`---`) MUST land on column 0. If the block is rendered (or pasted) indented, the opening and closing `---` shift off column 0, the YAML never parses, and the `publish` node loads body-only without its `name` / `description` (`sm check` then warns `frontmatter-malformed`). Present the block below exactly as written.
+
+> Create `.claude/commands/publish.md` with exactly this content (the first line is `---`, nothing before it):
+
+```markdown
+---
+name: publish
+description: |
+  Publishes the portfolio: runs the link check, hands off to the
+  content editor for any last fixes, then follows the deploy runbook.
+---
+
+# publish
+
+The one command you run when the site is ready to go out.
+
+## Steps
+1. Run /check-links on the pages in public/. If it reports broken links, stop and fix them first.
+2. If a page needs a content fix, brief @content-editor with the change.
+3. Follow the [deploy runbook](../../docs/DEPLOY.md): regenerate pages, run the link check, start the server.
+```
+
+Continue the tester message:
+
+> Save it. Watch the **Map**: **three** new arrows light up at once
+> from the new `publish` node, and each one is a different colour
+> because each one is a different kind of link:
+>
+> - `publish -> check-links` (kind: `invokes`), from the `/check-links`
+>   token in the body.
+> - `publish -> content-editor` (kind: `mentions`), from the
+>   `@content-editor` token.
+> - `publish -> docs/DEPLOY.md` (kind: `references`), from the
+>   `[deploy runbook](../../docs/DEPLOY.md)` markdown link.
+>
+> One node, three connectors, three link kinds. The harness is
+> starting to look like a real graph.
+>
+> 💡 Tip: to tidy every node into a clean layout, click the
+> **Re-arrange layout** button in the map toolbar. Handy whenever the
+> graph starts to look crowded.
+>
+> Did the three arrows appear?
+
+Wait for confirmation. You MAY use `Read` on the file afterwards to verify it landed, in particular that the opening and closing `---` are flush at column 0. If a later `sm check` flags `frontmatter-malformed` on `publish.md`, the fences got indented on paste: have the tester re-align every line flush left (strip the leading spaces so `---` is at column 0), then the next scan reads it clean. Mark `publish`: done.
+
+## Chapter `links` - The handbook becomes the hub (~4 min)
+
+**Context**: the handbook (`AGENTS.md`) has been a lonely node since the start of this part. Here it becomes the hub: we add two bullets so it mentions the content editor and invokes the publish command. We also give the content editor a reference to the style guide it follows. Several connectors land, and we recap the three link kinds and which syntax produced each.
+
+Apply both edits (their content + translation live in `fixtures-data/`).
+The first appends the two hub bullets to `AGENTS.md`; the second adds
+the style-guide reference line to the content-editor. Backstage (silent):
+
+```
+node .claude/skills/sm-tutorial/scripts/fixtures.js edit agents-hub --provider <provider> --lang <lang>
+node .claude/skills/sm-tutorial/scripts/fixtures.js edit content-editor-style --provider <provider> --lang <lang>
+```
+
+Tell the tester:
+
+> Two edits, and the **Map** fills in. Your handbook (`AGENTS.md`) is
+> now the hub: it points at the content editor and at the publish
+> command. And the content editor now reaches the style guide it
+> follows. New arrows:
+>
+> - `AGENTS.md -> content-editor` (kind: `mentions`), from `@content-editor`.
+> - `AGENTS.md -> /publish` (kind: `invokes`), from `/publish`.
+> - `content-editor -> docs/STYLE.md` (kind: `references`), from the
+>   `[style guide](../../docs/STYLE.md)` markdown link.
+>
+> Here is the whole recap of the three link kinds, one per syntax:
+>
+> - an `@handle` token is always a **mention**.
+> - a `/slash` token is always an **invoke**.
+> - a `[text](path.md)` markdown link is always a **reference**.
+>
+> The kind comes purely from how you wrote it. Your harness is wired
+> end to end now: the handbook reaches the work, the work reaches the
+> docs, and `/publish` pulls the whole publish flow together.
+>
+> Did the new arrows light up?
+
+Wait for confirmation. You MAY use `Read` on the two files afterwards to verify the edits landed before moving on. Mark `links`: done.
+
+## Chapter `confidence` - How sure is each link (~3 min)
+
+No file edits in this chapter, pure observation on the graph the tester just built.
+
+Tell the tester:
+
+> Last beat of this part: how sure is skill-map about each connection?
+> It records a **confidence** for every link and draws it as opacity:
+> a link that resolves to a real node is solid (**1.00**), a link that
+> does not lands fainter, so a glance at the **Map** separates the
+> solid wiring from the problem links.
+>
+> Open the Inspector for the `publish` node (click it on the **Map**).
+> Scroll down to the **Connections** panel and read the **Outgoing**
+> rows. Each row shows the link kind and a confidence badge, and here
+> every one reads **1.00**:
+>
+> - `publish -> docs/DEPLOY.md` (`references`) is a markdown link to a
+>   file that exists on disk, so skill-map is certain.
+> - `publish -> content-editor` (`mentions`) resolves to the real
+>   content-editor agent, and `publish -> check-links` (`invokes`)
+>   resolves to the real check-links skill, so both are certain too.
+>
+> Your whole harness reads solid because every link lands on a real
+> node, that is what a clean, fully wired graph looks like. So what
+> does a link that does NOT resolve look like? You met one back in the
+> prologue: `@demo-guideline` was a reference skill-map could not
+> resolve, it had nothing to land on, so skill-map drew no arrow and
+> flagged it as a **broken reference**, its confidence knocked down to
+> **0.50** by the broken penalty. The fix was one character: adding
+> `.md` (`@demo-guideline.md`) turned it into a file reference to the
+> real `demo-guideline.md`, and it drew a solid arrow at **1.00**.
+>
+> **IMPORTANT:** why does confidence matter? It mirrors how the runtime itself
+> resolves a reference: a deterministic name-and-path lookup, no guessing
+> and no scanning the tree for a file under some other extension. That is
+> cheaper and it does not fail, so the agent spends fewer tokens and less
+> time, the same reason a clean, well-named harness is worth keeping.
+>
+> Do you see every badge reading 1.00 in the Inspector?
+
+Wait for confirmation. Mark `confidence`: 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-settings.md

@@ -1,6 +1,6 @@
-# Part 4 (a): Extend skill-map - settings (step library, `settings-*` ids)
+# Part 3 (a): Extend skill-map - settings (step library, `settings-*` ids)
 
-Step bodies for the settings chapters of Part 4 (config layers, the
+Step bodies for the settings chapters of Part 3 (config layers, the
 `sm config` verbs, the active provider lens). The SKILL.md
 orchestrator dispatches each `settings-*` chapter id here;
 `authoring-*` ids it dispatches to `part-authoring.md`.

package/dist/cli/tutorial/sm-tutorial/scripts/state.js

@@ -236,8 +236,8 @@ function computeWipePaths(state) {
   // provider), so either part's presence means that fixture is on disk.
   if (has('fundamentals') || has('basic-fundamentals')) addFootprint('prologue');
   if (
-    has('project-kickoff') || has('connect-harness') || has('daily-loop')
-    || has('basic-kickoff') || has('basic-connect') || has('basic-daily')
+    has('project-kickoff') || has('daily-loop')
+    || has('basic-kickoff') || has('basic-daily')
   ) addFootprint('portfolio');
   if (has('extend')) addFootprint('master');
   // `cli` seeds the prologue demo fixture plus its external-ref demo.
@@ -274,5 +274,5 @@ function main() {
 }
 
 main();
-!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]="803fceb9-f545-5f51-8f46-4db3cba6abcf")}catch(e){}}();
-//# debugId=803fceb9-f545-5f51-8f46-4db3cba6abcf
+!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]="3ef90c0e-0700-5a7b-a25f-c47aa19fd567")}catch(e){}}();
+//# debugId=3ef90c0e-0700-5a7b-a25f-c47aa19fd567

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]="bde63370-f02c-51bb-92b1-0c58f46b6aee")}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]="a842c024-162c-5a3a-85db-1daea4b6735f")}catch(e){}}();
 import { existsSync as existsSync34 } from "fs";
 import { Builtins, Cli as Cli2 } from "clipanion";
 
@@ -250,7 +250,7 @@ function bucketByKind(kind, instance, bag) {
 // package.json
 var package_default = {
   name: "@skill-map/cli",
-  version: "0.68.0",
+  version: "0.68.1",
   description: "skill-map reference implementation \u2014 kernel + CLI + adapters.",
   license: "MIT",
   type: "module",
@@ -32062,13 +32062,15 @@ var TUTORIAL_TEXTS = {
   writtenLabelEn: "English",
   writtenLabelEs: "Espa\xF1ol",
   // Destination-provider prompt (interactive stdin, no `--for`). Header
-  // uses a yellow `?` glyph; options are a numbered list of provider
-  // label (with any `aka` agents in parentheses) + skill directory, with
-  // a `(default)` marker on the first option (Claude). The input line
-  // accepts a number, a provider id, or an empty answer (which takes the
-  // default).
+  // uses a yellow `?` glyph; options are a numbered list of the provider's
+  // vendor name (for a provider with an `aka`, the aka vendor leads and the
+  // provider label follows in parentheses), with a `(default)` marker on
+  // the first option (Claude). The destination folder is deliberately NOT
+  // shown: several providers share `.agents/skills`, so the folder does not
+  // identify the lens. The input line accepts a number, a provider id, or
+  // an empty answer (which takes the default).
   promptHeader: "{{glyph}}  Which agent should host the tutorial skill?",
-  promptOption: "     {{index}}) {{label}}: {{skillDir}}{{marker}}",
+  promptOption: "     {{index}}) {{label}}{{marker}}",
   promptDefaultMarker: "  (default)",
   promptInput: "  Enter the number or provider id [default {{index}}]: ",
   // Prompt answer matched neither an index nor an id. Goes to stderr,
@@ -32319,7 +32321,7 @@ function listScaffoldTargets(includeExperimental = false) {
   return out;
 }
 function labelWithAka(target) {
-  return target.aka.length > 0 ? `${target.label} (${target.aka.join(", ")})` : target.label;
+  return target.aka.length > 0 ? `${target.aka.join(", ")} (${target.label})` : target.label;
 }
 function renderTargetLines(targets, def, glyph) {
   const lines = [tx(TUTORIAL_TEXTS.promptHeader, { glyph })];
@@ -32329,7 +32331,6 @@ function renderTargetLines(targets, def, glyph) {
       tx(TUTORIAL_TEXTS.promptOption, {
         index: i + 1,
         label: labelWithAka(t),
-        skillDir: `${t.skillDir}/`,
         marker: t.id === def.id ? TUTORIAL_TEXTS.promptDefaultMarker : ""
       })
     );
@@ -32615,4 +32616,4 @@ function resolveBareDefault() {
   process.exit(ExitCode.Error);
 }
 //# sourceMappingURL=cli.js.map
-//# debugId=bde63370-f02c-51bb-92b1-0c58f46b6aee
+//# debugId=a842c024-162c-5a3a-85db-1daea4b6735f

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]="9e2b3a4e-2df6-5424-b6ce-30468020a39d")}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]="f0a24ed1-f91a-59a8-b2b9-db8168690990")}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.68.0",
+  version: "0.68.1",
   description: "skill-map reference implementation \u2014 kernel + CLI + adapters.",
   license: "MIT",
   type: "module",
@@ -4163,4 +4163,4 @@ export {
   runScanWithRenames
 };
 //# sourceMappingURL=index.js.map
-//# debugId=9e2b3a4e-2df6-5424-b6ce-30468020a39d
+//# debugId=f0a24ed1-f91a-59a8-b2b9-db8168690990

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]="f36575e1-2be1-582e-9ebc-c041fd1a716b")}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]="7dc46367-403b-5856-87b8-23673c2d3f6c")}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.68.0",
+  version: "0.68.1",
   description: "skill-map reference implementation \u2014 kernel + CLI + adapters.",
   license: "MIT",
   type: "module",
@@ -4163,4 +4163,4 @@ export {
   runScanWithRenames
 };
 //# sourceMappingURL=index.js.map
-//# debugId=f36575e1-2be1-582e-9ebc-c041fd1a716b
+//# debugId=7dc46367-403b-5856-87b8-23673c2d3f6c