@sreetej510/pi-shipd-checks 0.9.0 → 0.9.2

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.
Files changed (4) hide show
  1. package/README.md +2 -2
  2. package/dist/fargate-worker.mjs +373 -371
  3. package/dist/index.js +1 -1
  4. package/package.json +1 -1
package/README.md CHANGED
@@ -158,8 +158,8 @@ enabled project list is stored alongside the other settings in `~/.pi/agent/chec
158
158
 
159
159
  The patch precheck applies `test.patch`, requires `./test.sh base` to pass, requires every `./test.sh new` testcase to
160
160
  fail or error individually (with no suite-level error) before `solution.patch`, then requires both base and new suites to
161
- pass after the solution patch. A failed precheck aborts before Shipd is opened and includes the Linux platform, phase, exit code,
162
- JUnit counts, and failed/errored test names in the tool error.
161
+ pass after the solution patch. A failed precheck aborts before Shipd is opened and includes the Linux platform, a human-readable phase,
162
+ and failed/errored test names in the tool error.
163
163
 
164
164
  The `gap-finder` and `solution-precheck` tools are read-only and return repair recommendations; the caller changes the
165
165
  tests, prompt, or solution. Invoke them only when the user asks, never in parallel, and run repeated requests