@sreetej510/pi-shipd-checks 0.9.13 → 0.9.15

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 +8 -3
  2. package/dist/fargate-worker.mjs +483 -483
  3. package/dist/index.js +48 -48
  4. package/package.json +1 -1
package/README.md CHANGED
@@ -34,9 +34,14 @@ The agent-callable `quality-check` tool runs `create_patches.sh` in the current
34
34
  `agent_prompt.md`, `test.patch`, and `solution.patch`, first runs a Fargate patch precheck against a clean `HEAD`, then
35
35
  fills the authenticated Shipd draft fields, runs fresh checks with a `Run` button, reruns checks marked `Stale`, skips
36
36
  current checks, starts Test Quality before Solution Quality in one browser tab, waits for any started jobs, and returns only the useful report data:
37
- `details.testQuality.coverageSuggestions`, `details.testQuality.tests` filtered to test blocks whose `concerns` array is
38
- non-empty, and the complete `details.solutionQuality.evaluation` block. Its compact UI is labeled `Quality Checks`,
39
- shows live elapsed time, and only displays test-concern count, suggestion count, code-quality score, and
37
+ `details.testQuality.verdict`, `details.testQuality.coverageSuggestions`, `details.testQuality.unfairnessCount`, and
38
+ `details.testQuality.tests` filtered to blocks whose `concerns` array is non-empty or whose `fairness` is exactly `"Not fair"`,
39
+ plus `details.solutionQuality.verdict` and its evaluation fields with `level` and `overall_feedback` removed.
40
+ Fairness-only blocks with an empty `concerns` array are marked `Not fully fair`. Test Quality is `PASS` only when both
41
+ filtered tests and coverage suggestions are empty; otherwise it is `FAIL`. Solution Quality is `PASS` only when every
42
+ reported score equals its corresponding `max_score`; otherwise it is `FAIL`. Neither quality result includes `completed` or
43
+ `skipped`. Its compact UI is labeled `Quality Checks`, shows live elapsed time, and only displays the unfairness count
44
+ (including concern blocks), suggestion count, code-quality score, and
40
45
  comprehensiveness score. It takes no parameters. It uses one fresh headless browser tab at a time: it closes the
41
46
  browser after starting the needed jobs, checks after 5 minutes, then reopens every 90 seconds until those jobs finish, with no
42
47
  client-side overall timeout. If