Bamboo Specs: moving a UI-managed plan to repository-managed configuration

Goal: Move an existing manually configured Bamboo plan to Bamboo Specs management while preserving its current triggers, artifacts, and deployment settings.

Constraint: Bamboo Specs treats the committed specification repository as the source of truth, making the Bamboo UI a view rather than an independent source for that plan. Whether a detected spec change is applied automatically, held for review, or requires approval depends on the Bamboo edition and version; there is no universal auto-apply guarantee across releases. Reverting to UI-only management may not restore prior UI changes unless they were exported or recorded separately.

Does Bamboo apply a detected Specs change automatically or hold it for review in the target version? Which existing UI-only settings are preserved, replaced, or lost during the transition? Can the plan return to UI-only management without losing the pre-spec configuration?