@sreetej510/pi-shipd-checks 0.9.11 → 0.9.13
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/README.md +3 -3
- package/dist/fargate-worker.mjs +231 -231
- package/dist/index.js +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -34,9 +34,9 @@ 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
|
|
38
|
-
|
|
39
|
-
shows live elapsed time, and only displays
|
|
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
|
|
40
40
|
comprehensiveness score. It takes no parameters. It uses one fresh headless browser tab at a time: it closes the
|
|
41
41
|
browser after starting the needed jobs, checks after 5 minutes, then reopens every 90 seconds until those jobs finish, with no
|
|
42
42
|
client-side overall timeout. If
|