@sreetej510/pi-shipd-checks 0.10.10 → 0.10.11
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 +0 -10
- package/dist/fargate-worker.mjs +612 -612
- package/dist/index.js +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -146,7 +146,6 @@ On-Demand fallback. Spot interruptions are retried according to `fargate.maxRetr
|
|
|
146
146
|
}
|
|
147
147
|
}
|
|
148
148
|
```
|
|
149
|
-
|
|
150
149
|
`cluster`, `subnetIds`, and `securityGroupId` are optional when a default VPC is available.
|
|
151
150
|
With `adaptiveResourceProfile: true`, solver-gap runs use `resourceProfile` initially and adapt
|
|
152
151
|
on later runs (unless `projectProfiles` already overrides the repository). They upgrade when
|
|
@@ -161,15 +160,6 @@ On-Demand fallback. Spot interruptions are retried according to `fargate.maxRetr
|
|
|
161
160
|
`/checks --solver-gap-finder`. Projects need `Dockerfile`, `agent_prompt.md`,
|
|
162
161
|
`solution.patch`, `test.patch`, and `test.sh`.
|
|
163
162
|
|
|
164
|
-
For a Command Code subscription model, install the provider in the local pi if needed
|
|
165
|
-
(`pi install npm:pi-commandcode-provider`), then authenticate it with `/login` (**Use a
|
|
166
|
-
subscription** → **Command Code**) and make sure the plan includes Provider API access. Select a
|
|
167
|
-
`commandcode/...` solver model. The standalone Fargate worker bundles the pinned
|
|
168
|
-
`pi-commandcode-provider` package and registers it before starting solver sessions; installing a
|
|
169
|
-
separate Command Code CLI or npm package in the task image is not required. The task needs
|
|
170
|
-
outbound HTTPS access to the Command Code API. The runner uploads only the selected provider
|
|
171
|
-
credential from the local pi auth state for the task; never put the credential in project files.
|
|
172
|
-
|
|
173
163
|
Use `/analyze:on` and `/analyze:off` to control the gap-finder and solution-precheck tools per project, like HPC. The
|
|
174
164
|
enabled project list is stored alongside the other settings in `~/.pi/agent/checks-config.json`.
|
|
175
165
|
|