What happens

The targets of a mcpp.lock entry depend on which commands ran last, not on the configurations the project builds. Observed on mcpp 2026.11.7.2 in the mcpp-language-server workspace (7 members; the lock records x86_64-linux-gnu and x86_64-openkal):

1. mcpp test --workspace --no-run (default target) removes x86_64-linux-gnu from compat.xxhash and mcpplibs.mwrap.xxhash, which the root package uses on both targets:

   -targets = ["x86_64-linux-gnu", "x86_64-openkal"]
   +targets = ["x86_64-openkal"]

   The same happens with the manifests before any edit, so it is not caused by a manifest change. mcpp test --workspace --no-run --target x86_64-linux-gnu does not restore them.
2. mcpp test -p mcppls-pack test_archive followed by the same command with --target x86_64-openkal adds targets = ["x86_64-linux-gnu", "x86_64-openkal"] to nine entries that had no targets line (compat.bzip2, compat.libarchive, compat.lz4, compat.mbedtls, compat.xz, …).

A lock is therefore rewritten by commands that change no resolution, and a committed lock differs from one regenerated in another order. Projects restore the lines by hand (mcpp-ide's aarch64 rows, mcpp-language-server's xxhash rows).

Expected

An entry's targets is the set of configurations in which the resolution reaches the package, kept for the configurations a command did not plan; a command that plans one configuration neither removes the others nor writes targets where the entry records none.

Reproduction

git clone https://github.com/Sunrisepeak/mcpp-language-server && cd mcpp-language-server
git checkout mcppls-0.0.21
mcpp test --workspace --no-run
git diff mcpp.lock            # (1)
git checkout mcpp.lock
mcpp test -p mcppls-pack test_archive && mcpp test -p mcppls-pack test_archive --target x86_64-openkal
git diff mcpp.lock            # (2)