prizmkit 1.1.41 → 1.1.42

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.1.41",
-  "bundledAt": "2026-04-30T09:49:08.976Z",
-  "bundledFrom": "13a2ce9"
+  "frameworkVersion": "1.1.42",
+  "bundledAt": "2026-05-08T13:51:58.092Z",
+  "bundledFrom": "02ab9e3"
 }

package/bundled/dev-pipeline/scripts/generate-bootstrap-prompt.py

@@ -631,7 +631,7 @@ SECTION_TO_SKILL = {
 # phase-commit is split into two steps
 _COMMIT_STEPS = [
     ("prizmkit-retrospective", "Retrospective", []),
-    ("prizmkit-committer", "Commit", []),
+    ("prizmkit-committer", "Commit", ["--headless"]),
 ]
 
 

package/bundled/dev-pipeline/scripts/generate-bugfix-prompt.py

@@ -450,7 +450,7 @@ BUGFIX_STEPS = [
       ".prizmkit/bugfix/{slug}/plan.md"]),
     ("prizmkit-implement", "Implement Fix", []),
     ("prizmkit-code-review", "Code Review", []),
-    ("prizmkit-committer", "Commit", []),
+    ("prizmkit-committer", "Commit", ["--headless"]),
     ("bug-report", "Generate Fix Report",
      [".prizmkit/bugfix/{slug}/fix-report.md"]),
 ]

package/bundled/dev-pipeline/scripts/generate-recovery-prompt.py

@@ -117,7 +117,7 @@ Commit the fix and finalize:
 1. Run `/prizmkit-retrospective` (structural sync only — update file counts,
    interfaces, dependencies in .prizm-docs/)
 2. Stage all changed files explicitly (NEVER use `git add -A` or `git add .`)
-3. Run `/prizmkit-committer` with commit prefix `fix(<scope>): <description>`
+3. Run `/prizmkit-committer --headless` with commit prefix `fix(<scope>): <description>`
 4. Verify working tree is clean: `git status --short`
 5. Write `fix-report.md` to `.prizmkit/bugfix/{bug_id}/fix-report.md` with:
    - Root cause summary

package/bundled/dev-pipeline/scripts/generate-refactor-prompt.py

@@ -40,7 +40,7 @@ REFACTOR_STEPS = [
     ("prizmkit-code-review", "Review — Code Review & Behavior Verification",
      [".prizmkit/refactor/{slug}/review-report.md"]),
     ("prizmkit-committer", "Commit",
-     []),
+     ["--headless"]),
     ("refactor-report", "Generate Refactor Report",
      [".prizmkit/refactor/{slug}/refactor-report.md"]),
 ]

package/bundled/dev-pipeline/templates/bootstrap-prompt.md

@@ -36,7 +36,7 @@ Infer what needs to be done from the feature context above and follow the standa
 
 6. **Retrospective**: Run `/prizmkit-retrospective` to sync `.prizm-docs/` with code changes.
 
-7. **Commit**: Run `/prizmkit-committer` to commit all changes. Do NOT push.
+7. **Commit**: Run `/prizmkit-committer --headless` to commit all changes. Do NOT push.
 
 ### Critical Rules
 

package/bundled/dev-pipeline/templates/bugfix-bootstrap-prompt.md

@@ -240,7 +240,7 @@ git add <specific-files-modified>
 git add .prizm-docs/
 ```
 
-**d.** Run `/prizmkit-committer`:
+**d.** Run `/prizmkit-committer --headless`:
    - Commit message prefix: `fix({{FIX_SCOPE}}): {{BUG_TITLE}}`
    - Include both fix code and reproduction test
    - Do NOT push

package/bundled/dev-pipeline/templates/refactor-bootstrap-prompt.md

@@ -235,7 +235,7 @@ Include browser verification approach in plan.md:
 
 1. Run `/prizmkit-retrospective` (full sync — Job 1 + Job 2) to update `.prizm-docs/` with structural changes
 
-2. Run `/prizmkit-committer` with:
+2. Run `/prizmkit-committer --headless` with:
    - Commit message: `refactor({{REFACTOR_ID}}): {{REFACTOR_TITLE}}`
    - Include all refactored files and any new/updated tests
    - Do NOT push (user will push manually)

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.41",
+  "version": "1.1.42",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",

package/bundled/skills/bugfix-pipeline-launcher/SKILL.md

@@ -121,6 +121,13 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 5. **Ask configuration options** ⚠️ MANDATORY INTERACTIVE STEP — applies to ALL execution modes (Foreground, Background, AND Manual). You MUST ask the user to configure options and WAIT for their response BEFORE proceeding to step 6. Do NOT skip this step or merge it with step 6.
 
+   ⛔ **HARD STOP**: You MUST call `AskUserQuestion` with the questions below and WAIT for the user's response. You MUST NOT:
+   - Skip this step and jump to the next step
+   - Merge this step and the next step into one response
+   - Assume default values and show the command without asking
+   - Show the command as text and ask "ready?" without presenting the options
+   If you find yourself writing the final command before the user has answered these questions, STOP — you are violating this rule.
+
    Use `AskUserQuestion` to present the following configuration choices. Each question is a separate selectable option:
 
    **Question 1 — Verbose logging** (multiSelect: false):

package/bundled/skills/feature-pipeline-launcher/SKILL.md

@@ -138,6 +138,13 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 6. **Ask configuration options** ⚠️ MANDATORY INTERACTIVE STEP — applies to ALL execution modes (Foreground, Background, AND Manual). You MUST ask the user to configure options and WAIT for their response BEFORE proceeding to step 7. Do NOT skip this step or merge it with step 7.
 
+   ⛔ **HARD STOP**: You MUST call `AskUserQuestion` with the 4 questions below and WAIT for the user's response. You MUST NOT:
+   - Skip this step and jump to step 7
+   - Merge step 6 and step 7 into one response
+   - Assume default values and show the command without asking
+   - Show the command as text and ask "ready?" without presenting the options
+   If you find yourself writing the final command before the user has answered these questions, STOP — you are violating this rule.
+
    Use `AskUserQuestion` to present the following configuration choices. Each question is a separate selectable option:
 
    **Question 1 — Critic review** (multiSelect: false):

package/bundled/skills/prizmkit-committer/SKILL.md

@@ -66,6 +66,8 @@ Ask user: "Push to remote?"
 - Yes: `git push`
 - No: Stop
 
+**Headless mode**: If the skill was invoked with `--headless` in the args (e.g., `/prizmkit-committer --headless feat(F-001): ...`), **SKIP this step entirely**. Do NOT ask the question. Do NOT push. Stop after Step 5 verification. Headless mode is used by autonomous pipeline sessions where there is no human to answer interactive prompts.
+
 ## Example
 
 **Feature commit:**

package/bundled/skills/refactor-pipeline-launcher/SKILL.md

@@ -139,6 +139,13 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 6. **Ask configuration options** ⚠️ MANDATORY INTERACTIVE STEP — applies to ALL execution modes (Foreground, Background, AND Manual). You MUST ask the user to configure options and WAIT for their response BEFORE proceeding to step 7. Do NOT skip this step or merge it with step 7.
 
+   ⛔ **HARD STOP**: You MUST call `AskUserQuestion` with the questions below and WAIT for the user's response. You MUST NOT:
+   - Skip this step and jump to step 7
+   - Merge step 6 and step 7 into one response
+   - Assume default values and show the command without asking
+   - Show the command as text and ask "ready?" without presenting the options
+   If you find yourself writing the final command before the user has answered these questions, STOP — you are violating this rule.
+
    Use `AskUserQuestion` to present the following configuration choices. Each question is a separate selectable option:
 
    **Question 1 — Verbose logging** (multiSelect: false):

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.1.41",
+  "version": "1.1.42",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {