fabro/lib
Bryan Helmkamp 06f9cb8361
Delete fabro-sandbox's clone and push chain
The engine prepares every run's checkout, so fabro's clone
orchestration, the per-checkout GitHub credentials, the run-branch
setup, the push retries, and the push policies had no production
caller. RepoWorkspace::plan still validates the clone request and now
refuses one that asks for a clone; initialize creates an empty
workspace root. SandboxWorkspaceLayout and snapshot_info stay: the run
record projection in sandbox_spec.rs reads them. The run tool
regression keeps its assertion (a child targets the parent's pushed
run branch) over a plain git fixture instead of the deleted setup. The
Docker, Daytona, and Daytona-wire clone layout tests go: they proved
only the legacy clone. fabro-sandbox drops base64, uuid, fabro-proc,
serde, strum, and sandbox-driver-daytona-config; chrono is test-only.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-19 09:18:29 -04:00
..
apps Delete fabro-sandbox's clone and push chain 2026-09-19 09:18:29 -04:00
components Delete fabro-sandbox's clone and push chain 2026-09-19 09:18:29 -04:00
foundation Merge remote-tracking branch 'origin/main' into petri-integration 2026-09-19 06:37:02 -04:00
packages/fabro-api-client Regenerate the provider client model after the codecs merge 2026-09-19 06:49:05 -04:00