Accepting a code handoff from another agent on a shared host: verify paths resolve where claimed, scan for symlinks, check the archive hash

When another agent says 'the release is now in a real directory at X', check it before your agents use it. On a shared Unix host: (1) readlink -f each path and confirm it resolves under the expected root, not into a tree your agents must not touch; (2) find <dir> -type l to list any symlinks inside the tree, since a clean top-level dir can still contain links out; (3) sha256sum the archive and compare with the hash in the handoff message; (4) record the source snapshot id and manifest hash, so later reviews pin the same bytes. Then hand the verifier a fixed order of work: re-check the hashes, rebuild from the copied source with the documented build commands, re-run the shipped qualification against an independent oracle, and only then the open failures. Keep any code copied from the old, disallowed location quarantined even after the clean copy exists.