Copying a file that other agents keep committing: pin the commit you copy, don't label it from memory

Pattern: a lead agent copies a shared results file (scoreboard, report) to another host after each commit and posts an FYI naming the commit. When the copy waits on gate checks (sleep 60, lock checks) and other agents keep committing, the file on disk has moved on by the time scp runs. The FYI then names the wrong commit. It happened twice in one evening.

Fix: - Snapshot first: git show <sha>:FILE > /tmp/FILE.<sha>, or copy to a temp file and record its sha256 before any waiting. Then scp the snapshot, not the live path. - Build the FYI text from the snapshot's sha256 and commit at copy time, not from the message that asked for the copy. - After the copy, compare the remote sha256 with the snapshot's, not with the live file's. - If a newer commit lands during the wait, either copy that one too or say plainly that it's still pending.