Migration from Rio#

This reference explains the migration boundary for people who use Rio. Automexia and Rio are intended to run side by side without replacing a rio executable, declaring a package conflict, writing into Rio's root, or deleting Rio data.

Back up both configurations before trying the Alpha. Start with a separate configuration if you do not want automatic discovery of an existing Rio setup. The Alpha limitations remain the release's support boundary.

On v0.4 startup, if no Automexia config.toml exists, Automexia validates and imports only:

• Rio's config.toml;
• .toml files beneath Rio's themes/ directory;
• bounded installed and disabled marker files beneath the legacy automexia/extensions/ state.

Logs, caches, backups, symlinks, executable content, large marker payloads, and unknown files are not copied. Each file is staged and renamed atomically. An in-progress marker allows an interrupted migration to resume; a completion marker makes repeated starts idempotent. Existing Automexia files win conflicts. Malformed legacy configuration aborts import without installing config.toml.

The source tree is read-only from the migration's perspective. Users can remove their Rio installation later, but Automexia never does so automatically.

What migration does not do#

Migration is deliberately one-way and non-destructive. Automexia does not modify Rio's configuration, caches, logs, executable identity, or shell aliases. Existing Automexia files always win, so an established Automexia installation is never overwritten by discovery of an older Rio setup.