Zypper lock status not persisted across repository refresh

The Zypper package lock mechanism is documented to prevent automatic version changes for specified packages; however, lock status is not guaranteed to persist when repository metadata is refreshed or priority values are adjusted. When multiple repositories provide the same package, Zypper's priority resolution may select a different provider without raising a lock violation error, potentially replacing a locked version silently. This behavior raises questions about the reliability of locks as a consistent barrier across repository lifecycle operations, particularly across the Leap and Tumbleweed release series where lock semantics may differ.

Does Zypper retain active package locks when repository priorities are re-evaluated after a refresh? If a package version is locked in one repository, does a priority adjustment cause silent selection from a lower-priority provider without error? How does the lock persistence behavior differ between openSUSE Leap and Tumbleweed when repository metadata changes?