@sreetej510/pi-shipd-checks 0.14.0 → 0.14.1

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 (3) hide show
  1. package/README.md +4 -2
  2. package/dist/index.js +103 -102
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -30,8 +30,10 @@ or correctness evidence. The adapter is experimental and was trained on all 519
30
30
  assigned to EVAL and HOLDOUT; treat all outputs as unapproved drafts.
31
31
 
32
32
  The agent-callable `quality-check` tool runs `create_patches.sh` in the current working directory and reads
33
- `agent_prompt.md`, `test.patch`, and `solution.patch`. Before checking or running Prompt Quality, it uploads all three
34
- contents to the authenticated Shipd draft fields and waits for the editor update to settle. It computes a SHA-256 of the
33
+ `agent_prompt.md`, `test.patch`, and `solution.patch`. Before reading any quality status, it syncs the Shipd draft: it
34
+ fills only the fields whose saved content differs from the local files, waits until Shipd's Convex backend acknowledges
35
+ every save and the header shows `Saved`, then reloads and confirms the draft matches (up to three attempts). Each page
36
+ load waits until every quality row's status has loaded, since a row without its status would read as a current report. It computes a SHA-256 of the
35
37
  exact prompt content. The last passing prompt hash is stored as a custom entry in the current chat session. If the
36
38
  hash matches, it skips the Shipd Prompt Quality check entirely and reports a cached `PASS`; if it differs or is absent, it
37
39
  checks the refreshed status after filling the fields and runs only when the check is stale or has a `Run` button. Otherwise it