feat(routing): toAiGateway() terminator for BoxLang AI Gateways

changelog.md

@@ -9,8 +9,28 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Added
+
+- `route( "/gateways" ).toAiGateway()`: a routing DSL terminator exposing a BoxLang AI Gateway over
+  HTTP, alongside `toAi()` and `toMCP()`. Registers the sub-route family a gateway surface needs:
+  `GET/POST {pattern}[/:gateway]/events` (the platform's URL-verification handshake and its inbound
+  events, on one URL because that is what a platform is given),
+  `GET {pattern}/interactions/:requestID` and `POST {pattern}/interactions/:requestID/decisions` for
+  human-in-the-loop approvals, and `GET {pattern}/info`. Pin a mount to one gateway with
+  `toAiGateway( "slack" )`, or leave the name out and one mount serves every gateway registered in
+  `aiGatewayRegistry()`. Pass a `session` (a WireBox ID or a live `GatewaySession`) and every inbound
+  message is dispatched as an agent turn and acked `202` immediately, without waiting on the turn:
+  a platform webhook times out in seconds while an agent turn does not. Without one, inbound events
+  are verified and parsed only. BoxLang only, and requires the `bxai` module. ([bx-ai#286](https://github.com/ortus-boxlang/bx-ai/pull/286))
+
 ### Fixed
 
+- A route `response` closure that rendered the response itself (`event.renderData(...)`) had its
+  status code and content type flattened back onto the route's static `statusCode` by the router's
+  own `renderData()` call. Render data set during the closure is now left alone, so a closure can
+  answer with a per-request status. Render data an interceptor set before the route ran is
+  unaffected.
+
 - `BoxLangProvider` did not convert CacheBox's minute-based timeouts before handing them to BoxLang's
   cache, which reads a bare number as seconds, so every timeout expired sixty times too soon. A region
   moved from `CacheBoxProvider` to `BoxLangProvider` kept a 10 minute object for 10 seconds.