Package suddenly changed to "Locked": Deployment risks?

Hello Community,

I’m working on a Creatio Cloud instance (version 8.1.3.3193) and have encountered a challenge with a user-made package.

The Situation:

• I have a user-made package that contains replacing objects for Account and Contact (from the Customer360 app).
• The package was created directly in this environment (not installed via .zip or SVN).
• This package was previously open, but has suddenly changed to a locked status. Despite the lock icon, I am still able to modify and save schemas inside it.

My Questions:

1. Will this "locked" status cause errors when transferring the package to Production via .zip export or the Assembly process? or it cannot be trasferred?
2. What is the best way to remove this lock?
3. If unlocking isn't possible, should I create a new package that depends on this locked one and try to replace the objects again? I'm concerned that a "replacement of a replacement" might cause issues with the core Customer360 functionality.

Thank you for your guidance!