bertrand 0.14.0 → 0.14.1

package/dist/bertrand.js

@@ -1367,9 +1367,9 @@ After every response, you MUST call AskUserQuestion. This is a continuous loop \
 
 If the user's most recent answer to AskUserQuestion was "Done for now" (or contains it), this turn is the FINAL turn. Respond briefly to acknowledge and do NOT call AskUserQuestion again \u2014 the loop is over.
 
-Every option must be a concrete, actionable next step. No filler like "Have questions?" or "Want to learn more?" \u2014 if clarification is needed, phrase it as a specific action: "Discuss tradeoffs of X vs Y".
+Each question must encapsulate the moment \u2014 name the specific decision, tradeoff, or next step being asked about. Avoid generic phrasing like "What next?", "How should we proceed?", or "What would you like to do?". A reader who sees only the question (no recap, no preceding text) should understand what is being decided. Prefer "Which gap should we tackle first \u2014 bundle analysis, end-to-end dry-run, or registry?" over "What's next?"
 
-Every AskUserQuestion call MUST use multiSelect: true. No exceptions. Single-select fires on Enter with no confirmation, which causes accidental selections when a block gains focus. multiSelect requires explicit confirmation before submitting.
+Every option must be a concrete, actionable next step. No filler like "Have questions?" or "Want to learn more?" \u2014 if clarification is needed, phrase it as a specific action: "Discuss tradeoffs of X vs Y".
 
 Before each AskUserQuestion call, emit a \`<recap>...</recap>\` block in your text output. Use markdown \u2014 a short bullet list is usually the most scannable shape; a single short paragraph is fine when the turn was one cohesive thing. Keep it concise. The recap covers what happened since the previous AskUserQuestion (or session start) \u2014 what you found, decided, or did. Write the gist for someone reading the session timeline, not a process log. The dashboard renders these between AskUserQuestion events; do not use this tag for any other purpose.
 `;
@@ -1379,14 +1379,25 @@ var init_template = () => {};
 function buildContract(sessionName, ...contextLayers) {
   const base = template_default.replace("{sessionName}", sessionName);
   const layers = contextLayers.map((c) => c.trim()).filter((c) => c.length > 0);
-  if (layers.length === 0)
-    return base;
-  return base + `
+  const middle = layers.length === 0 ? "" : `
 
 ` + layers.join(`
 
 `);
+  return base + middle + `
+
+` + TRAILING_CRITICAL_RULES;
 }
+var TRAILING_CRITICAL_RULES = `## CRITICAL RULE \u2014 applies to every AskUserQuestion call
+
+Every AskUserQuestion call MUST set \`multiSelect: true\` on every question. No exceptions.
+
+The AskUserQuestion tool schema describes multiSelect as "allow multiple answers to be selected instead of just one." **Ignore that framing.** In bertrand, multiSelect is a UX-safety mechanism, not a cardinality signal \u2014 single-select submits on Enter the moment a question block gains focus, causing accidental selections. multiSelect requires explicit confirmation before submitting.
+
+Apply this rule even when options are mutually exclusive (e.g., "Which library: A, B, C, or D?"). The mechanic is about preventing accidental submissions, not about how many answers the user picks.
+
+WRONG: \`{ "multiSelect": false, "options": [...] }\`
+RIGHT: \`{ "multiSelect": true,  "options": [...] }\``;
 var init_template2 = __esm(() => {
   init_template();
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bertrand",
-  "version": "0.14.0",
+  "version": "0.14.1",
   "publishConfig": {
     "access": "public"
   },