@skill-map/cli 0.53.6 → 0.55.0

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

@@ -11,7 +11,7 @@ description: |
   `tutorial-state.yml` for pause/resume. Triggers: "tutorial",
   "sm-tutorial", "tutorial me", "run the tutorial", "ejecuta el
   tutorial", "test skill-map", "advanced tutorial", "go deeper",
-  "tutorial avanzado", "ejecuta el tutorial maestro".
+  "tutorial avanzado".
 ---
 
 # sm-tutorial: the skill-map book
@@ -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 6", off by one from the menu), a
+> the internal `order` index ("Part 4", off by one from the menu), a
 > raw "chapter id", or tour jargon ("the settings tour").
 
 ## Pre-flight (run once, silent on success)
@@ -201,9 +201,9 @@ set: `<provider_dir>/agents/demo-agent.md`,
 `notes/private-credentials.md`. This is the
 single source for that list. Four entry points delete exactly this set
 when the prologue ran first in the dir: `portfolio-init`, the campaign
-`seed` fast-forward, and `backstage-init` (Part 6), each so the part's
+`seed` fast-forward, and `backstage-init` (Part 4), each so the part's
 own fixture starts from a clean slate, plus start-over (§Menu, resume,
-wrap-up). Part 7 `cli` is the inverse
+wrap-up). Part 5 `cli` is the inverse
 consumer: its `prologue-built` seed *lays* this fixture (the
 connector-chapter subset, without `notes/private-credentials.md`)
 instead of deleting it, see `fixtures.md` §Seed snapshots. Keep the list
@@ -286,6 +286,8 @@ tutorial:
   provider: "<claude | agent-skills | antigravity>"
 tester:
   level: 2
+  # site_identity: { name, tagline } is added by the daily-loop `setup`
+  # chapter when the tester names their portfolio; absent until then.
 parts: {}   # filled in as the tester picks parts from the menu
 findings_file: "./findings.md"
 ```
@@ -335,7 +337,7 @@ When a part begins, honour its `preflight` from the manifest:
   `preflight: seed` to fast-forward into them directly, see the `seed`
   case below; `portfolio-init` is just Part 1's flavour of that,
   handling the Part 0 to Part 1 transition.)
-- **`backstage-init`** (Part 6 `extend`): the part teaches plugins on
+- **`backstage-init`** (Part 4 `extend`): the part teaches plugins on
   its own **master fixture**, distinct from both the demo and the
   portfolio, so on entry make the master fixture the only one on disk.
   Silently, with no narration: (1) clear whatever prior-part fixture is
@@ -355,10 +357,10 @@ When a part begins, honour its `preflight` from the manifest:
   `Write` the part's fixture (read `references/fixtures.md` for the
   verbatim `master-agent` / `master-skill` / `notes/ideas` files; skip
   kinds the provider doesn't claim). If nothing needed clearing and the
-  dir was already initialised with the master fixture in place (Part 6
+  dir was already initialised with the master fixture in place (Part 4
   re-entry), that is fine: skip the init and just ensure the fixture
   files are present.
-- **`seed: prologue-built`** (Part 7 `cli`): the part reads the **Part 0
+- **`seed: prologue-built`** (Part 5 `cli`): the part reads the **Part 0
   demo fixture**, NOT the cumulative portfolio, so on entry make that
   fixture the one on disk. Read the state, then:
   - Demo fixture already present (the tester came straight from the
@@ -371,21 +373,13 @@ When a part begins, honour its `preflight` from the manifest:
     lay the `prologue-built` snapshot from `fixtures.md` (§Seed
     snapshots), `sm init`, `sm scan`.
   - Nothing there → lay the snapshot, `sm init`, `sm scan`.
-- **`seed`** (the campaign parts `connect-harness` / `run-harness` /
-  `maintain` / `mcp` / `live-site`): the part builds on the accumulating portfolio
-  harness, but the tester may have jumped straight here from the menu.
-  On entry, read the state file:
+- **`seed`** (the campaign parts `connect-harness` and `daily-loop`):
+  the part builds on the accumulating portfolio harness, but the tester
+  may have jumped straight here from the menu. On entry, read the state
+  file:
   - If every predecessor campaign part up the `prereq` chain is `done`
     → reuse the accumulated state; an `sm scan` to refresh is enough,
-    nothing to lay. **`mcp` is the exception**: it is ordered last,
-    after `extend` (Part 6) and `cli` (Part 7), which both replace the
-    portfolio on disk with their own master / demo fixture, so its
-    accumulated state cannot be trusted to still be the portfolio.
-    `mcp` therefore ALWAYS re-lays its `harness-connected` snapshot on
-    entry (clearing a master / demo fixture first if one is present,
-    the same clears the `backstage-init` and `prologue-built` cases
-    do), then `sm init` if `.skill-map/` is missing and `sm scan`,
-    exactly like the fast-forward branch below.
+    nothing to lay.
   - Else → **fast-forward, silently** (backstage, do not narrate the
     plumbing): first, if the prologue ran first in this dir, clear the
     full Part 0 demo fixture set (§Fixture and state templates) so the
@@ -423,16 +417,20 @@ All three are specified in `_core.md`:
 - **Routing + menu**: §Routing + menu. The session always starts at
   the **numbered start menu** (Part 0 is option 1, the recommended
   first pick); the menu (the ToC from `_manifest.yml`, numbered,
-  completed parts ticked, `planned` parts hidden, `prereq` gating only
-  seedless parts, none today since Part 7 `cli` now self-seeds) is the
-  entry point on the first
+  completed parts ticked, `planned` parts hidden (so `mcp` stays out of
+  the menu), `prereq` gating only seedless parts, none today since
+  `cli` now self-seeds) is the entry point on the first
   invocation and after every part closes / on resume. Render it with
   the format in `_core.md` §Menu format.
 - **Resume / restart**: §Resume / restart. On start-over, the exact
   wipe list is whatever the tester's parts actually created:
   `tutorial-state.yml`, `findings.md`, `.skillmapignore`,
   `.skill-map/`, the full Part 0 demo fixture set (§Fixture and state
-  templates), the Part 6 fixture if `extend` ran
+  templates), the portfolio fixture if any campaign part ran (see
+  `fixtures.md` §Portfolio fixture + §Seed snapshots, including the Daily
+  Loop's own additions: `docs/draft.md`, `public/style.css` and the
+  generated pages, the renamed `new-page` command, `AGENTS.sm`, and
+  `.skill-map/settings.local.json`), the Part 4 fixture if `extend` ran
   (`<provider_dir>/agents/master-agent.md`,
   `<provider_dir>/skills/master-skill/`, `notes/ideas.md`,
   `.skill-map/plugins/`), `link-validation/` if the CLI part ran,

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

@@ -1,9 +1,9 @@
 # Core conventions (shared by every part)
 
-This file is the single home for the conventions that used to be
-duplicated across the two old skills (`sm-tutorial` + `sm-master`).
-The orchestrator `SKILL.md` loads it once; every `part-*.md` step
-library assumes it. Do NOT restate these rules inside a part file.
+This file is the single home for the conventions shared by every part
+of the tutorial. The orchestrator `SKILL.md` loads it once; every
+`part-*.md` step library assumes it. Do NOT restate these rules inside
+a part file.
 
 The tutorial is **one book**: an ordered sequence of **chapters
 grouped in parts**, listed in `_manifest.yml`. A chapter is the
@@ -20,7 +20,8 @@ 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 8 the MCP appendix). Use it in `**Context**:` blocks and author
+  Part 5 the CLI deep-dive; `mcp` at Part 6 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.
 - **Tester-facing (`S.N`)**: every part is a **section** numbered by
@@ -318,11 +319,11 @@ For every chapter:
   §Menu format).
 - **Which parts to list**: parts in `order`, `status: active` only
   (`planned` parts are hidden). A part with a `seed` (the campaign
-  parts plus Part 7 `cli`) is always shown, even out of order, its
+  parts plus `cli`) is always shown, even out of order, its
   `preflight: seed` fast-forwards the project into it (SKILL.md
   §Entering a part). A part with a `prereq` but NO `seed` would be
   shown only once its `prereq` is `done`; no active part is in that
-  state today (Part 7 `cli` used to be, now it self-seeds).
+  state today (`cli` used to be, now it self-seeds).
 - **After the tester picks**: walk that part; when it ends, run
   §Closing a part (a tester-facing close, then this menu).
 - **Adding content** is data-only: a new chapter in a part (or a new

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

@@ -20,7 +20,7 @@
 #   seed         which snapshot to fast-forward to when this part is
 #                entered out of order (see fixtures.md §Seed snapshot:*).
 #                Campaign parts use a cumulative portfolio snapshot;
-#                Part 8 `cli` uses the standalone `prologue-built` demo.
+#                `cli` uses the standalone `prologue-built` demo.
 #   prereq       recommended predecessor. Gates the menu ONLY for a part
 #                with NO `seed`; a seedable part is always shown (its
 #                seed bridges the gap, predecessors get marked `skipped`).
@@ -51,7 +51,7 @@ parts:
       - id: ignore          ; title: "Silence a file via .skillmapignore"  ; est_min: 2
 
   - id: extend
-    order: 6
+    order: 4
     title: "Extend skill-map for the site"
     # Spans three chapter libraries; dispatch by chapter-id prefix:
     #   settings-*  -> part-settings.md
@@ -81,7 +81,7 @@ parts:
       - id: authoring-6-upgrade      ; title: "Try `sm plugins upgrade`" ; est_min: 2
 
   - id: cli
-    order: 7
+    order: 5
     title: "The CLI in depth"
     step_file: part-cli.md
     pace: auto-advance
@@ -132,59 +132,38 @@ parts:
       - id: links       ; title: "Mentions (@) and references between assets" ; est_min: 3
       - id: confidence  ; title: "Connector confidence (opacity = certainty)" ; est_min: 2
 
-  - id: run-harness
+  - id: daily-loop
     order: 3
-    title: "Run the harness (your site, live)"
-    step_file: part-run-harness.md
-    pace: auto-advance
-    preflight: seed
-    seed: harness-connected   # fast-forward to here if the earlier parts are not done
-    prereq: connect-harness
-    status: active
-    chapters:
-      - id: generate    ; title: "The agent generates the HTML in public/" ; est_min: 3
-      - id: serve       ; title: "node server.js: your portfolio, live next to the graph" ; est_min: 3
-      - id: editor-live ; title: "Let the content-editor agent write a posts page (optional)" ; est_min: 3
-
-  - id: maintain
-    order: 4
-    title: "Maintain the harness"
-    step_file: part-maintain.md
+    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
+    fixture: portfolio        # reuses the wired harness; lays the pretty site (style.css + pages) as taught steps
     status: active
     chapters:
-      - id: broken-ref   ; title: "A ref breaks (you rename DEPLOY.md)" ; est_min: 3
-      - id: analyzers    ; title: "The analyzer catalogue (what sm check catches)" ; est_min: 3
-      - id: orphans      ; title: "Orphans (a page nobody links to)" ; est_min: 2
-      - id: reserved     ; title: "Reserved names" ; est_min: 2
-      - id: sidecar      ; title: "Annotations .sm and consent" ; est_min: 3
+      - id: setup            ; title: "Make it yours, make it presentable" ; est_min: 3
+      - id: add-page         ; title: "Add a page with your agent" ; est_min: 4
+      - id: orphan-draft     ; title: "A page nobody links to yet" ; est_min: 2
+      - id: wire-and-improve ; title: "Wire the draft in" ; est_min: 3
+      - id: broken-ref       ; title: "A rename breaks a link" ; est_min: 4
+      - id: reserved         ; title: "A reserved name collides" ; est_min: 2
+      - id: publish          ; title: "Ship it: run /publish for real" ; est_min: 4
+      - id: sidecar          ; title: "Annotate the handbook (.sm and consent)" ; est_min: 3
+      - id: golive           ; title: "Your portfolio, 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: 8
-    title: "MCP"            # standalone appendix, ordered last; ALWAYS re-seeds harness-connected (extend/cli wipe the portfolio before it)
+    order: 6
+    title: "MCP"
     step_file: part-mcp.md
     pace: auto-advance
     preflight: seed
-    seed: harness-connected   # fast-forward to here if the earlier parts are not done
+    seed: harness-connected
     prereq: connect-harness
-    status: active
+    status: planned           # temporarily disabled, hidden from the menu. Body exists; re-enable when MCP returns.
     chapters:
       - id: mcp-node ; title: "content-editor declares an MCP tool; the mcp:// node appears" ; est_min: 3
 
-  - id: live-site
-    order: 5
-    title: "Ship the site (the full publish pipeline)"  # the finale / climax
-    step_file: part-live-site.md
-    pace: auto-advance
-    preflight: seed
-    seed: harness-connected   # fast-forward to here if the earlier parts are not done
-    prereq: connect-harness
-    status: active
-    chapters:
-      - id: pipeline ; title: "Run /publish end to end (check-links, brief, deploy runbook)" ; est_min: 4
-      - id: golive   ; title: "Ship it: the richer site live next to the full graph" ; est_min: 3
-
 findings_file: "./findings.md"

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

@@ -1,7 +1,7 @@
 # Fixture templates
 
 Fixtures the orchestrator lays for the auto-fixtured parts. Two full
-templates live here: the **master fixture** (Part 6, "Extend
+templates live here: the **master fixture** (Part 4, "Extend
 skill-map", `backstage-init`) right below, and the **portfolio
 fixture** (Part 1, "The project from zero", `portfolio-init`) at the
 end of this file. The **Part 0 demo fixture** is not templated here:
@@ -18,7 +18,7 @@ context for. Holds for every command fixture wherever it is defined
 (today: the prologue `demo-command`, the `publish` command, and the
 `reserved` chapter's `init`).
 
-## Master fixture (Part 6): layout (per provider)
+## Master fixture (Part 4): layout (per provider)
 
 Per §Provider detection in `SKILL.md`, the `<provider_dir>`
 placeholder resolves to `.claude/` or `.agents/skills/` depending
@@ -130,7 +130,7 @@ Per finding:
 Laid backstage before the tester's `sm init` in Part 1. The Express
 skeleton (`server.js`, `package.json`, `public/index.html`) is plain
 scaffolding, not `.md`, so the scan ignores it; it makes the project
-real and runnable (Part 3 runs it, Part 5 ships it). The one boot node is the
+real and runnable (the daily loop, Part 3, runs and ships it). The one boot node is the
 handbook `AGENTS.md`. On `agent-skills` / Antigravity (no `agent`
 kind) the harness still works: the agent member is created as a skill
 in a later chapter.
@@ -148,6 +148,14 @@ Layout:
 └── package.json
 ```
 
+The daily loop (Part 3) grows this further as taught steps, all Layer 2
+or loose notes (not part of the harness graph): `public/style.css` plus
+the generated pages (`index.html` rewritten, `about.html`,
+`projects.html`, `posts.html`), `docs/draft.md`, the renamed `new-page`
+command, `AGENTS.sm`, and `.skill-map/settings.local.json`. The
+start-over wipe and the `extend` / `cli` clears account for them via
+this section.
+
 ### File: `AGENTS.md` (kind: markdown, the boot node)
 
 No frontmatter: a real handbook is plain prose (this repo's own
@@ -208,7 +216,7 @@ Append to the universal `.skillmapignore` (written in pre-flight, see
 ## Seed snapshots (for `preflight: seed`)
 
 When the orchestrator enters a seedable part out of order (the campaign
-parts when their predecessors are not `done`, or Part 7 `cli` when the
+parts when their predecessors are not `done`, or Part 5 `cli` when the
 demo fixture is not the one on disk), it fast-forwards the project by
 laying the snapshot below, then `sm init` (if `.skill-map/` is missing) +
 `sm scan`. These are **checklists, not content**: each row names a file
@@ -231,7 +239,7 @@ any cross-links:
 3. `<provider_dir>/agents/content-editor.md`  <-  part-project-kickoff.md, chapter `first-agent`.
 4. `docs/STYLE.md` and `docs/DEPLOY.md`  <-  part-project-kickoff.md, chapter `real-kinds`.
 
-### Seed snapshot: `harness-connected` (start of Parts 3-6)
+### Seed snapshot: `harness-connected` (start of the daily-loop part)
 
 Everything in `harness-built`, PLUS the Part 2 wiring:
 
@@ -243,12 +251,12 @@ Everything in `harness-built`, PLUS the Part 2 wiring:
 After laying a campaign snapshot the map matches the state a tester would
 have at the END of the part just before the one being entered.
 
-### Seed snapshot: `prologue-built` (Part 7 `cli`)
+### Seed snapshot: `prologue-built` (Part 5 `cli`)
 
 NOT cumulative and NOT the portfolio: this is the **Part 0 demo
 fixture**, the six standalone demo nodes with `notes/todo` wired as the
 hub, the clean state (`✓ No issues`) at the end of the prologue's
-connector chapters. Part 7 only reads it. Because it is a different
+connector chapters. Part 5 only reads it. Because it is a different
 fixture from the portfolio, entry first resets any portfolio on disk
 (see SKILL.md §Entering a part, the `cli` case).
 

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

@@ -1,6 +1,6 @@
-# Part 6 (c): Extend skill-map - build plugins (step library, `authoring-*` ids)
+# Part 4 (c): Extend skill-map - build plugins (step library, `authoring-*` ids)
 
-Step bodies for the plugin-authoring chapters of Part 6.
+Step bodies for the plugin-authoring chapters of Part 4.
 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-cli.md

@@ -1,4 +1,4 @@
-# Part 7: The CLI in depth - step library
+# Part 5: The CLI in depth - step library
 
 The deep-dive into the rest of the CLI: browsing verbs, ASCII graph + export, broken-ref issues, the `.sm` annotation consent prompt, and validating links to folders outside the scan scope. `pace: auto-advance` (walk straight into the next chapter's Announcement once one is marked done) and `preflight: seed` with the `prologue-built` snapshot: it self-seeds its own copy of the Part 0 demo fixture, so it works even if the campaign already replaced that fixture with the portfolio (see SKILL.md §Entering a part, the `cli` case). Shared conventions (tone, provider detection / substitution, the `> ` rendering rule, the per-step cycle) live in `_core.md`; do not restate them here.
 

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

@@ -18,14 +18,13 @@ description: |
 
 # check-links
 
-Runs as the last gate before the site goes out. Reads each page under
-the given root, follows every internal link, and reports the ones that
-point at a file that does not exist.
+The last gate before the site goes out.
 
 ## Steps
-1. Read every page under `root`.
-2. Collect the internal links from each page.
-3. Report any link whose target is missing.
+1. List every HTML file under `public/`.
+2. For each page, collect its internal links (every `href` to `/` or to a `.html` file).
+3. Check the target exists under `public/` (treat `/` as `public/index.html`).
+4. Report any link whose target is missing; if none, report "0 broken links".
 ```
 
 Tell the tester:
@@ -63,9 +62,9 @@ description: |
 The one command you run when the site is ready to go out.
 
 ## Steps
-1. Run /check-links on the generated pages first.
-2. If anything needs a fix, brief @content-editor on it.
-3. Follow the [deploy runbook](../../docs/DEPLOY.md) to ship.
+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:
@@ -107,7 +106,7 @@ Apply both edits with `Edit` (do not rewrite the files).
 - When the site is ready to go out, run /publish.
 ```
 
-**Edit `.claude/agents/content-editor.md`**: add this line to the body, right after the "Turns a short brief..." paragraph (substitute `<provider_dir>` per `_core.md`):
+**Edit `.claude/agents/content-editor.md`**: add this line at the end of the body, after the `Rules:` line (substitute `<provider_dir>` per `_core.md`):
 
 ```markdown
 Every page follows the [style guide](../../docs/STYLE.md).