A failed process lookup is no longer mistaken for a confirmed no when checking parent processes.
What's wrong with this entry?
Deciding whether a given process is an ancestor of this one now returns three states instead of true/false, so a lookup that produced no usable information is distinguished from one that positively ruled the process out.
- The result is only cached when the process start token read before and after walking the ancestor chain matches.
- The shell command that walks the parent chain now emits explicit END and FAIL sentinels, so a truncated or failed walk is reported instead of being treated as an empty chain.
no-evidence
Strings lifted out of the shipped bundle, so the claim above can be checked against them.