Over the last few months a lot of work has gone into the PAGI specification and its reference server PAGI::Server to make it more resilient under more real life workloads. The main focus of this release is to make PAGI::Server dependable when clients misbehave or connections end at awkward moments. Clients can abandon uploads, stop reading responses, send malformed traffic, or disappear halfway through a WebSocket closing handshake. Across HTTP, WebSocket, and SSE, the server should handle those cases predictably: report what actually happened, distinguish successful completion from an interrupted exchange, settle pending operations, and release resources without losing cleanup notifications.…