fix(lockfile): preserve default-branch flag through lock round-trips

ArrayDumper emits `default-branch: true` into the lock for any package
that came from a default branch, and ArrayLoader reads it back to
synthesize the `9999999-dev` alias inside Locker::getLockedRepository.
Mozart was dropping the flag in two places: packagist_version_to_locked_package
ignored pv.default_branch when building the lock entry, and
locked_package_to_packagist_version hardcoded default_branch=false when
re-hydrating a lock-pinned package's metadata for partial updates. The
result was that a non-allow-listed default-branch dev package (e.g. f/f
in update-changes-url) ended up in the new lock without the marker, so
collect_stale_installed_aliases thought its `9999999-dev` alias had
been retired and emitted a spurious MarkAliasUninstalled trace.

1 files changed, 1 insertions, 8 deletions

diff --git a/crates/mozart/tests/installer.rs b/crates/mozart/tests/installer.rs
index b1c1968..78772fb 100644
--- a/crates/mozart/tests/installer.rs
+++ b/crates/mozart/tests/installer.rs
@@ -234,13 +234,6 @@ macro_rules! installer_fixture {
             run_installer_fixture(stringify!($name));
         }
     };
-    ($name:ident, ignore) => {
-        #[test]
-        #[ignore = "not implemented yet"]
-        fn $name() {
-            run_installer_fixture(stringify!($name));
-        }
-    };
 }
 
 installer_fixture!(abandoned_listed);
@@ -394,7 +387,7 @@ installer_fixture!(update_allow_list_with_dependencies_require_new);
 installer_fixture!(update_allow_list_with_dependencies_require_new_replace);
 installer_fixture!(update_allow_list_with_dependencies_require_new_replace_mutual);
 installer_fixture!(update_allow_list_with_dependency_conflict);
-installer_fixture!(update_changes_url, ignore);
+installer_fixture!(update_changes_url);
 installer_fixture!(update_dev_ignores_providers);
 installer_fixture!(update_dev_packages_updates_repo_url);
 installer_fixture!(update_dev_to_new_ref_picks_up_changes);