@skyf0xx/hedgehog 3.0.3 → 3.0.4

package/README.md

@@ -118,11 +118,10 @@ npx @skyf0xx/hedgehog init
 Then open Claude Code and describe what you want to build.
 
 Plain `init` (no core flag) installs the agents, skills, and build graph
-only — no workspace, no framework, nothing core-specific. Planning
-intake designs an opinionated build order and stack for what you
-actually describe, then bootstrap lands that workspace for the first
-time. Don't pick `--ts-full-stack-app` or `--landing-page` by elimination
-when neither actually fits.
+that every core shares. Planning intake designs an opinionated build
+order and stack for what you actually describe, then bootstrap generates
+that workspace. Don't pick `--ts-full-stack-app` or `--landing-page` by
+elimination when neither actually fits.
 
 To update:
 

package/bin/cli.mjs

@@ -3,7 +3,7 @@
 // into the current repo, so the discipline travels with the project.
 //
 // Usage:
-//   npx @skyf0xx/hedgehog init                        no workspace yet — planner picks the core
+//   npx @skyf0xx/hedgehog init                        install; planner picks the core at intake
 //   npx @skyf0xx/hedgehog init --ts-full-stack-app     scaffold the full-stack-app core now
 //   npx @skyf0xx/hedgehog init --landing-page          scaffold the landing-page core now
 //   npx @skyf0xx/hedgehog init --force                 overwrite files that already exist
@@ -77,12 +77,12 @@ async function availableCores() {
 // and a project can only switch cores before it's bootstrapped anyway.
 //
 // `core` is `null` on a deferred install (plain `init`, no explicit
-// flag): which core applies hasn't been decided yet, so nothing
-// core-specific — no golden-core workspace, no filled CLAUDE.md section —
-// gets written speculatively. `bootstrap` lands the real workspace, for
-// whichever core `planner` picks, the first time either way. An explicit
-// flag (`--ts-full-stack-app`, `--landing-page`) is a confirmed choice,
-// not a guess, so it scaffolds immediately as before.
+// flag): the payload is the shared agents/skills/build-graph only, with
+// which core applies left for `planner` to decide. `bootstrap` lands the
+// golden-core workspace and fills the CLAUDE.md section for whichever
+// core `planner` picks — the first time either way. An explicit flag
+// (`--ts-full-stack-app`, `--landing-page`) is a confirmed choice, so it
+// scaffolds that workspace immediately, at install time.
 function plan(core) {
   const base = [
     { type: 'dir', from: 'src/agents', to: '.claude/agents' },
@@ -191,7 +191,7 @@ CLAUDE.md template and an empty build graph (${bold('.hedgehog/hedgehog.db')})
 into the repo root, so the discipline is committed alongside your code.
 
 ${bold('Usage')}
-  npx @skyf0xx/hedgehog init                      no workspace yet — planner picks the core
+  npx @skyf0xx/hedgehog init                      install; planner picks the core at intake
   npx @skyf0xx/hedgehog init --ts-full-stack-app  scaffold the full-stack-app core now
   npx @skyf0xx/hedgehog init --landing-page       scaffold the landing-page core now
   npx @skyf0xx/hedgehog init --force              overwrite existing files
@@ -217,10 +217,10 @@ off to bootstrap.
 Building something else (a CLI, library, browser extension, data
 pipeline, desktop app, etc.)? Run plain 'init' with no core flag rather
 than picking --ts-full-stack-app or --landing-page by elimination — it
-installs the agents, skills, and build graph only, nothing core-specific.
-The planner agent designs a core at planning intake (hedgehog-core-design)
-and bootstrap generates that workspace once it's confirmed. Describe the
-actual project and let Phase 0 route it.
+installs the agents, skills, and build graph, the payload every core
+shares. The planner agent designs a core at planning intake
+(hedgehog-core-design) and bootstrap generates that workspace once it's
+confirmed. Describe the actual project and let Phase 0 route it.
 
 ${bold('update')} re-copies only .claude/agents and .claude/skills from the
 installed Hedgehog version, so an already-bootstrapped project can pick up
@@ -245,7 +245,7 @@ async function init({ force, core, explicitCore }) {
 
   // Resolve the full list of writes up front so we can detect conflicts
   // before touching anything. A deferred install (no explicit core) plans
-  // against `null` — no golden-core workspace, nothing core-specific.
+  // against `null` — the shared agents/skills/build-graph payload only.
   const groups = [];
   for (const entry of plan(explicitCore ? core : null)) {
     const files = await plannedFiles(entry);
@@ -321,10 +321,9 @@ async function init({ force, core, explicitCore }) {
   } else {
     console.log(
       dim(
-        'Core: not chosen yet. Nothing core-specific landed — no workspace,\n' +
-          'no framework, no lockfile. planner decides which core applies at\n' +
-          'planning intake, then bootstrap lands that core\'s workspace for\n' +
-          'the first time.',
+        'Core: not chosen yet — this installed the agents, skills, and\n' +
+          'build graph every core shares. planner decides which core applies\n' +
+          'at planning intake, then bootstrap generates that core\'s workspace.',
       ),
     );
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyf0xx/hedgehog",
-  "version": "3.0.3",
+  "version": "3.0.4",
   "description": "Install the Hedgehog build discipline (agents + skills) into a repo.",
   "type": "module",
   "repository": {

package/src/agents/bootstrap.md

@@ -1,6 +1,6 @@
 ---
 name: bootstrap
-description: Use once per invocation, at the start of a new Hedgehog project, to land the workspace for whichever core `planner` selected at Phase 0 — the first real workspace this project gets, since `init` with no explicit core flag lands only agents/skills/the build graph, nothing core-specific. On full-stack-app, that's core (via hedgehog-bootstrap-full-stack-app-core, one pass) then exactly ONE add-on step of the hedgehog-bootstrap skill (0-3 steps depending on planning intake scope), handing off to a fresh instance of itself for the next add-on step. On landing-page, that's a single pass of hedgehog-bootstrap-landing-page-core with no add-on steps — one invocation, done. On an authored core (`.hedgehog/core.yaml` present), that's a single pass of hedgehog-bootstrap-authored-core, generating the workspace live for the stack `hedgehog-core-design` chose. Not for per-phase/per-module work — that's this core's own loop skill and its agents. Skip entirely if the core's workspace already exists (nx.json for full-stack-app, astro.config.mjs for landing-page, or the matching `feat(<id>): workspace` commit for an authored core).
+description: Use once per invocation, at the start of a new Hedgehog project, to land the workspace for whichever core `planner` selected at Phase 0 — the first real workspace this project gets, since `init` with no explicit core flag lands the shared agents/skills/build-graph payload and leaves the workspace to bootstrap. On full-stack-app, that's core (via hedgehog-bootstrap-full-stack-app-core, one pass) then exactly ONE add-on step of the hedgehog-bootstrap skill (0-3 steps depending on planning intake scope), handing off to a fresh instance of itself for the next add-on step. On landing-page, that's a single pass of hedgehog-bootstrap-landing-page-core with no add-on steps — one invocation, done. On an authored core (`.hedgehog/core.yaml` present), that's a single pass of hedgehog-bootstrap-authored-core, generating the workspace live for the stack `hedgehog-core-design` chose. Not for per-phase/per-module work — that's this core's own loop skill and its agents. Skip entirely if the core's workspace already exists (nx.json for full-stack-app, astro.config.mjs for landing-page, or the matching `feat(<id>): workspace` commit for an authored core).
 model: sonnet
 color: green
 tools: Read, Glob, Grep, Edit, Write, Bash

package/src/skills/hedgehog-core-design/SKILL.md

@@ -238,10 +238,10 @@ holds. Once confirmed and written, control returns to `planner`, which
 runs `hedgehog-planning-intake`'s Phase 1 mining against this core the
 same way it would against a shipped one, then hands off to `bootstrap`.
 
-This skill never touches the workspace itself — no `pnpm init`, no
-generator, no install. `hedgehog init` lands nothing core-specific until
-a core is chosen, so there's nothing on disk yet for this skill to
-conflict with; its job ends at the design artifacts. `bootstrap`'s
-`hedgehog-bootstrap-authored-core` is what later generates the real
-workspace for the stack chosen here — a separate step, run only once
-Phase 1 mining and Confirm & Lock have both landed.
+This skill's job ends at the design artifacts — `core.yaml` and
+`core-design.md` are text, written by editing files. `hedgehog init`
+lands the shared agents/skills/build-graph payload regardless of core, so
+the workspace this design describes is still `bootstrap`'s to generate:
+`hedgehog-bootstrap-authored-core` runs the stack's own generator and
+installs it, a separate step, once Phase 1 mining and Confirm & Lock have
+both landed.