Repository navigation
Conversation
…planning Add the buzz-sandbox-reaper workspace crate with its JSON configuration contract (namespaces, owners, checkpoint bucket and prefixes) and the pure lifecycle planner that turns a classified Sandbox state plus checkpoint evidence into a tombstone, hold, delete, or no-op action. The binary entry point is a placeholder until the reconcile subcommand is wired up later in the stack; the modules are covered by their unit and property tests. Signed-off-by: Tee8z <tee8z@protonmail.com>
tee8z
force-pushed
the
dev-2884-reaper-config-plan
branch
from
October 19, 2026 23:28
d3cd870 to
5c9dd4a
Compare
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Broken and orphaned Agent Sandboxes have no component that ends them. This PR adds the
buzz-sandbox-reapercrate with its configuration contract and a pure lifecycle planner. The planner turns one classified SandboxStateand its checkpointEvidenceinto at most oneAction. NoActionsetsoperatingMode: Runningor creates a Sandbox. Only an expired tombstone producesAction::Delete.src/config.rsparses the JSON file from ConfigMapsandbox-reaper-config(keyconfig.json). It refuses unknown fields and names the field that fails validation.checkpoint_bucket,checkpoint_region, and eachcheckpoint_prefix.State(frombuzz-backend-kubernetes::lifecycle)ActionIgnored(why)Ignore(why)Binding { abandoned: true }Tombstone, reasonbind-abandonedBindingIncomplete { expired: true }Tombstone, reasonbinding-failedEnding { reason }Tombstonewith the recorded reasonReplacedTombstone, reasonreplacedLost { confirmed: true }Tombstone, reasonlostCompleted, evidenceMissingorInheritedHolduntil finish time + 24 h, thenTombstone, reasoncompletedCompleted, other evidenceTombstone, reasoncompletedEnded { expired: true }DeleteNoneThe tombstone
checkpointvalue is the key forVerifiedandInherited,unconfiguredforUnconfigured, andmissingforMissing.Unavailableevidence turns anyTombstoneintoNone, so a later pass decides.Stack
Position 14 of 20 in the DEV-2884 Buzz stack. Base: #3. Next: #19.
Validation
Run in a worktree at this commit (
CARGO_TARGET_DIRshared,CARGO_BUILD_JOBS=4):cargo fmt --check: pass.cargo clippy -p buzz-sandbox-reaper --all-targets --locked -- -D warnings: pass.cargo test -p buzz-sandbox-reaper --locked: 8 passed, 0 failed. This includes the property testno_plan_resurrects_or_deletes_a_live_session.Limits
src/main.rsdeclares onlyconfigandplan, has#![allow(dead_code)], and an emptyfn main() {}. Layer 5 (reconcilesubcommand) replaces it.