@goodtek/vibeops 0.3.0 → 0.4.0

package/CHANGELOG.md

@@ -4,6 +4,13 @@ All notable changes to VibeOps are documented here.
 
 ## Unreleased
 
+## 0.4.0 - 2026-05-13
+
+### Changed
+
+- **Interactive plan LLM (`questionType`)**: system prompt prefers **`multi`** (checkbox, Space toggles) whenever several options can apply; reserve **`single`** for mutually exclusive choices. **`multi` vs `single` terminal behavior** is spelled out for the model.
+- **Plan JSON parsing**: if `questionType` is missing or invalid and **two or more** `options` are present, default to **`multi`** so users get multi-select instead of a hard error or accidental single-only flow.
+
 ## 0.3.0 - 2026-05-13
 
 ### Changed

package/dist/lib/plan-llm-openai.js

@@ -102,16 +102,27 @@ export function parsePlanLlmTurn(jsonText) {
     }
     if (turn === "question") {
         const message = typeof raw.message === "string" ? raw.message : "";
-        const questionType = raw.questionType;
         if (message.length === 0) {
             throw new Error('Invalid JSON: "question" turn needs non-empty "message".');
         }
-        if (questionType !== "single" && questionType !== "multi" && questionType !== "text") {
-            throw new Error('Invalid JSON: questionType must be "single", "multi", or "text".');
-        }
         const options = Array.isArray(raw.options)
             ? raw.options.filter((x) => typeof x === "string" && x.trim().length > 0)
             : [];
+        const rawQt = raw.questionType;
+        let questionType;
+        if (rawQt === "single" || rawQt === "multi" || rawQt === "text") {
+            questionType = rawQt;
+        }
+        else if (options.length >= 2) {
+            /** Model often omits or mistypes questionType — multi is the safer default when lists are offered. */
+            questionType = "multi";
+        }
+        else if (options.length === 1) {
+            questionType = "single";
+        }
+        else {
+            questionType = "text";
+        }
         return {
             turn: "question",
             message,

package/dist/lib/plan-llm-session.js

@@ -11,14 +11,15 @@ import { extractJsonObject, openAiChatCompletionJson, parsePlanLlmTurn } from ".
 import { normalizeLlmProjectBrief } from "./plan-llm-normalize.js";
 import { VERSION } from "../version.js";
 const MAX_LLM_TURNS = 48;
-const PLAN_JSON_PROTOCOL_CORE = `You are VibeOps' planning assistant. Learn about a software project through a short dialogue, infer the next best single question from the user's last answer, then produce a structured ProjectBrief.
+const PLAN_JSON_PROTOCOL_CORE = `You are VibeOps' planning assistant. Learn about a software project through a short dialogue, infer the next best question from the user's last answer, then produce a structured ProjectBrief.
 
 You MUST reply with a single JSON object only (no markdown fences). Allowed "turn" values: "question", "confirm", "done".
 
 1) While discovering:
 {"turn":"question","message":"<markdown allowed>","questionType":"single"|"multi"|"text","options":["..."]}
 - **One primary ask per turn** (see conversation rules below).
-- For "single" or "multi", include "options" (3–12 short labels) as **suggested answers only**. The terminal may show a picker (arrow keys / Space) but the user can always choose Other or type a custom reply.
+- **questionType — critical:** Prefer **"multi"** whenever more than one option can legitimately apply (e.g. target users, MVP features, integrations, deployment targets, risks, auth methods, “which concerns apply”, stacks that can combine). Use **"single"** only when choices are **mutually exclusive** (exactly one can be true: e.g. one primary package manager, one hosting model when alternatives exclude each other, a single primary language for the codebase). When in doubt, use **"multi"** so the user can toggle several options with Space.
+- For "single" or "multi", include "options" (3–12 short labels) as **suggested answers only**. **"multi"** uses a checkbox (Space toggles, Enter submits). **"single"** uses a one-line picker (Enter picks one). The user can always pick Other or type a custom reply.
 - For "text", omit "options" or use an empty array.
 
 2) When information is enough for a solid ProjectBrief and task breakdown, **before** "done", emit exactly one approval step:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@goodtek/vibeops",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "description": "Workflow rails for Cursor-based vibe coding projects.",
   "type": "module",
   "author": "VibeOps contributors",