Bryan Helmkamp d24042ba64 Put the driver's sandbox status on the API instead of a projection ... Fabro projected the driver's status into its own state enum, resource, network, and timestamp types for the run sandbox and inventory endpoints, losing the provider's state string, the network policy, the sandbox kind, and the driver's own vocabulary along the way. The API now carries the driver's SandboxStatus itself: SandboxDetails is fabro's run record beside the status, SandboxInfo is the provider beside the status, and the OpenAPI schema describes the driver's types (state, resources in the units the driver reports, the network policy, the sandbox kind, workspace ownership) which fabro-api reuses through with_replacement with round trip tests proving identity and JSON parity. The projection types and their conversion go; the web sandbox page and summary panel read the status directly, and the TypeScript client is regenerated. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-11 13:07:00 -06:00
..
client-sdks.mdx	refactor: organize crates into three layers	2026-07-23 17:59:34 -04:00
fabro-api.yaml	Put the driver's sandbox status on the API instead of a projection	2026-09-11 13:07:00 -06:00
overview.mdx	docs: refresh product documentation	2026-08-24 09:53:09 -04:00