Verified:GitHub

local-automation-runtime-upgrade

Upgrade local automation runtimes while preserving secrets, state, and configuration.

1|Updated Jan 22, 2026

Search Tags:#validation #configuration management #runtime upgrade #state preservation #local automation #template diff #GitHub project automation

Ready to run

npx skills add https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools --skill local-automation-runtime-upgrade

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: local-automation-runtime-upgrade
Source: https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools/tree/main/.cursor/skills/local-automation-runtime-upgrade
Command: npx skills add https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools --skill local-automation-runtime-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading an installed local automation runtime often risks overwriting operator-specific secrets, logs, job state, and repository checkouts, causing downtime or lost configuration.

Core Features & Use Cases

Safe template refresh: Compares the installed runtime against templates/local-automation-runtime/ and updates template-managed scripts, docs, tests, and example configs.
Local state preservation: Preserves sensitive and runtime-specific directories/files such as config.env, codex-home/, jobs/, logs/, repos/, and state/, including local validation outputs.
Controlled validation: Runs pre-upgrade verification (python3 scripts/verify_repo.py) and post-upgrade checks (unittest smokes and ./check_runtime.sh) plus harness verification when applicable.

Quick Start

Tell the runtime operator to upgrade by following the Local Automation Runtime Upgrade Flow: record current state, verify the repo, compare and copy template-managed files, preserve local-only secrets/state, migrate new config keys into config.env, refresh the image if container files changed, then run unit tests and runtime checks.

Frequently Asked Questions about local-automation-runtime-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I upgrade a local automation runtime without losing secrets and state?▼

Upgrading a local automation runtime safely requires backing up preserved assets like config.env, jobs, logs, and state directories, then selectively copying template-managed files to refresh scripts and configs without overwriting local-only data.

What is the best way to migrate new configuration keys during a runtime upgrade?▼

Migrating new configuration keys during a runtime upgrade involves comparing your current config.env against the runtime template and safely integrating newly required keys into your existing local configuration file.

How do I validate local automation behavior after applying a template diff?▼

Validating local automation behavior after a template diff requires running pre-upgrade repository verification scripts and executing post-upgrade unittest smokes plus runtime checks to ensure operational stability without resuming mutating operations.

Does a local automation runtime upgrade overwrite repository checkouts and logs?▼

A proper local automation runtime upgrade preserves repository checkouts, logs, and sensitive configuration directories by selectively applying template-managed changes instead of performing a blanket file overwrite.

When should I refresh the container image during a local automation upgrade?▼

You should refresh the container image during a local automation upgrade only when template-managed container files have changed during the template diff and copy process.

Can I resume mutating operations immediately after copying template-managed files?▼

No, after copying template-managed files and migrating new config keys, you must pass unit tests and runtime validation gates like check_runtime.sh before resuming any mutating operations to prevent downtime.