instabox 0.8.9 → 0.8.10

package/cli/SHA256SUMS

@@ -1,6 +1,6 @@
-5e836cac82c6deb332a1a7e230eb893102f96f7386ddd2faef1570a97c6a9442  instabox-darwin-amd64
-6b8d80437459810252cf29a21169a2aca1fd80577b540d9275f89425383c5964  instabox-darwin-arm64
-b9ae345cb4c57e2641156f8c9c1524920ea061352134f45b8be23a75b1176097  instabox-linux-amd64
-2fe98aec8a624e0a34dc5d8da833ae8dbd1ee7def514bcc7ee11bd5a289ae087  instabox-linux-arm64
-d9fd1d411eff160bc59ab860f9e440f83c633f55e49544c7b34346a514cda2d1  instabox-windows-amd64.exe
-f20fafc12184fed0da993461e045ff08bb2fdacc599d3a6d300736f3bfe8e647  instabox-windows-arm64.exe
+18d4f64cfc257bb332c6fd9d8906da2ba33e4d8d198a4967f27b3627b362a973  instabox-darwin-amd64
+caa66d800e41b806b49839b5d24352c692bc66df7c664ac4c8be37df9cddd78d  instabox-darwin-arm64
+f76fbb432d06b7291fe697ad76b3bd53dce2a4c445a4cde1e22145d5eafa1238  instabox-linux-amd64
+4fe5191be15a8eeabafe7b8ca5d4e5118e7329cd3bc9ad0a00c95e28d364dca0  instabox-linux-arm64
+2780378439b6d9520dd566037f2fe3ec7e20120a29193807ebff7443cd2a687f  instabox-windows-amd64.exe
+bcbe37f6429089ee42665f1ac8be15f1849229985c64fea2234506b564ca8a3d  instabox-windows-arm64.exe

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "instabox",
-  "version": "0.8.9",
+  "version": "0.8.10",
   "description": "A cloud box for your coding agent, the instabox CLI and its agent skills in one command: npx instabox@latest",
   "type": "module",
   "bin": {

package/skills/instabox/SKILL.md

@@ -142,14 +142,21 @@ instabox webhooks events                       # the event types
 
 ## CI (GitHub Actions)
 
-- A clean box for each run, or you are setting CI up for the user: a GitHub-hosted job runs the tests with `instabox run`, which creates a box, uploads the checkout, runs the command, deletes the box and exits with the command's code.
-- Out of GitHub Actions minutes, or moving existing jobs over: keep one box as a self-hosted GitHub runner, and the workflows use `runs-on: [self-hosted, instabox]`.
+When the user asks to run their CI on instabox, set up `runs-on: instabox-medium` in their repo, end to end. Each job then runs on a fresh Ubuntu 24.04 box (like `ubuntu-latest`) that is deleted when the job ends.
+
+1. Get OWNER/REPO: `gh repo view --json owner,name,visibility --jq '.owner.login+"/"+.name+" "+.visibility'`. Jobs of a public repository are refused; say so and stop if it's public. Then run `instabox ci` (with `--org ORG` for a workspace): if it says GitHub Actions jobs aren't open on this account yet, use the CLI way below instead.
+2. Send the user the App link, https://dashboard.instabox.sh/auth/github-app/install (for a workspace other than their personal one, add `?org=ORG_ID` from `instabox workspace ls`; linking takes an owner or admin of it). Ask them to install the App on OWNER, give it access to REPO and link it to the workspace, and wait until they say it's done. You can't do this step for them.
+3. Change `runs-on:` of the jobs to move to `instabox-medium` (4 vCPU / 8 GiB), or `instabox-small` (2 / 4) or `instabox-large` (8 / 16) where the plan has them (the free plan runs `instabox-medium` only; any other `instabox` label, `instabox` alone included, is refused). Leave the steps alone; the jobs' secrets stay GitHub Actions secrets, as the box gets none of the user's instabox secrets.
+4. Show the user the diff and push only with their OK.
+5. Check the first run: `gh run watch`, and `instabox ci` (with `--org ORG` for a workspace) shows each job's state and why it waits or was refused. When nothing is linked, `instabox ci` says so and prints the App install link to send. A job that stays queued on GitHub with nothing in `instabox ci` means the App has no access to REPO; go back to step 2.
+
+For another CI, or a job that must stay on GitHub's runner, a step runs one command in a box with the CLI, with INSTABOX_API_KEY from a CI secret:
 
 ```sh
-instabox run --push . --timeout 10m -e CI=1 -- 'npm ci && npm test'   # in the job, with INSTABOX_API_KEY from a repository secret
+instabox run --push . --timeout 10m -e CI=1 -- 'npm ci && npm test'
 ```
 
-The workflow, the CI key, a saved snapshot to start from, the runner setup and the limits: https://instabox.sh/docs/ci.md
+Both ways, their limits and the reasons a job is refused: https://instabox.sh/docs/ci.md
 
 ## Moving work onto a box