When you no longer need the examples, remove the resources created only for them while keeping the service's intended configuration and existing access in place. If a request had an uncertain result, inspect the affected resource before retrying it.
- Stop further activity. Let the selected job or pipeline reach a known terminal state, or cancel only its recorded numeric ID. Preserve its source SHA, ref, status, job list, and trace before removing a branch. Follow Practise stopping, investigating, and recovering for active work.
- Close temporary credentials first. Revoke each exact personal, project, or group access token created for the practice. Read it back as revoked and inactive; a successful local logout or a deleted environment variable doesn't establish closure. Never print or retain the secret value.
- Remove temporary access and execution state. Delete only the recorded temporary branch after its current head equals the recorded exercise SHA. Remove only memberships, job-token allowlist entries, variables, or runner assignments introduced by the practice, then read the affected direct and effective state again. Use Diagnose and recover containment for the job-token and runner boundary.
- Restore trusted configuration deliberately. Compare the current policy, branch rule, CI configuration, or repository file with the recorded starting revision. Restore only the reviewed change through its normal protected path, then read the effective configuration back. Use Diagnose and recover policy authority for policy links and ownership, and Restore a reviewed repository or policy revision for file recovery. Keep the protection in place throughout cleanup.
- Check the affected result again. Confirm the intended default-branch SHA, policy relationship, allowlists, and file digests. Where the practice reached a runtime, also check the selected environment's current deployment, artifact identity, health, and required behavior. A restored repository alone doesn't establish a restored service.
- Preserve operating records. Keep the configuration revisions, release approvals and relevant pipeline, deployment and incident records under your retention policy. Retain a usable operating baseline explains which profile, pipeline, finding and review records to keep.
- Assign retained resources. If a practice project, runner, artifact, or environment remains for review, keep it private where applicable and record its owner and review or deletion date. A review date isn't an automatic deletion promise. Delete it later only after preserving required records and verifying its exact identity.
Use Change or remove a scanner profile for temporary scanning configuration and Roll back with a new signed decision for the local application. Confirm that temporary resources are gone and retained services are in their intended state. Work with the responsible owners to resolve any remaining external credentials, sessions, deployments, or affected data.