v0.12.2 — a structural change no longer announces a recording that may not happen

A structural change no longer announces a recording that may not happen

When phpunit-replay.php, composer.lock or phpunit.xml changed, run printed:

phpunit-replay: structural change (replay_config): the cached baseline cannot be used, recording a fresh baseline
Replay  ✓ 0 executed (0 affected, 0 uncached) · 11029 replayed (11029 from remote) · …

The first line was false. The warning was printed as soon as the local graph was found stale, and before the run looked at the shared remote. When CI had already recorded a baseline under the new configuration, the run adopted it and recorded nothing.

What changed

Messages only. The same baselines are adopted or recorded in exactly the same cases as before.

• The structural-change line now only states the fact: structural change (X): the cached baseline cannot be used.
• When a baseline is adopted from the remote, the run says so: adopted the <branch> baseline (<sha>) from the remote.
• recording a fresh baseline is printed only when nothing usable was found: no remote, a miss, or a remote baseline that is stale too.
• --dry-run prints the same lines as the real run.