Greptile Summary

Fixes a false-stale lockfile error where aube ci rejected imported npm-workspace root link: entries whose workspace packages are not listed in the root package.json. The fix collects workspace package names upfront, then skips the "manifest removed" drift check for root entries that are confirmed link: sources pointing at a known workspace package.

• check_drift_for_importer is refactored into a two-layer design: the existing public method now delegates to check_drift_for_importer_with_workspace_links, and check_drift_workspace calls the inner form directly with the computed workspace_link_names set.
• The workspace-link exemption is deliberately narrow: it only fires for the root importer (\".\"), only when the locked name appears in the workspace manifests, and only when the resolved package has LocalSource::Link(_).
• A regression test (workspace_drift_allows_root_links_for_workspace_packages) exercises the exact scenario from the bug report.

Confidence Score: 5/5

Safe to merge — the change is well-scoped, the exemption condition is tight, and removal of a workspace package from the manifests slice still triggers stale correctly.

The workspace-link exemption requires three independent conditions to all be true (root importer, name in workspace-manifest set, resolved package is a link), making accidental over-exemption very unlikely. The non-workspace check_drift path is unaffected (passes an empty HashSet). The refactoring is minimal and the regression test directly covers the reported failure scenario.

No files require special attention.

Important Files Changed

_{Reviews (1): Last reviewed commit: "fix(lockfile): preserve imported workspa..." | Re-trigger Greptile}