credentialSecret compatibility boundary: restoring Node-RED flows without the original secret
Assuming a recent Node-RED runtime, migrating an instance between environments or restoring from backup may leave flows containing encrypted credentials generated under a different credentialSecret. The runtime does not validate during restore whether those encrypted values can be decrypted with the currently configured secret, so credential nodes appear pre