You gotta respect the tactic. Their GHA SLA for enterprise customers is based on number of workflows that fail. Workflows can't fail if you can't invoke them through commits or the API to begin with
Users who do not want to use the base Flatpaks can do so by simply basing a custom image off Cosmic. They do not inherit the ISO from us. Also could have explained what the real issue was.
flatpak-readonlyroot reads toml config to configure a custom Flatpak installation, it's not specific to bootc. The name reflects the intended use case rather than technical limitations
The main downside of this approach is the increased filesize. e.g. platform dependencies are not shared between the flatpak-readonlyroot installation and the typical flatpak installations