OpenRC and runit: Interoperability question on migrating service packages

Goal

In an Artix Linux installation that initially uses OpenRC, an administrator wants to switch to runit while keeping existing services operational.

Constraints and Uncertainty

Artix packages are split by init suffixes (e.g., cronie-openrc vs. cronie-runit). Mixing packages from different init families is unsupported, and there is no documented in‑place migration path. Systemd‑dependent services such as elogind or seatd may behave differently under each supervisor. The repository layout places Artix’s own repos before any Arch repos, which affects package resolution during the transition.

Specific Questions

• Is there an officially supported method to convert OpenRC service scripts into runit service units, or must services be re‑installed with the runit‑specific packages?
• Can a system simultaneously install both -openrc and -runit service packages, or does Artix require a purge of one init family before the other can be used?
• How does Artix handle systemd‑dependent components (e.g., logind) when switching from OpenRC to runit, and what fallback mechanisms are recommended?