v0.8.12

v0.8.12

The room bridge's own tools take the host's room arguments now, so an agent names a room the same
way for next_request as for a page tool. The events extension signs and verifies its webhooks
through servicekit v0.2.2, with no change on the wire.

Changed (room bridge)

• WithRoomOf(fn, rooms.RoomArgs{...}). RoomArgs declares the arguments the mapper reads,
  as JSON Schema properties, and attach, detach, list_pages, pair and next_request accept
  them beside resource. Before, only page tools took the host's arguments, and the rest needed the
  room's resolved name, which nothing on the wire tells an agent. resource still wins when given,
  and the mapper runs only when one of its arguments is present, so a bare list_pages keeps the
  session's default rooms. attach and pair stop requiring resource once room arguments are
  declared. (issue 1633, PR 1635)
  • Breaking: WithRoomOf takes a second argument. nil keeps the old behaviour.

Changed

• servicekit v0.2.2 in every module (was v0.2.0). (PR 1634)
• experimental/ext/events signs and verifies Standard Webhooks through
  servicekit/http/webhooks. VerifyStandardWebhooksSignature, TimestampWithinTolerance,
  DefaultTimestampTolerance and GenerateSecret keep their names and behaviour and wrap it now,
  so another module can reuse the same signer. The events conformance suites pass unchanged.
  (issue 1578, PR 1634)

Upgrading downstream

• agni:
  • Go: experimental/ext/rooms, …/rooms/massrelay and …/integrations/roomsevents at
    v0.8.12.
  • Pass the design argument's schema to WithRoomOf, e.g.
    rooms.WithRoomOf(designRoom, rooms.RoomArgs{"design": {"type": "string"}}), and an agent can
    call next_request{design} the way it calls viewer_show_sheet (agni issue 1173).
  • Browser: @panyam/mcpkit-rooms@0.8.12. No change from 0.8.11.