[johnmatthewtennant]

Problem

Deleting a local agent that is still a member of any archived channel never finishes. Every attempt ends with "Switchboard isn't deleted yet and may still be in some channels. It stays stopped; Delete it again to finish."

Delete removes the agent from every channel whose relay roster lists it, then requires a fresh roster read to confirm it is gone. The relay refuses membership changes in an archived channel (OK false "invalid: channel is archived"), so the archived roster keeps listing the agent and the confirmation can never succeed. On John's production account, Switchboard was a member of 14 channels, all archived Solo chats he owns.

Solution

Collect only unarchived channels when removing an agent's memberships:

• removeAgentFromChannels passes the loaded channels that list the agent to memberChannels as candidates.
• memberChannels adds the relay roster hits, reads their fresh relay-signed 39000 metadata, and drops those with archived=true. A loaded row that has not yet seen another client's archive is still skipped.

An archived channel refuses all writes, so the leftover membership is inert. Delete still archives the identity, hiding it from member lists and mentions even if the channel is later unarchived, and deletes the key, so the agent can never act there. The owner can still remove that roster entry later, since removal is signed by the owner. The alternative, unarchiving, removing and re-archiving each channel during Delete, would change the owner's channels as a side effect of deleting an agent.

Reproduction

1. Add a local agent to a channel you own, then archive the channel.
2. Delete the agent from Agents.
3. Before: Delete fails with "isn't deleted yet" on every attempt. After: Delete completes.

Testing

• New regression in relay-removal.test.ts: one active and one archived channel, in both the relay rosters and the loaded channel list, where the loaded row is stale and does not say archived. Removal publishes 9001 only for the active channel and resolves. Without the fresh metadata check, the relay refuses the archived removal and the test fails. The fixture relay now refuses 9001 in archived channels as the real relay does.
• John installed the change in his daily-driver app and deleted Switchboard and Monitor on production, both previously stuck on archived channels. No separate agent app run.

buzz-review-completed

[loganj]

🤖 Larry and Rbot: an independent adversarial review of 4aaf864. Source review only; we did not run the tests locally. Hosted CI is green.

Approve. We found nothing that needs a change.

What we checked:

• Both callers of the Delete cleanup (relay-removal.ts:33 and service.ts:3355) go through removeAgentFromChannels, so the archive skip covers every delete path. memberChannels has no other caller.
• The relay does refuse membership writes in an archived channel (buzz-relay/src/handlers/ingest.rs, "invalid: channel is archived"), so skipping those channels is the only way the fresh-roster confirmation can succeed.
• The archive check is one batched, fresh 39000 read for all candidates, not one read per channel. A channel with no readable metadata stays in the removal set, which is the safe default. A stale loaded row that does not show the archive is still skipped, and the new test covers that case.
• Race: if a channel is archived between the metadata read and the 9001, the 9001 is refused and Delete reports "isn't deleted yet"; a second Delete then skips it. That is acceptable.

Advice (no change needed): exactLifecycleTag throws on a malformed archived tag, so one malformed relay-signed 39000 would now fail the whole Delete, where before it was not read. The relay signs these, so this is very unlikely.