prizmkit 1.1.47 → 1.1.48

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.1.47",
-  "bundledAt": "2026-05-21T00:55:32.225Z",
-  "bundledFrom": "59d8ec1"
+  "frameworkVersion": "1.1.48",
+  "bundledAt": "2026-05-21T01:37:14.355Z",
+  "bundledFrom": "a20d996"
 }

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.47",
+  "version": "1.1.48",
   "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

@@ -112,23 +112,30 @@ Detect user intent from their message, then follow the corresponding workflow:
      --action status 2>/dev/null
    ```
 
-4. **Ask execution mode** (first user decision):
+4. **Ask execution mode** (first user decision — SEPARATE `AskUserQuestion` call):
 
-   Present the three modes and ask the user to choose:
-   - **(1) Foreground** (recommended) — pipeline runs in the current session via `run-bugfix.sh run`. Visible output and direct error feedback.
-   - **(2) Background daemon** — pipeline runs fully detached via `launch-bugfix-daemon.sh`. Survives AI CLI session closure.
-   - **(3) Manual** — display the final assembled commands only. Do not execute anything. User runs them on their own.
+   ⛔ **This MUST be its own standalone `AskUserQuestion` call.** Do NOT combine execution mode with step 5 config questions. The execution mode question is asked ALONE, user responds, THEN you proceed to step 5.
 
-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.
+   Use `AskUserQuestion` with exactly 1 question:
 
-   ⛔ **HARD STOP**: You MUST call `AskUserQuestion` with the questions below and WAIT for the user's response. You MUST NOT:
+   **Question 1 — Execution mode** (multiSelect: false):
+   - Foreground (Recommended) — pipeline runs in the current session via `run-bugfix.sh run`. Visible output and direct error feedback.
+   - Background daemon — pipeline runs fully detached via `launch-bugfix-daemon.sh`. Survives AI CLI session closure.
+   - Manual — display the final assembled commands only. Do not execute anything. User runs them on their own.
+
+   ⚠️ STOP HERE and wait for user response before continuing to step 5.
+
+5. **Ask configuration options** ⚠️ MANDATORY INTERACTIVE STEP — applies to ALL execution modes (Foreground, Background, AND Manual). This is a SEPARATE `AskUserQuestion` call from step 4. You MUST ask the user to configure options and WAIT for their response BEFORE proceeding to step 6.
+
+   ⛔ **HARD STOP**: You MUST call `AskUserQuestion` with the 4 questions below and WAIT for the user's response. You MUST NOT:
+   - Combine step 4 and step 5 into one `AskUserQuestion` call (this is the most common violation — execution mode MUST be asked separately in step 4)
    - 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.
+   If you find yourself writing the final command before the user has answered these 4 questions, STOP — you are violating this rule.
 
-   Use `AskUserQuestion` to present the following configuration choices. Each question is a separate selectable option:
+   Use `AskUserQuestion` to present ALL 4 configuration choices (the full 4-question budget goes to config, NOT shared with execution mode):
 
    **Question 1 — Verbose logging** (multiSelect: false):
    - On (default) — Detailed AI session logs including tool calls and subagent activity

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

@@ -129,23 +129,30 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    If `global_context.database` is absent and no features mention database keywords, the script skips DB checks automatically.
 
-5. **Ask execution mode** (first user decision):
+5. **Ask execution mode** (first user decision — SEPARATE `AskUserQuestion` call):
 
-   Present the three modes and ask the user to choose:
-   - **(1) Foreground** (recommended) — pipeline runs in the current session via `run-feature.sh run`. Visible output and direct error feedback.
-   - **(2) Background daemon** — pipeline runs fully detached via `launch-feature-daemon.sh`. Survives AI CLI session closure.
-   - **(3) Manual** — display the final assembled commands only. Do not execute anything. User runs them on their own.
+   ⛔ **This MUST be its own standalone `AskUserQuestion` call.** Do NOT combine execution mode with step 6 config questions. The execution mode question is asked ALONE, user responds, THEN you proceed to step 6.
 
-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.
+   Use `AskUserQuestion` with exactly 1 question:
+
+   **Question 1 — Execution mode** (multiSelect: false):
+   - Foreground (Recommended) — pipeline runs in the current session via `run-feature.sh run`. Visible output and direct error feedback.
+   - Background daemon — pipeline runs fully detached via `launch-feature-daemon.sh`. Survives AI CLI session closure.
+   - Manual — display the final assembled commands only. Do not execute anything. User runs them on their own.
+
+   ⚠️ STOP HERE and wait for user response before continuing to step 6.
+
+6. **Ask configuration options** ⚠️ MANDATORY INTERACTIVE STEP — applies to ALL execution modes (Foreground, Background, AND Manual). This is a SEPARATE `AskUserQuestion` call from step 5. You MUST ask the user to configure options and WAIT for their response BEFORE proceeding to step 7.
 
    ⛔ **HARD STOP**: You MUST call `AskUserQuestion` with the 4 questions below and WAIT for the user's response. You MUST NOT:
+   - Combine step 5 and step 6 into one `AskUserQuestion` call (this is the most common violation — execution mode MUST be asked separately in step 5)
    - 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.
+   If you find yourself writing the final command before the user has answered these 4 questions, STOP — you are violating this rule.
 
-   Use `AskUserQuestion` to present the following configuration choices. Each question is a separate selectable option:
+   Use `AskUserQuestion` to present ALL 4 configuration choices (the full 4-question budget goes to config, NOT shared with execution mode):
 
    **Question 1 — Critic review** (multiSelect: false):
    - Off (default) — Skip adversarial review
@@ -162,9 +169,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    **Question 4 — Advanced config?** (multiSelect: false):
    - No (default) — Use defaults for session timeout and failure behavior
-   - Yes — Configure session timeout and stop-on-failure options
-
-   Note: Due to the 4-question limit per `AskUserQuestion` call, Feature filter and Browser verify use their defaults (all features, auto-detect browser tools). If the user selects "Other" on any option, handle their custom input.
+   - Yes — Configure session timeout, stop-on-failure, and deploy-after-completion options
 
    Default Critic to Off unless features have `estimated_complexity: "high"` or above (in which case default to On).
 

package/bundled/skills/feature-planner/SKILL.md

@@ -284,10 +284,11 @@ A feature is **exempt** when ANY true:
 
 ### Default Behavior (Phase 4.2)
 
-1. **Auto-generate** `browser_interaction` for ALL qualifying features. Read `${SKILL_DIR}/references/browser-interaction.md` for the object format, field rules, and `tool` selection guide.
-2. **Tool selection**: Default `tool` to `"auto"`. Override to `"opencli"` when the feature involves OAuth/SSO callbacks, third-party dashboard verification, or requires real login state. Override to `"playwright-cli"` when the feature is purely local UI (forms, components, routing).
-3. **Present a summary** to the user showing which features received `browser_interaction` (including the `tool` value).
-4. **User can opt-OUT** specific features or override the `tool` choice.
+1. **Ask user for browser tool preference (Mandatory)**: Before generating any `browser_interaction` fields, use `AskUserQuestion` to ask which browser verification tool to use as the project default. Read `${SKILL_DIR}/references/browser-interaction.md` §Browser Tool Selection for the exact question format and options (`auto`/`playwright-cli`/`opencli`). Do NOT skip this step or assume a default without asking.
+2. **Auto-generate** `browser_interaction` for ALL qualifying features. Read `${SKILL_DIR}/references/browser-interaction.md` for the object format, field rules, and per-feature `tool` override logic.
+3. **Tool assignment per feature**: Use the user's chosen default. Override to `"opencli"` when the feature involves OAuth/SSO callbacks, third-party dashboard verification, or requires real login state. Override to `"playwright-cli"` when the feature is purely local UI (forms, components, routing). If user chose `"auto"`, AI assigns per-feature based on these rules.
+4. **Present a summary** to the user showing which features received `browser_interaction` (including the `tool` value for each).
+5. **User can opt-OUT** specific features or override the `tool` choice.
 
 ## Output Rules
 
@@ -323,7 +324,7 @@ Set default testing-related fields for each feature. The user can opt out.
 | medium | `true` | `1` | Single critic review |
 | low | `false` | (omitted) | Skip critic |
 
-For frontend features with `browser_interaction`, browser verification is enabled by default. The `tool` field determines which browser tool is used (default: `auto` — AI chooses at runtime between `playwright-cli` and `opencli`).
+For frontend features with `browser_interaction`, browser verification is enabled by default. The `tool` field uses the user's choice from the mandatory browser tool question in Phase 4.2 (see §Browser Interaction Planning → Default Behavior).
 
 Present a consolidated testing summary table at Phase 8, then ask for confirmation.
 

package/bundled/skills/feature-planner/references/browser-interaction.md

@@ -1,6 +1,17 @@
 # Browser Interaction Planning
 
-For web apps with UI, features that involve user-facing pages or interactive flows can optionally include a `browser_interaction` field. This enables the dev-pipeline to verify UI behavior automatically using `playwright-cli` after implementation.
+For web apps with UI, features that involve user-facing pages or interactive flows can optionally include a `browser_interaction` field. This enables the dev-pipeline to verify UI behavior automatically after implementation using the configured browser tool (`playwright-cli` or `opencli`).
+
+## Browser Tool Selection (Mandatory — Ask User)
+
+Before auto-generating `browser_interaction` for features, you MUST ask the user which browser tool to use as the project default via `AskUserQuestion`:
+
+**Question**: "Which browser verification tool should this project use by default?"
+- **Auto — AI chooses per feature (Recommended)** — `playwright-cli` for local UI, `opencli` for authenticated flows. AI decides per-feature at planning time.
+- **playwright-cli** — isolated browser instance, no login state. Best for local dev server, forms, components.
+- **opencli** — reuses Chrome's logged-in sessions via Browser Bridge. Best for OAuth, third-party dashboards, SSO.
+
+Store the user's choice as the project-level default. Individual features can still override (see Tool Selection per Feature below).
 
 ## How to Capture
 
@@ -11,6 +22,7 @@ For each qualifying feature, generate the `browser_interaction` object:
 ```json
 {
   "browser_interaction": {
+    "tool": "auto",
     "verify_steps": [
       "Verify login form renders with email and password fields",
       "Verify valid credentials redirect to dashboard",

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

@@ -130,23 +130,30 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    Wait for user confirmation before proceeding.
 
-5. **Ask execution mode** (first user decision):
+5. **Ask execution mode** (first user decision — SEPARATE `AskUserQuestion` call):
 
-   Present the three modes and ask the user to choose:
-   - **(1) Foreground** (recommended) — pipeline runs in the current session via `run-refactor.sh run`. Visible output and direct error feedback.
-   - **(2) Background daemon** — pipeline runs fully detached via `launch-refactor-daemon.sh`. Survives AI CLI session closure.
-   - **(3) Manual** — display the final assembled commands only. Do not execute anything. User runs them on their own.
+   ⛔ **This MUST be its own standalone `AskUserQuestion` call.** Do NOT combine execution mode with step 6 config questions. The execution mode question is asked ALONE, user responds, THEN you proceed to step 6.
 
-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.
+   Use `AskUserQuestion` with exactly 1 question:
 
-   ⛔ **HARD STOP**: You MUST call `AskUserQuestion` with the questions below and WAIT for the user's response. You MUST NOT:
+   **Question 1 — Execution mode** (multiSelect: false):
+   - Foreground (Recommended) — pipeline runs in the current session via `run-refactor.sh run`. Visible output and direct error feedback.
+   - Background daemon — pipeline runs fully detached via `launch-refactor-daemon.sh`. Survives AI CLI session closure.
+   - Manual — display the final assembled commands only. Do not execute anything. User runs them on their own.
+
+   ⚠️ STOP HERE and wait for user response before continuing to step 6.
+
+6. **Ask configuration options** ⚠️ MANDATORY INTERACTIVE STEP — applies to ALL execution modes (Foreground, Background, AND Manual). This is a SEPARATE `AskUserQuestion` call from step 5. You MUST ask the user to configure options and WAIT for their response BEFORE proceeding to step 7.
+
+   ⛔ **HARD STOP**: You MUST call `AskUserQuestion` with the 4 questions below and WAIT for the user's response. You MUST NOT:
+   - Combine step 5 and step 6 into one `AskUserQuestion` call (this is the most common violation — execution mode MUST be asked separately in step 5)
    - 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.
+   If you find yourself writing the final command before the user has answered these 4 questions, STOP — you are violating this rule.
 
-   Use `AskUserQuestion` to present the following configuration choices. Each question is a separate selectable option:
+   Use `AskUserQuestion` to present ALL 4 configuration choices (the full 4-question budget goes to config, NOT shared with execution mode):
 
    **Question 1 — Verbose logging** (multiSelect: false):
    - On (default) — Detailed AI session logs including tool calls and subagent activity

package/package.json

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