What problem does it solve? Cloud agent containers get reclaimed and rolled back, silently wiping or reverting the scripts, loops, and config an agent depends on. This Skill treats the Fulcra File Store as the durable home for operational state and local disk as a cache, so agents survive machine loss without from-memory rebuilds or silent downgrades. ## Core Features & Use Cases - Stash lifecycle: Push tooling on change, pull on wake, and list stash contents via the coord-engine stash verbs, with per-file sha256 checksums and executable-bit restoration from a manifest. - Re-entrancy probes: Ordered auth, stash-existence, and local-cache probes tell a waking session exactly where to enter the restore workflow, and every step is safely re-runnable. - Fail-closed secrets guard: stash push refuses secret-shaped filenames (.env, *.key, *token*) and credential-shaped content, keeping shared team paths free of leaked tokens. - Use Case: A fleet coordinator in a rollback-prone container loses its listener loop to a filesystem revert; on the next session it runs the probes, fails the local-cache check, and restores the full bundle with one stash pull instead of rebuilding from memory. ## Quick Start Ask the agent to probe its stash state and restore any missing tooling from the Fulcra File Store before starting work.
