Greptile Summary

This PR fixes plain aube update run from a workspace member so it merges results into the shared workspace-root aube-lock.yaml rather than creating a per-member lockfile, and shares that merge logic with the existing filtered-update path by extracting merge_update_graph_into_workspace_lockfile.

• write_update_lockfile is called instead of write_and_log_lockfile on the hot path; it detects whether cwd is a workspace member with shared-lockfile enabled and, if so, reads the root lockfile and delegates to the shared merge helper.
• merge_update_graph_into_workspace_lockfile now carries workspace_extra_fields with a symmetric insert/remove pair, correctly pruning stale entries when a member no longer produces that field.
• A new Bats regression test validates that aube install followed by aube up from a workspace member leaves only the root aube-lock.yaml and that the member's importer entry appears in it.

Confidence Score: 5/5

Safe to merge — the fix is well-scoped, the extraction is mechanical, and the regression test directly exercises the broken scenario.

The refactor correctly routes plain workspace-member updates to the shared root lockfile, the workspace_extra_fields pruning is symmetric (insert/remove), and the merge_filtered_update_lockfile lockfile-removal ordering is preserved. No wrong-data or stale-state paths were introduced.

No files require special attention.

Important Files Changed

_{Reviews (2): Last reviewed commit: "fix(update): prune stale workspace extra..." | Re-trigger Greptile}