GeezerVison

Assisted-by: Claude Code:claude-opus-5-5

When a package has more than one pnpm or vlt peer-variant store copy,
apply and rollback already patch (or restore) every copy, but they only
reported what happened to the first one. A run that fixed only a twin
copy said "already patched" (applied: 0), and a rollback that restored
only a twin said "already original" (rolledBack: 0).

Apply and rollback now share one store-copy fan-out and one fold, which
merges each copy's per-file records into the result under the copy's
on-disk path. The two private folds, which had drifted on which
advisories they kept, are gone; both directions now carry only the
ownership advisory from a copy.

Fixes #756, #772.

Assisted-by: Claude Code:claude-opus-5-5

End-to-end regression for #756 through the real binary, on hand-built
pnpm and vlt store layouts: apply that patches only a twin copy reports
it as applied, and rollback that restores only a twin counts it as
rolled back. Documents the copy-qualified file paths in CLI_CONTRACT.

Assisted-by: Claude Code:claude-opus-5-5

cursor Bot left a comment •

edited

Loading

Uh oh!

There was an error while loading. Please reload this page.

Under --force, a store twin missing a patched file skips it and still
succeeds. The fold already dropped that copy's "all files skipped" note,
but it carried the skipped file's NotFound record, so a package whose
primary copy was already patched was reported as "applied" with no
files instead of "already patched". Those records now stay with the
copy, like its note.

Assisted-by: Claude Code:claude-opus-5-5

cursor Bot left a comment •

edited

Loading

Uh oh!

There was an error while loading. Please reload this page.

Conflict in tests/apply/in_process_npm_multicopy.rs: both sides appended
new tests at the end of the file (this branch's pnpm twin-reporting test,
main's #601 bundled-copy and #626 first-party-link tests). Kept both.

Co-Authored-By: Claude <[email protected]>

#605 taught the name-keyed npm resolver to probe bundled store
trees, so it now finds aliased copies (node_modules/lp) and a nested
host's store peers itself. Two vex_consumed tests from #738 assumed
that set never held aliases, so main's CI went red after both merged.

The tests now feed the alias-free set explicitly to keep covering
alias expansion, and also check the resolver's own set reaches the
same copies with no duplicates. No production code changes.

Assisted-by: Claude Code:claude-opus-5-5
(cherry picked from commit 40dac07)

cursor Bot left a comment