@sjawhar/pi-legion 18.49.0 → 18.49.1

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/dist/legion.js CHANGED
@@ -14337,7 +14337,7 @@ import { logger as logger3 } from "@oh-my-pi/pi-utils";
14337
14337
  // package.json
14338
14338
  var package_default = {
14339
14339
  name: "@sjawhar/pi-legion",
14340
- version: "18.49.0",
14340
+ version: "18.49.1",
14341
14341
  license: "Apache-2.0",
14342
14342
  type: "module",
14343
14343
  omp: {
@@ -135,8 +135,18 @@ issue pod, on the issue's own disk, by the issue's roles together.
135
135
 
136
136
  **The worked case, and the one a role actually meets: the Dispatch e2e stack.** A change to
137
137
  `packages/dispatch` is proved in the pod by driving the specs it touches, one spec a command
138
- (`bun run e2e -- e2e/<one spec file>`); the whole browser suite runs in CI's `dispatch` job on the
139
- pull request. One spec needs the same stack as all of them: a Postgres with pgvector. On a digest
138
+ (`bun run e2e -- e2e/<one spec file>`) — except a wall-clock spec, whose three projects are out
139
+ of the default selection, so its command names its project:
140
+ `bun run e2e -- --project=chromium-alone e2e/heavy-bodies.e2e.ts --workers=1`.
141
+ `packages/dispatch/AGENTS.md` carries both of those as the three commands to copy as they stand.
142
+ CI's `dispatch-browser` job runs one of two lanes, and neither is the whole suite on every pull
143
+ request. An unlabelled pull request gets the pull-request lane: `chromium`, `iphone`, `stub`
144
+ and `stub-phone`, held to the rows tagged `@pr`. The full lane - every project over every row,
145
+ the three `-alone` ones among them - runs on a pull request labelled `full-ci`, on the merge
146
+ queue and nightly, and the `alone` job that holds the wall-clock rows is gated on it
147
+ (`if: inputs.lane == 'full'` under `alone:` in `.github/workflows/dispatch-browser.yaml`), so no
148
+ unlabelled pull request runs a wall-clock row at all. One spec needs
149
+ the same stack as all of them: a Postgres with pgvector. On a digest
140
150
  carrying `legion-testpg`, use the pod's own server
141
151
  (`skill://legion-worker/references/tools.md#the-database-your-tests-use`) and
142
152
  unpack nothing. On a digest without it, the way
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/pi-legion",
3
- "version": "18.49.0",
3
+ "version": "18.49.1",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "omp": {