Reset only resources created by this workspace
A cleanup command deletes every container with a generic project label, including another checkout's database.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Safe automation · Resource ownership · Destructive-operation design
Estimated field mix
- DevOps60%
- Security40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional support portal requires a database, cache, object store, and mail catcher. Setup lives in personal notes, reset scripts sometimes target shared resources, and offline work fails after package caches are cleared. Build a local-only development contract with synthetic data; no shared staging system or production credentials are supplied.
Setup prerequisites
- Environment variables
- Service health
- Database migrations
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Workspace identity is stable, explicit, and included on owned resources
- Reset previews exact absolute targets and service identities
- Foreign and ambiguous resources are refused
Implementation constraints
- The command operates only on generated local fixtures and requires an explicit reset flag.
Verification to include
- Preview and reset one isolated fixture workspace.
- Add a second workspace and an ambiguous unlabeled resource, then prove both survive.
Deliverables
- Scoped reset command and cross-workspace safety tests
Rollout and recovery
Ship preview-only first and document recovery limits.
Value of the work
For the engineer: Practice developer-environment automation, safe reset boundaries, portability, and diagnostic quality.
For the team: Reduce onboarding and support cost while making local dependencies and destructive operations explicit.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.