`gmake setup` / `helios-build` doesn't rebuild `pilot` (in some cases?)

I built an OS image on atrium (which is on heliosv2) today, using the omicron shell script, which wraps running gmake setup and then helios-build experiment-image .... After installing the OS on madrid, it had a hostname of unknown; the logs for the compliance/hostname service revealed the cause:

++ pilot gimlet info -i
ld.so.1: pilot: fatal: libssl.so.1.1: open failed: No such file or directory

Looking in my helios working directory, the pilot binary is quite old (~2 weeks) and predates the heliosv2 upgrade:

john@atrium ~/helios $ ls -l projects/pilot/target/release/pilot
-rwxr-xr-x   2 john     staff    47684680 Jul 12 19:06 projects/pilot/target/release/pilot
john@atrium ~/helios $ elfdump -d ./projects/pilot/target/release/pilot | grep ssl
       [1]  NEEDED            0x6c6dd4            libssl.so.1.1

I expect I can work around this by manually cleaning projects/pilot (or probably safer: blowing away my helios and starting fresh?).

Start with tools/build-host-image.sh and the gmake setup and helios-build steps it wraps, then inspect how projects/pilot/target/release/pilot is rebuilt. Reproduce the stale binary after an OS upgrade and verify that setup produces a pilot linked against the available libraries rather than libssl.so.1.1.