Benefits of Putting Yarn in package.json engines

[Kurt-von-Laven]

What is the rationale for including a snippet of the following form in the package.json of a Yarn project?

"engines": {
  "yarn": "4.0.2"
},

My understanding is that "packageManager": "yarn@4.0.2" is used by Corepack, but I am not aware of any tool besides Yarn v1 that reads the Yarn version from the engines field. Is it only relevant for Yarn v1 compatibility? I know yarn init used to add a yarn engines entry for some version of Yarn, but no version of Yarn v2+ that I tested does this. Hence, I suspect it's safe to remove the engines entry for Yarn, but I want to make sure I'm not missing something.