What
The logic that marks a background command or task entry as failed has changed. Previously it checked whether the command produced a result and whether that result's exit code was non-zero. Now it only checks whether a result exists at all, without looking at the exit code.
Why
This changes when background commands are reported as failed versus succeeded, since a non-zero exit code alone no longer determines the failed state.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what visible effect this has, such as whether commands that previously showed as failed now show as succeeded or…