LLM/moltbot
1
0
Fork 0
mirror of https://github.com/moltbot/moltbot.git synced 2026-05-13 15:47:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(ci): document blacksmith outage fallback

Browse Source
This commit is contained in:
Vincent Koc
2026-05-06 15:20:48 -07:00
parent 6c9a848dd3
commit 75f7f30209
2 changed files with 27 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
.agents/skills/crabbox/SKILL.md
View File

@@ -229,6 +229,21 @@ Raw Blacksmith footguns:
- Treat `blacksmith testbox list` as cleanup diagnostics, not a shared reusable
queue.
Blacksmith queue/outage mode:
```sh
blacksmith --version
blacksmith testbox list --all
blacksmith testbox status --id <tbx_id>
```
If the CLI can list/status boxes but new warmups stay `queued` with no IP or
Actions run URL after a couple of minutes, treat it as Blacksmith provider,
org-limit, billing, or queue pressure. Stop the queued ids you created and do
not warm more boxes into the same stalled queue. Check the Blacksmith dashboard,
billing, and org limits out-of-band, then use Owned Cloud Fallback below for
maintainer proof.
Escalate to owned AWS/Hetzner only when Blacksmith is down, quota-limited,
missing the needed environment, or owned capacity is the explicit goal. Use the
Owned Cloud Fallback section below.
@@ -262,6 +277,9 @@ Important Blacksmith footguns:
- Always run from repo root. The CLI syncs the current directory.
- Raw commit SHAs are not reliable `warmup --ref` refs; use a branch or tag.
- If `blacksmith testbox list --all` works but warmups stay `queued`, this is
not a Crabbox bug. Stop the queued ids and switch to owned AWS/Hetzner instead
of retrying.
- If auth is missing and browser auth is acceptable:
```sh

10
docs/ci.md
View File

@@ -553,7 +553,8 @@ pnpm crabbox:run -- --provider blacksmith-testbox \
Read the final JSON summary. The useful fields are `provider`, `leaseId`, `syncDelegated`, `exitCode`, `commandMs`, and `totalMs`. One-shot Blacksmith-backed Crabbox runs should stop the Testbox automatically; if a run is interrupted or cleanup is unclear, inspect live boxes and stop only the boxes you created:
```bash
blacksmith testbox list
blacksmith testbox list --all
blacksmith testbox status --id <tbx_id>
blacksmith testbox stop --id <tbx_id>
```
@@ -572,6 +573,13 @@ blacksmith testbox run --id <tbx_id> "env CI=1 NODE_OPTIONS=--max-old-space-size
blacksmith testbox stop --id <tbx_id>
```
If `blacksmith testbox list --all` and `blacksmith testbox status` work but new
warmups sit `queued` with no IP or Actions run URL after a couple of minutes,
treat it as Blacksmith provider, queue, billing, or org-limit pressure. Stop the
queued ids you created, avoid starting more Testboxes, and move the proof to the
owned Crabbox capacity path below while someone checks the Blacksmith dashboard,
billing, and org limits.
Escalate to owned Crabbox capacity only when Blacksmith is down, quota-limited, missing the needed environment, or owned capacity is explicitly the goal:
```bash