D1: Promote forge bootc#15 (composefs stable) now, or gate it on the upgrade fixes? #237

Blocks: #160

bootc#2516 fixes switch/upgrade on the default image-builder disk layout. Declaring stable while that is broken invites bug reports, and #2516 is small and already in review. The re-approval itself costs one click and should happen either way.

Q: Re-approve forge bootc#15 ("Declare the backend stable") at 7fbd35ec and promote it now, or gate it on the switch/upgrade fixes?

Options:
A) Promote only after bootc#2516 (GRUB + separate /boot) merges, so image-builder disks are not "stable but broken on upgrade".
B) Re-approve and promote now. It already scopes the upgrade claims to what CI covers; bootc#2516 and bootc#2515 land in parallel.
C) Hold until tracker#7 (upgrade-path CI) is also in.

Recommended: A, because of the reasons above.

Answer with a comment on this issue: an option's letter alone on the first line (e.g. B), optionally followed by your own text, or just text. Only comments by the cgwalters login count.

Unblocks:

• composefs: Declare the backend stable bootc#15
• Epic: Help cgwalters maintain his FOSS: ostree, composefs, bootc and friends #160
• stabilizing composefs cgwalters-bot/praxis-credential-broker#2
• bootc: composefs switch/upgrade fails with GRUB and a separate /boot partition #35
• bootc CI: cover composefs upgrade paths (bridge test, Fedora upgrade, btrfs) #7
• bootc: extend test-49 bridge to a >=1.16.4 stager (stages V1 directly) #19
• docs: Add composefs integration plan cgwalters/bootc#1
• rhel-bootc-examples: composefs stable branch on c10s + bootc git main, image-builder containerdisk #33

Generated-by: https://github.com/cgwalters/#llms