generatesaas 2.3.0 → 2.4.0

package/dist/skill/content/SKILL.md

@@ -154,7 +154,7 @@ it stays complete). Read `newOptions` from `.generatesaas/staging.json`. **If it
 empty, skip this step entirely.**
 
 Otherwise, present each option so the user can decide whether to adopt it. Each entry has
-`{ key, label, hint, default, impact, requiresLabel? }`. For each one:
+`{ key, label, hint, default, impact, choices?, requiresLabel? }`. For each one:
 
 ```
 ### New since your version: {label}
@@ -172,14 +172,32 @@ it is a large surface you didn't originally choose" or "Safe to adopt - it is pu
 > 2. **Adopt it** - turn this feature on
 ```
 
+**An entry with `choices` is not a yes/no.** It takes one of several values, so the two-way block
+above cannot express it - offer the values as a numbered pick list instead, one line per choice,
+with the entry's `default` marked as the current behavior:
+
+```
+**Default:** `{default}` (your project's current behavior is unchanged).
+**My recommendation:** {your recommendation, naming one of the choices}
+
+> **Which would you like?**
+> 1. **`{choices[0]}`** {"(current)" on the one equal to default}
+> 2. **`{choices[1]}`**
+> 3. **`{choices[2]}`** ...one line per choice, however many there are
+```
+
 **Ask the user about every new option, in every mode - including Automatic.** Surfacing a new
 feature is exactly the kind of decision the update must never assume. Give your recommendation,
 but the user decides.
 
 **Applying the decisions:**
 
-1. For each option the user **adopts**, write its enabling value into `.generatesaas/manifest.json`
-   (e.g. set `"desktop": true`). The manifest is the single shaping input.
+1. For each option the user **adopts**, write the value they picked into
+   `.generatesaas/manifest.json` under the entry's `key`. For an option with no `choices` that value
+   is `true` (e.g. set `"desktop": true`); for one with `choices` it is the choice they named,
+   verbatim (e.g. set `"errorTracking": "sentry"`). Never write `true` for an option that has
+   `choices` - the CLI refuses any value outside them and stages nothing at all. The manifest is the
+   single shaping input.
 2. **If the user adopted at least one option, re-stage once** so re-shaping produces the
    feature's files. Re-run the CLI (append `auto` if you are in Automatic mode, so the staged
    metadata keeps the unattended signal):

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "generatesaas",
-  "version": "2.3.0",
+  "version": "2.4.0",
   "type": "module",
   "description": "CLI for scaffolding and managing GenerateSaaS projects",
   "license": "UNLICENSED",