@skill-map/cli 0.70.0 → 0.72.0

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

@@ -45,10 +45,6 @@ The chapters grow the harness from there.
 
 ## Chapter `kickoff` - Start the portfolio (~2 min)
 
-**Context**: same `sm init` the tester learned in the prologue, but
-now on a real project. The map will show the project's harness, not
-throwaway demo nodes.
-
 If the prologue (`fundamentals`) ran first in this directory, the
 demo fixture (`demo-agent`, `demo-skill`, `notes/…`) is still on
 disk. The orchestrator's `portfolio-init` already cleared it during
@@ -90,12 +86,6 @@ Wait for confirmation. Mark `kickoff`: done.
 
 ## Chapter `manual` - The handbook (AGENTS.md) and CLAUDE.md (~2 min)
 
-**Context**: the dogfood beat. Real Claude Code projects can
-reference the generic `AGENTS.md` from their `CLAUDE.md` (this very
-repo does). That one-line pointer is a real `references` link (the
-`.md` extension makes `@AGENTS.md` a file pointer), the tester's first
-connector on the real project.
-
 Tell the tester to create the file themselves (it is their project's
 file, Inviolable rule #2). Backstage, get the content:
 `node .claude/skills/sm-tutorial/scripts/fixtures.js cat portfolio --file "CLAUDE.md" --provider <provider> --lang <lang>`,
@@ -147,11 +137,6 @@ Wait for confirmation. Mark `first-agent`: done.
 
 ## Chapter `real-kinds` - The real kinds in context (~2 min)
 
-**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 the Daily Loop's maintenance beats have something to point at.
-
 Lay the two markdown docs the harness references later (their content
 + translation live in `fixtures-data/`). Backstage (silent):
 
@@ -181,8 +166,6 @@ 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):
@@ -203,9 +186,7 @@ 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.
+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, line for line: never soft-wrap, and never let a newline fall inside a `[text](path)` link (a break inside the `(path)`, e.g. `(../../docs/DEPLOY.md)`, splits it and the link stops resolving). See `_core.md` §Language mirroring + fixture content.
 
 > Create `.claude/commands/publish.md` with exactly this content (the first line is `---`, nothing before it):
 
@@ -253,8 +234,6 @@ Wait for confirmation. You MAY use `Read` on the file afterwards to verify it la
 
 ## 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):
@@ -325,9 +304,10 @@ Tell the tester:
 >
 > **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.
+> and no scanning the tree for a file under some other extension. A link that
+> does not resolve sends the agent guessing and retrying, which burns time and
+> tokens; a deterministic one does not fail and resolves first try, the same
+> reason a clean, well-named harness is worth keeping.
 >
 > Do you see every badge reading 1.00 in the Inspector?
 

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

@@ -22,9 +22,6 @@ stop, do not try to re-init mid-chapter.
 
 ## Step `settings-1-layers` - the config layers (~3 min)
 
-**Context**: where settings live and how `sm` resolves a value
-when more than one place sets it.
-
 > `sm` resolves every setting through a stack of **layers**, each
 > one overriding the layer below it:
 >
@@ -74,9 +71,6 @@ Mark `settings-1-layers: done`.
 
 ## Step `settings-2-resolve` - read, resolve, and set a value (~3 min)
 
-**Context**: the four config verbs (`get`, `show`, `set`, `reset`)
-and how `show --source` reveals which layer won.
-
 > Read a single setting. We'll use `scan.maxNodes`, the cap on how
 > many nodes a scan walks:
 
@@ -123,10 +117,8 @@ Mark `settings-2-resolve: done`.
 
 ## Step `settings-3-lens` - the active provider lens (~2 min)
 
-**Context**: the single most consequential setting, the lens that
-decides which provider types the project's files. It auto-detects and
-never touches your `.md` files. (Agent: substitute `<provider>` with
-`tutorial.provider`, the lens this run was scaffolded for.)
+(Agent: substitute `<provider>` with `tutorial.provider`, the lens
+this run was scaffolded for.)
 
 > One setting earns its own step: the **active provider lens**. A
 > skill-map project reads its files through exactly **one** provider

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

@@ -78,7 +78,10 @@ function writeFileEnsuring(abs, content) {
  * tier, then the per-provider overlay (`providers/<provider>/{shared,<lang>}/`).
  * The overlay carries the skill-shaped variants of nodes a lens renders
  * differently (e.g. the `content-editor` agent becomes a skill on
- * agent-skills); claude declares no overlay because the base IS its shape.
+ * agent-skills). claude is mostly the base shape, but it still carries a tiny
+ * overlay for the entry-pointer file: the portfolio root pointer is `CLAUDE.md`
+ * (claude/codex overlays) vs `README.md` (agent-skills / antigravity), so it
+ * cannot live in the universal base `shared/` tier.
  */
 function laySet(manifest, set, o, only = null) {
   const { kinds } = pdirAndKinds(o);
@@ -297,5 +300,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]="9e366749-efd9-5bc5-bba4-41147eabf625")}catch(e){}}();
-//# debugId=9e366749-efd9-5bc5-bba4-41147eabf625
+!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]="b7c7dad8-e6ce-5918-a25b-41b4e2d13a4c")}catch(e){}}();
+//# debugId=b7c7dad8-e6ce-5918-a25b-41b4e2d13a4c