Each first-boot step writes a marker only after it succeeds, so a failed step retries on the next network connection instead of being skipped. Deleting a marker makes that step run again.
Home of the unprivileged sobarch-build user that builds vendored packages. Per-run build trees are temporary directories under /var/tmp/sobarch-aur-sync-*.
System files sobarch manages
These are written by first boot and are not reconciled like your dotfiles, so edit them directly if you need to.
/etc/nftables.conf, the firewall ruleset.
/etc/ssh/sshd_config.d/10-sobarch-no-root-login.conf, only when SSH is enabled.
/etc/polkit-1/rules.d/46-sobarch-power.rules, the power-action rule.
/etc/pam.d/ly and /etc/pam.d/ly-autologin, edited to use pam_oo7.so instead of pam_gnome_keyring.so.
/etc/pacman.d/hooks/sobarch-aur-sync.hook, the sync trigger, owned by the sobarch-scripts package.
/etc/NetworkManager/dispatcher.d/90-sobarch-firstboot, which starts the network-dependent first-boot units, also owned by sobarch-scripts.
/etc/systemd/system/sobarch-firstboot-*.service, the first-boot units, written by the installer with your username filled in.
/etc/xdg/mimeapps.list, the system-wide default applications, owned by sobarch-skel; ~/.config/mimeapps.list overrides it.
/usr/local/share/applications/vesktop.desktop, the launcher override that routes Vesktop through its integrity wrapper, present only while both packages are installed.
On a laptop, tlp.service and tlp-pd.service are enabled and systemd-rfkill is masked; see the FAQ.