From a maintainability standpoint and to eventually make it easy for us to swap Centarro Claro for Gin (or beyond) we may want to extract the parts of the recipe that are related to admin UI and experience into separate recipe. Ie. admin_toolbar module and the centarro_claro admin theme should make it into its own recipe which commerce_kickstart_base depend on. We may even consider that Admin UI recipe can be selected via the installer so one can choose between Drupal CMS Admin UI vs (current) Commerce Kickstart Admin UI. That's if we want to maintain the current Kickstart Admin UI that is.
Active
5.0
Recipes
MR for changes in Commerce Kickstart Base are in https://git.drupalcode.org/project/commerce_kickstart_base/-/merge_reque...
The recipe itself can be found in https://github.com/zaporylie/commerce_recipe_admin_ui
While I put the recipe in commerce_recipe namespace I don't believe now this is a good choice. This would not be a general commerce recipe but part of kickstart ecosystem hence it should belong to the commerce_kickstart namespace.