Dug a bit more into this, turns out ref bug #1509912 that abandon/adopt is destructive wrt the nested stacks, with no way to opt out of that behavior.
Maybe just maintaining the resources will be enough, but atm it's not looking like adopt is an easy way to maintain the entire nested stack over the update - so mangling the type/resource_definition in update.py may be required if that's what we want.
Dug a bit more into this, turns out ref bug #1509912 that abandon/adopt is destructive wrt the nested stacks, with no way to opt out of that behavior.
Maybe just maintaining the resources will be enough, but atm it's not looking like adopt is an easy way to maintain the entire nested stack over the update - so mangling the type/resource_ definition in update.py may be required if that's what we want.