A pre-warmed spare session now clears its spare marker once real work arrives.
What's wrong with this entry?
A session started as a spare now clears its spare flag in its process file when it becomes busy, and a poll clears it when a session state file appears in the session directory.
- Only sessions marked as born spare are affected.
- The process-file writer now returns whether the write succeeded instead of discarding the result, and logs
[concurrentSessions] updatePidFile failed:when it does not.
[concurrentSessions] updatePidFile failed:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.