@sreetej510/pi-shipd-checks 0.11.4 → 0.11.7

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 +3 -2
  2. package/dist/fargate-worker.mjs +2187 -1728
  3. package/dist/index.js +85 -95
  4. package/package.json +4 -4
package/README.md CHANGED
@@ -37,8 +37,9 @@ or correctness evidence. The adapter is experimental and was trained on all 519
37
37
  assigned to EVAL and HOLDOUT; treat all outputs as unapproved drafts.
38
38
 
39
39
  The agent-callable `quality-check` tool runs `create_patches.sh` in the current working directory and reads
40
- `agent_prompt.md`, `test.patch`, and `solution.patch`. It fills the authenticated Shipd draft fields and computes a SHA-256
41
- of the exact prompt content. The last passing prompt hash is stored as a custom entry in the current chat session. If the
40
+ `agent_prompt.md`, `test.patch`, and `solution.patch`. Before checking or running Prompt Quality, it uploads all three
41
+ contents to the authenticated Shipd draft fields and waits for the editor update to settle. It computes a SHA-256 of the
42
+ exact prompt content. The last passing prompt hash is stored as a custom entry in the current chat session. If the
42
43
  hash matches, it skips the Shipd Prompt Quality check entirely and reports a cached `PASS`; if it differs or is absent, it
43
44
  checks the refreshed status after filling the fields and runs only when the check is stale or has a `Run` button. Otherwise it
44
45
  uses the current report. A new hash is saved only after Prompt Quality passes. On failure, only `promptQuality` is returned; there are no Test/Solution results or `stoppedReason`.