[itz4blitz]

What

A person who is already signed in to Slack, Discord, or the other networks can add one Tiny server they already run, from the rail plus menu. The sheet asks for the server address, then the email, then the password. chatd stores that session in the existing per-network keychain item. Signing out drops it locally even if the server cannot be reached.

Slack, Discord, Teams, Telegram, Signal, and Messages are unchanged. They still talk to those networks directly. There is still no tinyclient server.

The server this client talks to is tinyserver.

Not in this pull request

Conversations, invites, rooms, and voice. The session HTTP this client calls (POST /v1/session, GET /v1/me, DELETE /v1/session) lives in tinyserver.

Tests

• cargo test -p protocol --lib
• cargo test -p chatd --lib adapters::tiny (bad address, bad email, session JSON, and a local HTTP server for open / me / delete / a redirect that is not followed)
• cargo check -p tinyclient --features gui --tests
• cargo test -p tinyclient --features gui every_problem_has_the_words_of_the_design
• One ignored live round trip against a running tinyserver: open, me, delete, then me is unauthorized. It passed locally and is not run by CI.

Message search joins the space table for the space name. The previous query read conversation.space_title, which is not a column, so cargo test --workspace failed here and on main.