instabox 0.8.9 → 0.8.11

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
+b790ef7a0a0061739327a4dd72cc7ef924b58cf8340fd033426aa2d60753a59b  instabox-darwin-amd64
+2057c2ce9caf54afb785c272a5d970be78ecd85974506d273525e5e13c343396  instabox-darwin-arm64
+ffa924da20c7db0b437cd4d829d83e13ff56283cab71fa7b464992082f7131a1  instabox-linux-amd64
+116fe6e04f9102a3e9770995b4f553c79583f6317316c91f5ae623698cb4d5db  instabox-linux-arm64
+bda55c61293157f07db5068f6110038688e180d7784a84ac6012b21ef2a979d7  instabox-windows-amd64.exe
+090dd5aef606ded11d2c22c6da0d6870136e0f0b647f05ce4555a799a9c15afb  instabox-windows-arm64.exe

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "instabox",
-  "version": "0.8.9",
+  "version": "0.8.11",
   "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