task: verify two people on two machines can talk on the deployed relay

[tucktuck101]

Parent PRD

#2

Objective

Record evidence on this issue that two cohort members, on separate machines with separate Nostr identities, exchanged both channel messages and direct messages through the deployed relay.

Definition of done

• Person A and person B each connect from their own machine, each with their own Nostr identity
• Both pubkeys are added to the roster with buzz-admin add-member, and the commands are recorded
• A and B both see each other's messages in a shared channel
• A direct message from A reaches B, and a direct message from B reaches A — both directions evidenced separately
• Neither participant is on the VPS itself, nor on the same machine as the other
• A pubkey that was never added to the roster is shown to be refused, confirming gating is live rather than merely configured
• Each success criterion listed in prd 0 - Deploy the relay to a VPS and verify two people can log in #2 is referenced explicitly against the evidence that satisfies it
• Anything that could not be verified is stated as not verified rather than omitted

Impacted components

deployed relay      runtime verification only
launchpad/deploy/   membership steps corrected if the runbook proved wrong

No repository files change unless the runbook needed correcting.

Out of scope

• Desktop or mobile client changes. Clients connect as they ship, per prd 0 - Deploy the relay to a VPS and verify two people can log in #2.
• Agent workloads on the relay. Two humans exchanging messages is the bar.
• Load, soak or capacity testing.
• Fixing anything the verification uncovers. That gets filed as a Bug against prd 0 - Deploy the relay to a VPS and verify two people can log in #2.

---

_{Filed by an AI agent (Claude Opus 5) on behalf of @tucktuck101 as part of a decomposition of #2. Drafted, not executed — this issue is the final verification gate for #2 and depends on the deployment task completing first.}

[tucktuck101]

Done, per @tucktuck101: the deployed relay is up and in use. Client authentication against it was independently observed on 2026-08-21 (NIP-42 auth, 6 channels loaded from a desktop client).

_{Closed by an AI agent (Claude Opus 5) on the explicit instruction of @tucktuck101.}