Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix: harden event-handler deadlock fix

Follow-ups to the re-entrant pump in waitResult:

- waitResult: on abort in the re-entrant branch, re-check pc.done before
  setting the close error, mirroring the blocking path. Prevents a delivered
  result from being masked by a spurious "Connection closed" when a reply and
  a concurrent Stop()/Close() land in the same instant.
- waitResult: guard the dispatch-goroutine match against id 0 so neither the
  pre-Start zero value nor an unparseable stack header is mistaken for the
  dispatch goroutine.
- currentGoroutineID: return 0 on ParseUint failure instead of silently
  ignoring the error; 0 is never a valid goroutine id so the normal blocking
  path is taken.
- currentGoroutineID: replace the sync.Pool + *[]byte with a stack-local
  [64]byte buffer; simpler with no behavioural change.
- Document the bounded re-entrancy depth of the pump.