Omar Sobh
89f5892e20
Build with clawstor cache / Cargo build (clawstor-cached) (pull_request) Failing after 4s
Ships the wire-up piece for real CI: a composite Gitea Action that wraps `claw-cargo build` with cache-outcome reporting, plus a matching workflow file that opts the clawstor repo itself into being cache-hit-tested on every push. Also docs the one-time per-runner provisioning (leaf cert, PATH install, config.toml). * `.gitea/actions/cargo-cache/action.yml` — composite Action. Inputs: workspace, profile, no-upload, parallel-restore. Outputs: cache-outcome (HIT|MISS|POPULATED|SKIPPED), fingerprint, elapsed-seconds. Runner-side config lives in `~/.config/claw-cargo/config.toml` (not in the workflow — no secrets shipped from repos). * `.gitea/workflows/build-with-cache.yml` — dogfoods the action on clawstor's own repo. `no-upload` set from event_name so PRs from forks can't poison the cache. * `docs/runner-integration.md` — one-time setup steps, sample workflow snippet, expected numbers (Pi 5: 2.79× wall, tank: 2.18×), and troubleshooting for the failures I hit in the tank and Pi pilots (bind_lan on fabric-only, missing CLI/config, rustc drift warn). Test protocol: push this branch → main triggers the workflow → the runner on tank has claw-cargo + tls + config provisioned already (2026-07-13 pilot setup) → first build should MISS + populate, subsequent build on same fingerprint should HIT.