Bryan Helmkamp baa2fc8b5c Keep every workspace under Petri's retention and say why ... Petri's retention decides whether a released workspace is kept or removed. Fabro's lifecycle settings decide whether a sandbox keeps running after the run and whether a delete may remove it; none asks for removal at the run's end, and the sandbox tab, `fabro cp`, the run's delete and the sandbox scenarios read the container after the run. So the mapping is `Retention::Always` for every setting, named once as `engine::RETENTION` with the reasoning, instead of a per-setting function that released a finished sandbox. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-18 18:39:58 -04:00
..
src	Keep every workspace under Petri's retention and say why	2026-09-18 18:39:58 -04:00
tests	Merge branch 'petri-integration' into petri-integration-gaps	2026-09-18 16:00:51 -04:00
build.rs	refactor: organize crates into three layers	2026-07-23 17:59:34 -04:00
Cargo.toml	Delete fabro-validate and fabro-acp; validate on Petri's check	2026-09-18 11:32:04 -04:00