@pikku/skills 0.12.56 → 0.12.58

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pikku/skills",
3
- "version": "0.12.56",
3
+ "version": "0.12.58",
4
4
  "repository": {
5
5
  "type": "git",
6
6
  "url": "git+https://github.com/pikkujs/pikku.git",
@@ -64,7 +64,9 @@ to learn a dependency is vulnerable; use `update` to move Pikku itself.
64
64
  - Coverage is the nearest package.json walking up from the project root, plus
65
65
  every workspace it declares — a monorepo updates in one pass. All four
66
66
  dependency fields are read, `peerDependencies` included, so an addon's own
67
- declared peer range moves with it.
67
+ declared peer range moves with it. `overrides` and `resolutions` move too —
68
+ an override left behind pins the old version over the new range. A nested
69
+ override (an object, not a version) is left alone.
68
70
 
69
71
  Statuses, per dependency: `outdated` (the range floor is behind latest — this is
70
72
  what `--update` writes), `stale-install` (the range already admits latest but
@@ -31,13 +31,13 @@ installGroups: [core]
31
31
  This skill covers writing and running scenarios end to end. Five topics are one level down, and
32
32
  each says when to open it:
33
33
 
34
- | Read | For |
35
- | -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
36
- | `references/steps.md` | Authoring a `pikkuScenarioStep` — intent, witnesses, what a step is given |
37
- | `references/browser.md` | Browser bindings, and locating by message key in a translated app |
34
+ | Read | For |
35
+ | -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
36
+ | `references/steps.md` | Authoring a `pikkuScenarioStep` — intent, witnesses, what a step is given |
37
+ | `references/browser.md` | Browser bindings, and locating by message key in a translated app |
38
38
  | `references/virtual-users.md` | Virtual users vs virtual users, `defineVirtualUsers`, upstream credentials for virtual users, and human sign-in as a virtual user |
39
- | `references/coverage.md` | Live coverage, filling it, and unit tests for pure logic |
40
- | `references/virtual-user-run.md` | Running a model-driven virtual user against a stage |
39
+ | `references/coverage.md` | Live coverage, filling it, and unit tests for pure logic |
40
+ | `references/virtual-user-run.md` | Running a model-driven virtual user against a stage |
41
41
 
42
42
  ## What a scenario is
43
43
 
@@ -321,6 +321,7 @@ pikku scenario run local --spawn --exclude-tags ai-live
321
321
  | `--api-url` / `--app-url` | Override the environment's URLs — for a target that only exists at run time |
322
322
  | `--trace` | Keep every stack frame on failure (default shows only the project's own) |
323
323
  | `--coverage` | Reset/snapshot server coverage per scenario |
324
+ | `--run-id <id>` | Record the run under this id rather than a fresh one, so a caller can follow it |
324
325
 
325
326
  Output is `PASS <name> (<ms>) → <output>` / `FAIL <name> (<ms>): <error>`, then `N/M scenarios passed against '<env>'`. A scenario inside a feature is named `<Feature> › <scenario> <data>`.
326
327