Make Experience Builder a production dependency

Is experience builder committing to update paths for all the configuration entities etc. it provides from now on? Otherwise this seems like it will lead to breakage as soon as sites try to update to later pre-release versions of XB.

Installing this by default in all Drupal CMS sites really does feel like a bad idea. I am OK with the idea of XB being available as some kind of experimental addon recipe in Drupal CMS, but to present it as-is by default when it is very incomplete in its current state seems like over promising and under delivering, and that's before we even get to any future upgrade issues.

See 📌 Create a specialized recipe to hold the XB demo Active for a proposed solution. XB would still be a production dependency there, but not enabled by default.

#3++, because the answer to #2 is .

Then again, thanks to [#34977881], XB could indeed conceivably function as a "read-only demo" 😮 🤔

Curious to see what the Drupal CMS product owner(s) think! 😄

Relevant discussion over at 🌱 Milestone 0.2.0: the one for Drupal CMS 1.0 Active .

XB is a production dependency in our development branch now, but not our release branch. This is as it should be; it will make it into the 1.1.x release branch when the time comes :)