@pikku/skills 0.12.19 → 0.12.21

package/skills/pikku-scenario/SKILL.md

@@ -367,7 +367,7 @@ string the generated step map is keyed by — the file name, and every helper in
 are English in every project regardless of who the product is for or what
 language the team speaks. There is no setting that changes this.
 
-**Prose follows `locale` in `pikku.config.json`** (default `en`). That is a
+**Prose follows `metaLocale` in `pikku.config.json`** (default `en`). That is a
 step's `description` and `template`, a feature's `name` and `description`, a
 scenario's `title`, and the positional step names passed to
 `scenario.given/when/then`. Read the field before you write any of them.
@@ -378,7 +378,7 @@ language. The report is the deliverable, and it is read by the team; the
 identifier is an API, and it is read by the toolchain.
 
 ```typescript
-// pikku.config.json: { "locale": "de" }
+// pikku.config.json: { "metaLocale": "de" }
 export const buysAnApple = pikkuScenarioStep<{ qty: number }, { orderId: string }>({
   name: 'buysAnApple',          // identifier — English, always
   description: 'kauft einen Apfel',  // prose — follows locale
@@ -392,19 +392,19 @@ export const buysAnApple = pikkuScenarioStep<{ qty: number }, { orderId: string
 Note what does **not** change: `placeOrder` is still `placeOrder`, and the file
 is still `apple.scenario.ts`.
 
-A product with a non-English UI is not on its own a reason to set `locale` — that
+A product with a non-English UI is not on its own a reason to set `metaLocale` — that
 is the app's language, not the team's. Ask, or leave it `en`.
 
-**Where a non-`en` `locale` still shows English, today.** The reporter composes a
+**Where a non-`en` `metaLocale` still shows English, today.** The reporter composes a
 sentence as `<Keyword> the <actor> <template>` (`composeStepProse`), and both the
 keyword and the article `the` are English literals. The Console translates the
 Given/When/Then keywords into its own UI language; the CLI reporter does not, and
-nothing translates `the`. So `locale: "de"` gives you German step prose inside an
+nothing translates `the`. So `metaLocale: "de"` gives you German step prose inside an
 English frame — `Given the shopper kauft 1 Äpfel`. Write templates that read
 acceptably in that frame rather than trying to defeat it. A second gap: where a
 function or scenario declares no `title`, the Console falls back to splitting the
 **identifier** into an English-looking label (`toEnglishName`), so under a
-non-`en` `locale` meta is worth authoring rather than leaving to the fallback.
+non-`en` `metaLocale` meta is worth authoring rather than leaving to the fallback.
 
 ### `then` bindings are witnesses, not alternatives
 
@@ -606,7 +606,7 @@ await page.getByRole('button', { name: t('jobs_apply_submit'), exact: true }).cl
 
 - Type off `messages/<baseLocale>.json`, **not** the generated Paraglide output — `i18n/paraglide/` is build output, so typing against it makes the tests unbuildable until the app has been built. The JSON is the tracked source.
 - Fall back to the base locale for a key a locale has not translated. That is what Paraglide does at run time, so a helper that throws instead would disagree with the screen the test is looking at.
-- This is not only about locators. A copy literal passed to a **project helper** (`pick('Where would you like to work?', …)`) reaches the DOM the same way, and so does a pane name quoted back in a failure message. `pikku fabric validate` scans every string in a `*.steps.ts` / `*.scenario.ts` against the base catalogue and errors on any verbatim match, wherever it sits.
+- This is not only about locators. A copy literal passed to a **project helper** (`pick('Where would you like to work?', …)`) reaches the DOM the same way, and so does a pane name quoted back in a failure message. `pikku fabric validate` scans every string in a `*.steps.ts` / `*.scenario.ts` against the base catalogue and errors on any verbatim match, wherever it sits — except comments, and the `name` / `description` / `template` declared directly on a `pikkuFeature`, `pikkuScenario` or `pikkuScenarioStep`, which are Console meta written in the project's `locale` rather than app copy.
 - A regex locator (`{ name: /^Next$/i }`) hides the literal but not the problem. `{ name: t('key'), exact: true }` is both stricter and locale-correct.
 - Strings the catalogue does not own — a test id, a fixture filename, a seeded value — stay literal. The catalogue is the test for whether something is copy.
 
@@ -709,11 +709,12 @@ frontend gets a one-click "Sign in as …" switcher over the **same** list, and
 app can be reviewed as each kind of user without anyone knowing a seed password.
 
 The sandbox dev server bakes both halves into the frontend from the declared
-personas: `VITE_DEV_ACTORS` (the JSON actor list) and
-`VITE_SCENARIO_ACTOR_SECRET`. Neither is set in a production build, so the
-control renders nothing there — but gate the reads on your bundler's dev flag
-anyway (`import.meta.env.DEV ? … : undefined`) so the secret never reaches a
-production bundle in the first place.
+personas: `VITE_DEV_ACTORS` (the JSON actor list) and `VITE_DEV_ACTOR_SECRETS`
+(`{ email: credential }`, one per persona — `SCENARIO_ACTOR_SECRET` itself never
+goes in a bundle; see **pikku-better-auth**). Neither var is set in a production
+build, so the control renders nothing there — but gate the reads on your
+bundler's dev flag anyway (`import.meta.env.DEV ? … : undefined`) so no
+credential reaches a production bundle in the first place.
 
 Do not hand-roll the switcher: `useDevActors()` (`pikku-react`, a separate install) is the logic and
 `<DevActorSwitcher />` from `@pikku/mantine/dev` is a ready rendering of it.
@@ -833,7 +834,7 @@ Services are plain objects — a Pikku function is pure business logic, so a moc
 | Assuming a clean database                           | There is no state reset — it may be a staging server. Scope what you create.                                                |
 | `sleep()` before asserting                          | Use `expectEventually`.                                                                                                     |
 | A step named `clicksAddToBasket` / `opensThePage`   | That is an action, not an intent. Name the step for what the actor wanted; put the clicking in a utility.                   |
-| A step named `kauftEinenApfel` / a `vorgang` table   | Identifiers are English in every project. The German belongs in `description` / `template`, and only when `pikku.config.json` sets `locale`.  |
+| A step named `kauftEinenApfel` / a `vorgang` table   | Identifiers are English in every project. The German belongs in `description` / `template`, and only when `pikku.config.json` sets `metaLocale`.  |
 | A browser step that assumes it is already on a page | It can then only run mid-flow. Arrive first — check the URL, navigate if needed.                                            |
 | `getByLabel('Full Name')` in a translated app        | Passes only in the base locale, and a copy edit breaks it as an unexplained timeout. Locate by message key.                 |
 | A `browser` binding guarding `if (!browser)`        | The binding guarantees it. The guard hides the real error, which is a missing actor (`PKU677`).                             |