Use AWS/Hetzner only when Blacksmith is down, quota-limited, missing the needed

environment, or owned capacity is explicitly the goal.

When AWS capacity is under pressure, do not start with `class=beast`.

`beast` begins at 48xlarge instances and can burn 192 vCPU quota per request.

Use `standard` first, then `fast`, and use `large`/`beast` only when the task

truly needs that many cores or the AWS quota increase has landed.

Preferred AWS pressure-relief flow:

```sh

CRABBOX_CAPACITY_REGIONS=eu-west-1,eu-west-2,eu-central-1,us-east-1,us-west-2 \

pnpm crabbox:warmup -- --provider aws --class standard --market on-demand --idle-timeout 90m

pnpm crabbox:hydrate -- --id <cbx_id-or-slug>

pnpm crabbox:run -- --id <cbx_id-or-slug> --timing-json --shell -- "env NODE_OPTIONS=--max-old-space-size=4096 OPENCLAW_TEST_PROJECTS_PARALLEL=6 OPENCLAW_VITEST_MAX_WORKERS=1 OPENCLAW_VITEST_NO_OUTPUT_TIMEOUT_MS=900000 pnpm check:changed"

pnpm crabbox:stop -- <cbx_id-or-slug>

```

Use `--market spot` only when testing Spot behavior or saving cost matters more

than launch reliability. Use `--market on-demand` when diagnosing quota/capacity

because it removes Spot market churn from the failure.

```sh

pnpm crabbox:warmup -- --provider aws --class beast --market on-demand --idle-timeout 90m

CRABBOX_CAPACITY_REGIONS=eu-west-1,eu-west-2,eu-central-1,us-east-1,us-west-2 \

pnpm crabbox:warmup -- --provider aws --class fast --market on-demand --idle-timeout 90m

pnpm crabbox:hydrate -- --id <cbx_id-or-slug>

pnpm crabbox:run -- --id <cbx_id-or-slug> --timing-json --shell -- "env NODE_OPTIONS=--max-old-space-size=4096 OPENCLAW_TEST_PROJECTS_PARALLEL=6 OPENCLAW_VITEST_MAX_WORKERS=1 OPENCLAW_VITEST_NO_OUTPUT_TIMEOUT_MS=900000 pnpm test:changed"

pnpm crabbox:stop -- <cbx_id-or-slug>

Escalate to owned Crabbox capacity only when Blacksmith is down, quota-limited, missing the needed environment, or owned capacity is explicitly the goal:

```bash

pnpm crabbox:warmup -- --provider aws --class beast --market on-demand --idle-timeout 90m

CRABBOX_CAPACITY_REGIONS=eu-west-1,eu-west-2,eu-central-1,us-east-1,us-west-2 \

pnpm crabbox:warmup -- --provider aws --class standard --market on-demand --idle-timeout 90m

pnpm crabbox:hydrate -- --id <cbx_id-or-slug>

pnpm crabbox:run -- --id <cbx_id-or-slug> --timing-json --shell -- "env NODE_OPTIONS=--max-old-space-size=4096 OPENCLAW_TEST_PROJECTS_PARALLEL=6 OPENCLAW_VITEST_MAX_WORKERS=1 OPENCLAW_VITEST_NO_OUTPUT_TIMEOUT_MS=900000 pnpm check:changed"

pnpm crabbox:stop -- <cbx_id-or-slug>

```

Under AWS pressure, avoid `class=beast` unless the task really needs 48xlarge-class CPU. A `beast` request starts at 192 vCPUs and is the easiest way to trip regional EC2 Spot or On-Demand Standard quota. Prefer `standard` or `fast`, set multiple `CRABBOX_CAPACITY_REGIONS`, and use `--market on-demand` for capacity diagnosis so Spot market churn is not mixed into the signal.

`.crabbox.yaml` owns provider, sync, and GitHub Actions hydration defaults for owned-cloud lanes. It excludes local `.git` so the hydrated Actions checkout keeps its own remote Git metadata instead of syncing maintainer-local remotes and object stores, and it excludes local runtime/build artifacts that should never be transferred. `.github/workflows/crabbox-hydrate.yml` owns checkout, Node/pnpm setup, `origin/main` fetch, and the non-secret environment handoff for owned-cloud `crabbox run --id <cbx_id>` commands.

## Related