@skill-map/cli 0.61.1 → 0.61.2

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

@@ -131,14 +131,16 @@ element. Decide with §Provider detection:
 
 - `provider == claude` (Claude Code, blockquotes render as a styled
   left bar): emit tester-facing messages with `> ` on every line,
-  including blank lines inside a multi-paragraph block.
-- `provider != claude` (Antigravity CLI, agent-skills, any other
-  host: most non-Claude renderers show `>` as a literal character):
-  emit **plain prose**, NO `> ` prefix anywhere.
+  including blank lines inside a multi-paragraph block. This is the
+  only active path today.
+- `provider != claude` (coming soon: Antigravity CLI, agent-skills,
+  any other host where most non-Claude renderers show `>` as a
+  literal character): emit **plain prose**, NO `> ` prefix anywhere.
+  Kept as the wiring for the coming-soon providers; not exercised
+  while the tutorial demos `claude` only.
 
 Sample messages throughout the part files are written in the Claude
-variant (with `> `); strip the prefix when the host is non-Claude,
-the wording is unchanged.
+variant (with `> `).
 
 **The rule, in one line**: every tester-facing line of prose carries
 the `> ` bar in the Claude variant, context sentences, intros, tips,
@@ -257,41 +259,41 @@ on-disk convention:
 | Provider       | Base dir          | Kinds it claims             | Detect via env var(s)                                  |
 |----------------|-------------------|-----------------------------|--------------------------------------------------------|
 | `claude`       | `.claude/`        | `agent`, `command`, `skill` | `CLAUDECODE=1` OR `AI_AGENT` starts with `claude-code` |
-| `agent-skills` | `.agents/skills/` | `skill` only (vendor-neutral; also the on-disk home for Google's Antigravity CLI, which replaced the Gemini CLI on 2026-05-19 and adopted this open standard) | no formal env yet; opt-in if the tester says so |
-| `openai`       | `.codex/`         | `agent` (`.codex/agents/*.toml`) | no formal env yet; informational today |
-
-**Decision logic, applied silently during pre-flight**:
-
-1. Inspect the agent's environment (`process.env`).
-2. Claude-flavoured var present → `provider = claude`,
-   `<provider_dir> = .claude`, kinds = `{agent, command, skill}`.
-3. Else if the tester says Antigravity / agent-skills (opt-in) →
-   `provider = agent-skills`, `<provider_dir> = .agents`, kinds =
-   `{skill}`.
-4. Else → **fallback to claude** AND surface one short message so
-   they can correct course (render `> ` if it turns out to be
-   Claude, plain prose if they correct you):
-
-   > Heads up: I couldn't detect which agent runtime is hosting me,
-   > so I'll demo skill-map's Claude provider (`.claude/`). If you
-   > actually use Antigravity or agent-skills, tell me and I swap
-   > the fixture to `.agents/skills/`.
+| `agent-skills` | `.agents/skills/` | `skill` only (vendor-neutral; also the on-disk home for Google's Antigravity CLI, which replaced the Gemini CLI on 2026-05-19 and adopted this open standard) | coming soon (not selectable in the tutorial yet) |
+| `openai`       | `.codex/`         | `agent` (`.codex/agents/*.toml`) | coming soon (not selectable in the tutorial yet) |
+
+**Decision logic, applied silently during pre-flight**: the tutorial
+demonstrates the `claude` provider only. `agent-skills` and `openai`
+are **coming soon** and are not selectable here, so there is no
+runtime to detect or opt into.
+
+1. `provider = claude`, `<provider_dir> = .claude`, kinds =
+   `{agent, command, skill}`. Always.
+2. Do NOT offer Antigravity / agent-skills / openai as an alternative,
+   and do NOT ask the tester which runtime hosts them. If a tester
+   says they use another runtime, acknowledge it briefly and explain
+   that those providers are coming soon, the tutorial demos `claude`
+   (`.claude/`) today:
+
+   > Heads up: skill-map also reads Antigravity, agent-skills and
+   > Codex projects, but those providers are coming soon in this
+   > tutorial. We'll demo skill-map's Claude provider (`.claude/`)
+   > today.
 
 Persist `provider` into the state file (`tutorial.provider`) so a
-resumed session does not re-detect.
+resumed session does not re-detect. (It is always `claude` for now.)
 
 **Global substitution rule**: the fixture scripts do the file-level
 work. You pass `--provider <p>` (the value persisted in
 `tutorial.provider`) and `--lang <l>`, and they resolve the
 `__PROVIDER__` path token, skip files whose kind the provider does
 not claim, and report the adjusted `nodeCount` plus the `skipped`
-list in their summary. Your job is the **narration**: wherever a part
-file's tester-facing prose says `.claude/`, swap it for the detected
-`<provider_dir>`, and narrate the node count from the script summary
-(on `agent-skills` / Antigravity only the skill + markdown notes
-exist, so the count is lower and the agent / command beats fold
-away). The campaign cross-link chapters target `claude` today (see
-the reality check below).
+list in their summary. Today `provider` is always `claude`, so the
+narration uses `.claude/` throughout; the `--provider` plumbing stays
+wired so the coming-soon providers (`agent-skills` / Antigravity,
+`openai`) drop in later without a narrative rewrite. The campaign
+cross-link chapters target `claude` today (see the reality check
+below).
 
 **Reality check (don't mention to the tester)**: this skill ships
 at `.claude/skills/sm-tutorial/`, so Claude Code is the only host

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

@@ -35,9 +35,11 @@ marker for the `openai` lens) sitting next to the `.claude/` folder
 (the `claude` marker, where the tutorial skill itself lives). With two
 markers present, `sm init`'s first scan can NOT auto-pick a lens and
 asks the tester to choose (`⚠ Multiple provider markers detected`).
-The portfolio is a Claude project, so the answer is `claude`. The
-prompt is expected, blessed behaviour; the tester just needs to know
-which option to pick, so the message below previews it.
+The portfolio is a Claude project, so the answer is always `claude`,
+the other options the prompt lists (`openai`/Codex and friends) are
+coming soon in the tutorial and we do not walk them. The prompt is
+expected, blessed behaviour; the tester just needs to know which
+option to pick, so the message below previews it.
 
 ```bash
 sm init
@@ -52,8 +54,8 @@ Tell the tester:
 > site). skill-map maps that harness.
 >
 > Run `sm init`. If it asks you to pick a lens (`⚠ Multiple provider
-> markers detected`), choose `claude`, this is a Claude project. Then
-> run `sm` to boot the live UI.
+> markers detected`), choose `claude`, this is a Claude project (the
+> other lenses are coming soon). Then run `sm` to boot the live UI.
 >
 > Open the URL `sm` printed. You'll see **one node**: `AGENTS.md`,
 > the project's handbook (the operating manual for the site).

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

@@ -122,24 +122,20 @@ catalog is closed.)
 
 Mark `settings-2-resolve: done`.
 
-## Step `settings-3-lens` - the active provider lens (~4 min)
+## 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 is reversible
-and never touches your `.md` files, only the scan cache.
+decides which provider types the project's files. It auto-detects and
+never touches your `.md` files, only the scan cache.
 
 > One setting earns its own step: the **active provider lens**. A
 > skill-map project sees its filesystem through exactly **one**
 > provider at a time, and that lens decides how each file is read.
 > Under the `claude` lens a `.claude/agents/*.md` is an agent and
-> `@`-mentions / `/`-commands become links; point the lens at
-> `openai` and the same tree is read against Codex's layout instead.
-> Same files, different reading.
+> `@`-mentions / `/`-commands become links. Same files, one reading.
 
 > The lens auto-detects on the first scan from the markers in your
-> project (`.claude/` → claude, `.codex/` or a root `AGENTS.md` →
-> openai, `.agents/` → agent-skills). Scan once and check where it
-> landed:
+> project (`.claude/` → claude). Scan once and check where it landed:
 
 ```bash
 sm scan
@@ -151,39 +147,13 @@ Expected: the scan prints a line like `Auto-detected activeProvider
 .skill-map/settings.json`, and `get` then reports `claude`. The lens
 is just a key in `settings.json`, persisted like any other setting.
 
-> Now switch it by hand and watch what happens. We'll point it at
-> `openai`:
-
-```bash
-sm config set activeProvider openai
-```
-
-Expected: alongside the usual `✓  activeProvider = openai  (wrote
-.skill-map/settings.json)`, the CLI warns `Lens switched. Cleared 7
-scan table(s) ... Run sm scan to repopulate the graph under the new
-lens`. The important part: it cleared the **scan cache only**, your
-`.md` files are untouched. The graph is derived data; the source is
-always your filesystem.
-
-> Re-scan under the new lens, then put it back the way you found it:
-
-```bash
-sm scan
-sm config reset activeProvider
-sm scan
-```
-
-Expected: the first scan repopulates under `openai`; `reset` removes
-the key (`Removed activeProvider from .skill-map/settings.json`); the
-last scan auto-detects `claude` again from your `.claude/` marker.
-Back where you started, nothing lost.
-
-> That's the whole idea of the lens: one project, one active
-> provider at a time, chosen by `activeProvider` and backed by the
-> built-in provider plugins (`claude`, `openai`, `agent-skills`,
-> `antigravity`). Switching it is cheap and reversible because the
-> graph is always rebuilt from your files, never the other way
-> around.
+> Other lenses exist in the engine (`openai` for Codex,
+> `agent-skills`, `antigravity`), but they are **coming soon** in the
+> tutorial: today we demo the `claude` lens only. The idea to keep is
+> the one above, one project reads through exactly one provider at a
+> time, chosen by `activeProvider`. The lens is cheap to change later
+> because the graph is always rebuilt from your files, never the
+> other way around.
 
 Mark `settings-3-lens: done`.
 

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]="9a536139-6f70-53a7-b32a-eed4fc49b7a4")}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]="e231edcd-bd03-5552-a0d2-b977373884d8")}catch(e){}}();
 import { existsSync as existsSync33 } 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.61.1",
+  version: "0.61.2",
   description: "skill-map reference implementation \u2014 kernel + CLI + adapters.",
   license: "MIT",
   type: "module",
@@ -31057,4 +31057,4 @@ function resolveBareDefault() {
   process.exit(ExitCode.Error);
 }
 //# sourceMappingURL=cli.js.map
-//# debugId=9a536139-6f70-53a7-b32a-eed4fc49b7a4
+//# debugId=e231edcd-bd03-5552-a0d2-b977373884d8

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]="3bc6390b-70e8-568a-835e-870172658869")}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]="2ededba2-1ecd-5a1b-a725-23567a98a0b7")}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.61.1",
+  version: "0.61.2",
   description: "skill-map reference implementation \u2014 kernel + CLI + adapters.",
   license: "MIT",
   type: "module",
@@ -3847,4 +3847,4 @@ export {
   runScanWithRenames
 };
 //# sourceMappingURL=index.js.map
-//# debugId=3bc6390b-70e8-568a-835e-870172658869
+//# debugId=2ededba2-1ecd-5a1b-a725-23567a98a0b7

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]="1b30d8c8-edea-5922-be87-39c4ebe079c0")}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]="8f7ca4a9-1a8e-5b21-a436-9a4500fd710f")}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.61.1",
+  version: "0.61.2",
   description: "skill-map reference implementation \u2014 kernel + CLI + adapters.",
   license: "MIT",
   type: "module",
@@ -3847,4 +3847,4 @@ export {
   runScanWithRenames
 };
 //# sourceMappingURL=index.js.map
-//# debugId=1b30d8c8-edea-5922-be87-39c4ebe079c0
+//# debugId=8f7ca4a9-1a8e-5b21-a436-9a4500fd710f