@skyf0xx/hedgehog 5.1.5 → 5.1.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyf0xx/hedgehog",
-  "version": "5.1.5",
+  "version": "5.1.7",
   "description": "Install the Hedgehog build discipline (agents + skills) into a repo, for Claude Code, Cursor, or Gemini CLI.",
   "type": "module",
   "repository": {
@@ -16,7 +16,8 @@
   "scripts": {
     "check": "node scripts/check.mjs",
     "repro": "node --experimental-sqlite repro/run-all.mjs",
-    "release": "npm version patch -m \"chore: bump version to %s\""
+    "release": "npm version patch -m \"chore: bump version to %s\"",
+    "release:plugin": "node scripts/bump-plugin-version.mjs"
   },
   "files": [
     "bin",

package/src/agents/tweaker.md

@@ -211,30 +211,6 @@ discipline as `.hedgehog/BMAD/`. A later related incident is its own new
 4. **Repeat step 3** for as many tweaks as the user has, one at a time —
    don't batch unrelated tweaks into one commit.
 
-## Self-test
-
-- Job 2 ran at most once for this build — but within that run, every
-  distinct real pattern the friction log showed, and every distinct
-  feedback item the user actually gave, got its own suggested issue, not
-  just the single clearest one.
-- The user was directly asked for feedback, separate from the friction
-  log — job 2 didn't skip straight to filing friction issues without
-  asking.
-- Entries (or feedback items) that trace to the same underlying gap were
-  grouped into one issue, not filed as duplicates.
-- Shown content is literal/final and correctly labeled — never a
-  summary, never altered post-approval, and never created without an
-  explicit approval on that specific issue's exact shown content.
-- Every tweak is its own commit, scoped to what the user actually asked
-  for — no drive-by refactor riding along on a color change.
-- A request that's actually new scope was routed onward — to `planner`'s
-  Re-entry pass on a module axis, or to the Correction Protocol's
-  post-build entry otherwise — not built here, and the user was told the
-  build is extendable, not that the request was refused.
-- The `ROADMAP.md`/contributing mention happened at most once for this
-  build, stayed to one sentence, and wasn't repeated or pressed after a
-  "no" or silence.
-
 ## Constraints
 
 - Never create a GitHub issue against the user's own project repo — job

package/src/hosts/capabilities.mjs

@@ -22,12 +22,6 @@ export const AGENT_CAPABILITY = {
   'pwa-eng': 'full',
   tweaker: 'full',
 
-  // Author artifacts, but never run commands.
-  'landing-headline-writer': 'no-bash',
-  'landing-sequencer': 'no-bash',
-  'landing-strategist': 'no-bash',
-  'landing-systems': 'no-bash',
-
   // Inspect and report; the verification command (and, for the Polish
   // Loop reviewers, the build/screenshot/interaction commands) is theirs
   // to run.
@@ -35,9 +29,6 @@ export const AGENT_CAPABILITY = {
   'landing-visual-reviewer': 'readonly-bash',
   'landing-ux-reviewer': 'readonly-bash',
 
-  // Inspect and report only.
-  'landing-critic': 'readonly',
-
   // Write its rationale artifact, nothing else.
   'ux-planner': 'write-only',
 };

package/src/skills/hedgehog-contributing/SKILL.md

@@ -117,14 +117,3 @@ back-and-forth to extract the facts.
    (`Addresses the "<item name>" item in ROADMAP.md`, or `Fixes #<n>`).
 7. **Report the PR URL** `gh` returns and stop — don't merge, don't push
    further commits without being asked.
-
-## Self-test
-
-- The change happened in a Hedgehog repo clone, never inside the user's own
-  project directory.
-- The PR is scoped to one agent, one skill, one template, or one host —
-  not a bundle of unrelated changes.
-- The install smoke test actually ran and actually confirmed the specific
-  change, not just that `init` exits zero.
-- Commit messages and the PR title follow Conventional Commits.
-- Nothing was merged or force-pushed without the user explicitly asking.