@sreetej510/pi-shipd-checks 0.8.2 → 0.8.3
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 +1 -1
- package/dist/index.js +39 -39
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -38,7 +38,7 @@ The agent-callable `quality-check` tool runs `create_patches.sh` in the current
|
|
|
38
38
|
shows live elapsed time, and only displays unfair-test count, suggestion count, code-quality score, and
|
|
39
39
|
comprehensiveness score. It takes no parameters. It uses one fresh headless browser tab at a time: it closes the
|
|
40
40
|
browser after starting the stale jobs, checks after 5 minutes, then reopens every 90 seconds until those jobs finish. If
|
|
41
|
-
no check is stale, it uses
|
|
41
|
+
no check is stale, it uses existing reports without starting a job; a fresh `Run` row is reported as skipped. Each
|
|
42
42
|
browser context blocks images, fonts, and media to reduce memory use. It does not click the final orange
|
|
43
43
|
challenge-submit button. Authentication comes from `SHIPD_STORAGE_STATE` or the saved state created by
|
|
44
44
|
`/shipd:auth`. `/shipd:auth` launches the installed browser as a normal visible process and attaches over local CDP,
|