A declared lockstep path is contained lexically only, so a committed symlink inside the repository that points outside it is read through: launch reads a file out of the tree and surfaces its parse error or the version value at the pointer. The path must be resolved and a target outside the repository refused.

A declared lockstep path is contained lexically only, so a committed symlink inside the repository that points outside it is read through: launch reads a file out of the tree and surfaces its parse error or the version value at the pointer. The path must be resolved and a target outside the repository refused.

Grounds

• pursued: a declared lockstep file or primary manifest that is a symlink out of the repository makes the check unreadable without reading the outside value; a lockstep read that still opens a joined path would show it wrong