Bryan Helmkamp 07c52b07ca Depend on the sandbox-driver crates by git revision ... Fabro pins the sandbox-driver workspace the same way it pins the Daytona SDK: every crate at one commit on main. The bundled Host, Docker, and Daytona provider libraries link in-process, and the protocol crate reaches third-party providers over stdio. Nothing uses the crates yet; the following commits move fabro onto them one layer at a time. The driver pins tracing-subscriber exactly, so the lockfile settles on that version for the whole workspace. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-09 14:18:58 -06:00
..
apps	Remove expired startup secret migrations	2026-09-05 14:05:48 -04:00
components	Depend on the sandbox-driver crates by git revision	2026-09-09 14:18:58 -06:00
foundation	Rebuild conclusion stage summaries from run events	2026-09-05 11:44:23 -04:00
packages/fabro-api-client	Remove unsupported workflow playground	2026-09-03 12:04:35 -04:00