@pikku/skills 0.12.17 → 0.12.19

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pikku/skills",
-  "version": "0.12.17",
+  "version": "0.12.19",
   "description": "The Pikku agent skills — the instruction set coding agents read to build, wire and deploy Pikku projects",
   "author": "yasser.fadl@gmail.com",
   "license": "MIT",

package/skills/pikku-fabric/SKILL.md

@@ -322,7 +322,12 @@ Why it parked is the whole story, and it is `statusReason`, not `status`:
   accepts them for that deploy.
 - `needs_config` — a declared secret or variable has no value covering the
   stage. The CLI names them. `--auto-approve` will **not** force this through;
-  set the values (`pikku fabric secrets set <name>`) and re-attach.
+  set the values and re-attach — `pikku fabric secrets set <name>` for a
+  declared secret, `pikku fabric variables set <name> --value <v>` for a declared
+  variable. They are separate stores: a secret is sealed to the stage and cannot
+  be read back, a variable is stored plainly and can (`variables get`). `set`
+  reads the value as JSON when it parses, so `--value true` is the boolean on a
+  stage exactly as it is from `.env`, and `--value '"true"'` is the string.
 - `needs_attention` — the plan is red. Nothing to approve.
 
 `--sync` defaults to a 900s ceiling; `--timeout <seconds>` moves it. On timeout

package/skills/pikku-scenario/SKILL.md

@@ -213,14 +213,14 @@ The **feature is the run unit**: `--flows` on a scenario whose every feature ent
 
 A scenario records what someone was **trying to do**, never the keystrokes they used to do it. This is the one decision that determines whether a suite survives its first redesign, and it applies to every step name you write.
 
-| Action ladder — wrong               | Intent ladder — right                               |
-| ----------------------------------- | --------------------------------------------------- |
-| `Given opens /shop`                 | `Given the shopper is browsing the shop`            |
-| `When clicks the category filter`   | `When the shopper buys the £5 strawberry milkshake` |
-| `And clicks "Drinks"`               | `Then it is in their basket`                        |
-| `And clicks the first product card` |                                                     |
-| `And clicks Add to basket`          |                                                     |
-| `Then sees "1 item"`                |                                                     |
+| Action ladder — wrong               | Intent ladder — right                           |
+| ----------------------------------- | ----------------------------------------------- |
+| `Given opens /shop`                 | `Given shopper is browsing the shop`            |
+| `When clicks the category filter`   | `When shopper buys the £5 strawberry milkshake` |
+| `And clicks "Drinks"`               | `Then it is in their basket`                    |
+| `And clicks the first product card` |                                                 |
+| `And clicks Add to basket`          |                                                 |
+| `Then sees "1 item"`                |                                                 |
 
 Three things go wrong with the left-hand column, and all three are expensive:
 
@@ -313,7 +313,7 @@ await scenario.when(
   { name: '£5 strawberry milkshake' },
   { actor: actors.shopper }
 )
-// reporter renders: When the shopper buys the £5 strawberry milkshake  ✓  1.2s
+// reporter renders: When shopper buys the £5 strawberry milkshake  ✓  1.2s
 ```
 
 **Every intent step begins by arriving.** `ensureOnShop` is not defensive noise — it is what lets a scenario start at any step, run alone, and be reordered without touching it. It checks first and navigates only if needed, so a scenario already on the shop pays nothing. This is about the _browser's_ starting position, not the database: there is still no state reset (see above), and you still scope what you create.
@@ -489,7 +489,7 @@ await scenario.given(
   { qty: 1 },
   { actor: actors.shopper }
 )
-// reporter renders: Given the shopper buys 1 apples   ✓  412ms
+// reporter renders: Given shopper buys 1 apples   ✓  412ms
 ```
 
 Rules that bite: