pfx 0.25.2

A patch release: pfx steam stage accepts a game build reached through the tree's own target symlink.

Install the pfx tool with cargo install --locked --git https://github.com/gmrdad82/pfx --tag v0.25.2 pfx, and depend on a crate by the same tag, for example pfx-game = { git = "https://github.com/gmrdad82/pfx", tag = "v0.25.2" }.

What's new

• pfx steam stage follows the tree's target link. A clone that shares warm builds by making its target folder a symlink into a cache writes its binaries inside the tree by name but outside it once resolved, and v0.25.1 refused them. A depot's path may now also sit under the folder that the caller's own <tree>/target link resolves to, alongside the caller's git tree and the CARGO_TARGET_DIR pfx runs with. A link that holds the caller's tree widens nothing, the manifest itself still has to sit in the tree, and a path outside all of them is refused with a message that names every folder it was checked against (docs/steam.md, "steam.toml").

Notes for callers

• No API changes. A pfx steam stage that was refused for a path under its tree's target link now stages; every other refusal is unchanged, and a refusal's message now lists the target link's folder when there is one.