@skyf0xx/hedgehog 4.3.4 → 4.3.6

package/bin/cli.mjs

@@ -548,31 +548,22 @@ async function init({ force, core, explicitCore, host = DEFAULT_HOST, hostOnly =
     );
     console.log(dim('     instead of polling tightly or narrating the wait.'));
     console.log(`  2. ${bold('git add -A && git commit -m "chore: install Hedgehog"')}`);
-    console.log(
-      `  3. Start a ${bold('new')} ${HOSTS[host].label} session and describe what you want to build.`,
-    );
+    console.log(`  3. Describe what you want to build.`);
   } else {
     console.log(`  1. ${bold('git add -A && git commit -m "chore: install Hedgehog"')}`);
-    console.log(
-      `  2. Start a ${bold('new')} ${HOSTS[host].label} session and describe what you want to build.`,
-    );
-  }
-  console.log(
-    dim(
-      `     The ${bold('planner')} agent runs planning intake, then hands off to bootstrap.`,
-    ),
-  );
-  // A host enumerates its agents once, at session start. This install just
-  // wrote them mid-session, so in THIS session they are not dispatchable —
-  // and the failure is worse than a plain error: names like `planner` and
-  // `reviewer` often resolve to the user's own unrelated global agents,
-  // silently running a different discipline instead of erroring.
+    console.log(`  2. Describe what you want to build.`);
+  }
+  // Hand off by path, not by name. Reading the file works on every host in
+  // the session that ran this install — no restart, no dependence on whether
+  // the harness re-scans its agent directory, and no chance of a bare
+  // `planner` resolving to an unrelated global agent of the same name.
+  const agents = HOSTS[host].agentsDir;
+  const skills = HOSTS[host].skillsDir;
   console.log(
     dim(
-      `     A new session matters: ${HOSTS[host].label} lists its agents at startup, so the\n` +
-        '     ones just installed are not dispatchable in the session that ran this.\n' +
-        '     If a handoff must happen here anyway, read the agent file and follow it\n' +
-        '     inline rather than dispatching to a name that may resolve elsewhere.',
+      `     Read ${bold(`${agents}/planner.md`)} and follow it — it runs planning\n` +
+        `     intake (${skills}/hedgehog-planning-intake/SKILL.md), then hands\n` +
+        `     off to ${agents}/bootstrap.md.`,
     ),
   );
   console.log();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyf0xx/hedgehog",
-  "version": "4.3.4",
+  "version": "4.3.6",
   "description": "Install the Hedgehog build discipline (agents + skills) into a repo, for Claude Code, Cursor, or Gemini CLI.",
   "type": "module",
   "repository": {

package/src/agents/planner.md

@@ -87,7 +87,12 @@ and the scaffolded workspace.
   real app beyond a single page. If in doubt between this and
   landing-page because the project has *both* a marketing page and a
   real app behind it, this is `full-stack-app` — the page becomes routes
-  inside `apps/web`, not a separate project.
+  inside `apps/web`, not a separate project. Data that gets stored is
+  this core, at any size: a todo list, a notes app, a tracker of any
+  kind. Never talk the user down to browser-local storage, an in-memory
+  array, or a single-file page because the app sounds small, and never
+  offer that as a quicker start — the core ships a real database, and
+  reaching for less is the drift this discipline exists to prevent.
 - **`landing-page`** — the description is a marketing/announcement/
   waitlist/portfolio page (or a small handful of such pages) with no
   persistent domain data of its own. A page that only collects an email

package/src/templates/CLAUDE.md

@@ -38,20 +38,19 @@ Lock and the `bootstrap` handoff. This same rule holds at every later
 handoff to a newly-installed agent or skill in this session: read its
 file, don't assume its content.
 
-Dispatch is the part that can't be worked around by reading. A host lists
-its agents once, at session start, and this install wrote them after
-that — so in this session `bootstrap` and the rest may not be
-dispatchable at all. Two symptoms, and neither means a broken install:
-an error naming the available agents without Hedgehog's in it, or —
-worse, because it has no symptom — a name like `planner` or `reviewer`
-silently resolving to the user's own unrelated global agent and running a
-different discipline. If either happens, read the agent's file from
-`.claude/agents/` and follow it inline here; each one is self-contained.
-Everything delegates normally from the next session on, which is why the
-installer's next step is to start a fresh one. Don't re-explain the discipline or summarize this
-file; the greeting is one line, not a tour. Skip this entirely once the
-placeholder is filled in — every later session starts with `hedgehog
-status`, not a greeting.
+The build continues in this session — nothing here needs a restart. Hosts
+differ in whether they pick up agents written mid-session, so prefer
+reading an agent's file from `.claude/agents/` and following it inline;
+each one is self-contained, and that path works everywhere. Reading also
+avoids the quiet failure of dispatch by name, where `planner` or
+`reviewer` resolves to the user's own unrelated global agent and runs a
+different discipline with no symptom. If a dispatch does error with a
+list of available agents that omits Hedgehog's, that is the same case —
+read the file and carry on.
+
+Don't re-explain the discipline or summarize this file; the greeting is
+one line, not a tour. Skip this entirely once the placeholder is filled
+in — every later session starts with `hedgehog status`, not a greeting.
 
 ## How to work here
 
@@ -86,6 +85,16 @@ loop) is what a generic skill pack has no notion of, and running one
 alongside Hedgehog's own skills produces work that bypasses the very
 discipline this file describes.
 
+**Build through the loop, including when the work looks too small to need
+it.** A task that seems like a quick edit is not a reason to skip the
+graph, the step sequence, or the gate — scope grows, and the shortcut is
+what turns a small change into debt the next step has to work around.
+Don't propose going around the discipline to save a step, and don't treat
+a user's impatience as license to: say what the loop's next step is and
+take it. Where a rule genuinely conflicts with what the user is asking
+for, name the conflict and let them decide — never resolve it by quietly
+taking the faster path.
+
 {{CORE_SECTION}}
 
 ## Consuming the graph