The self-hosted runner carries a pending-follow-up flag that nothing sets yet.
A bgResultPendingFollowup flag is threaded through session spawn but never set in this build.
What's wrong with this entry?
The self-hosted runner threads a new pending-follow-up callback from its entry point through session spawn, and each session now carries a bgResultPendingFollowup flag initialised to false alongside its live background task list and in-flight turn marker. Nothing in the build shows where the flag is set, so it has no observable effect yet.
bgResultPendingFollowup
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task