* feat(producer): a render that fails on a missing file says what was gone again
Restores the diagnostic the previous commit on main took out, as it was; the commits after it confine what it looks at.
* test(producer): render failure diagnostics never probe a path from error text or outside the render
* fix(producer): probe a missing path only from a real error, inside the render's folders
describeMissingPath now reads only the path Node set on an ENOENT error, never
one quoted in a message the page can write, and looks on disk only under the
render's temp root, extract cache or work folder. Any other path is named from
its text, so a network share is never contacted and the facts cannot tell an
existing path from a missing one.
* test(producer): a missing-path probe never passes an outside link or climbs above its folder
* fix(producer): walk down from the render's own folder and check each link before following it
* build(producer): give the packed size budget its 5% headroom with the missing-file diagnostic back
* revert(producer): a render that fails on a missing file stops naming what was gone, for now
This reverts commit cfea8cfff5 (#7955). The detail comes back in a follow-up that only looks inside the folders the render owns.
* revert(producer): name the files the #7955 revert removes in the deletion guard
* fix(producer): a render that fails on a missing file says what was gone
* fix(producer): a failed look at what was missing never hides the render's own error
The missing-path probe now returns nothing when it throws, reads through at most four links and only
links that point into the temp root or the cache folder, names a removed folder by its own name, treats
a custom cache folder as the cache, and skips programs that could not start.
* refactor(producer): split the missing-path link walk into its own step