What problem does it solve? Restoring a system to a known-good state often risks overwriting user data, creating mixed-version states, or skipping verification. This Skill enforces a bounded, evidence-backed restoration process that protects persistent data and proves the restore actually worked. ## Core Features & Use Cases - Bounded Restore Execution: Declares exact replace/retain boundaries before actuation, covering application payload, configuration, runtime, services, or full install trees. - Data Protection by Default: Preserves persistent user data and failed-state evidence unless explicitly authorized otherwise. - Post-Restore Verification: Verifies target identity, representative behavior, and protected-data survival after the switch. - Use Case: After a failed deployment corrupts a service, use this Skill to stage the last verified build, restore configuration in dependency order, and confirm both identity and function before declaring recovery complete. ## Quick Start Restore the service to the last verified rollback target while protecting user data and verifying the result.