Viability of "persistent" functionality for live-boot

I noticed that chimera has brought forward the Debian live-boot persistence functionality that can be configured via persistence.conf on the appropriately labeled drive and when the proper boot argument is added.

I recognize that the goal here is to be able to sync with upstream so I'm not sure if persistent mode is actually meant to be enabled (and more importantly used) in Chimera or if that is a relic of inheriting from upstream.

1. If persistence is a goal, it should probably be documented somewhere (and/or linked to the appropriate upstream docs, like above) and there are some bugs (at least one, see below)
2. If persistence is not a goal, perhaps shortcutting out or disabling the actual loading of the persistent drive/configuration should likely be done

Today, you can absolutely perform a persistent live iso chimera boot but there is at least one bug (I wasn't trying to test this, I was just futzing around with a personal project), the anon user will be re-added (on next boot) if the user is deleted (and/or the password would be changed if you changed it). I didn't do much more analysis as I was just looking around but there may be other problems - likely some of the chimera-specific operations could step on other persistent operations a user could perform that would be undone by some of the hook commands.

[q66]

it's ostensibly supposed to work but i don't really care much for testing or documenting it or whatever, i'm not really sure how useful it is in practice if at all

if someone finds it useful i'm fine with bugfixes and whatever, but it's not something i intend to "support"