chattolib 0.5.0b4 vendor update: full migration and fixes — refresh vendor/ to 0.5.0b4, migrate adapter for new API changes, fix admin_get_member() dict shape and remove isinstance hacks, type _dispatch_message_posted payload parameter as MessagePostedEvent, add debug logging to _admit_and_build exit points, replace admin_get_member with get_room_member for non-admin user resolution, update tests for event_id parameter change

AGENTS.md

@@ -27,7 +27,7 @@ consumption — because the bot is a Chatto client just like the browser. Read
 how the platform itself models a problem before inventing our own shape (its
 presence-overlay pattern is what shaped the roster projection below).
 
-The vendored copy is upstream `chattolib[realtime]` 0.5.0a5.post1 (realtime
+The vendored copy is upstream `chattolib[realtime]` 0.5.0b4 (realtime
 protocol v2); the matching server floor is Chatto v0.5.0-alpha.4. Refreshing `vendor/`
 via `vendor_chattolib.sh` can move that floor (see VENDORING.md) — after each
 refresh, restate the new version here and in README.md.

README.md

@@ -4,7 +4,7 @@ A [Chatto](https://github.com/chattocorp/chatto) platform adapter plugin for [He
 
 All API interaction goes through [chattolib](https://github.com/TheCodemancerLtd/chattolib): a persistent WebSocket realtime connection delivers inbound events, ConnectRPC over HTTP handles outbound messages, reactions, uploads and more. Messages are processed through the full Hermes Agent pipeline (tool use, memory, reasoning) and answered in real time.
 
-Tested against Chatto v0.5.0-alpha.4 with the vendored `chattolib[realtime]` 0.5.0a5.post1 (realtime protocol v2). Chatto servers below v0.5.0-alpha.4 are not supported by this build.
+Tested against Chatto v0.5.0-alpha.4 with the vendored `chattolib[realtime]` 0.5.0b4 (realtime protocol v2). Chatto servers below v0.5.0-alpha.4 are not supported by this build.
 
 Before setup, here's the part most people want to know: how Hermes behaves once it's in your Chatto instance.
 
@@ -431,7 +431,7 @@ grep -i "chatto\|websocket\|realtime" ~/.hermes/logs/gateway.log | tail -30
 ## Notes
 
 - **Self-hosted friendly**: Works with any self-hosted Chatto instance. No cloud account or subscription required.
-- **Minimal dependencies**: Only requires `chattolib[realtime]==0.5.0a5.post1`, which is vendored — nothing to install.
+- **Minimal dependencies**: Only requires `chattolib[realtime]==0.5.0b4`, which is vendored — nothing to install.
 - **No message backfill**: Events missed while the gateway is down are gone — Chatto keeps no replay for the bot. Redelivered events after a reconnect are recognised and processed only once; anything genuinely new starts from the moment of reconnection.
 
 ## Acknowledgements