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(server): extend panic recovery wrapper and cover the connect mux

Address review feedback on the recovery wrapper and its coverage:

- Add Unwrap on committedWriter so http.ResponseController can reach
  the underlying writer's Hijacker, deadline, and full-duplex methods;
  without it a protocol upgrade through the connect reverse proxy on
  the UI server would fail.
- Add ReadFrom passthrough so copies into the wrapper keep the
  underlying writer's optimized path, which io.Copy looks up on the
  destination directly without walking Unwrap.
- Wrap the connect server mux with the same recovery handler. The
  webhook bridge does its own parsing before the protected handler,
  and ping, health, reflection, and CORS had no recovery at all. RPC
  panics are still converted to connect error codes by WithRecover
  first; the outer wrapper only sees panics that escape it.
- Rename uiPanicRecovery to httpPanicRecovery since it now fronts both
  servers.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>