The /conversations/:id/leave handler used to delete the leaver's
participant row unconditionally. If the leaver was the only admin, the
group survived but no one could rename it, change the picture, or
add/remove members. If they were also the only participant, the empty
conversation lingered forever.
Server (artifacts/api-server/src/routes/conversations.ts):
- Load all participants ordered by joinedAt before mutating anything.
- If the leaver is the only participant, delete the conversation row
(cascades clean up participants, messages, and reads) and skip the
emit.
- If the leaver is the only admin, promote the longest-tenured
remaining participant (oldest joinedAt) to admin in the same flow.
- Emit a `member_left` system message and, when applicable, an
`admin_promoted` system message (with reason `previous_admin_left`)
before removing the leaver, so members see both events live.
Client (artifacts/teaboy-os/src/pages/chat.tsx + locales):
- Render the new `member_left` and `admin_promoted` system message
kinds with bilingual copy in en.json and ar.json.
- Extended SystemMessageMeta with `promoted` and `reason` fields.
Approach notes:
- Chose auto-promotion over a chooser dialog to keep the leave flow
one-tap; proposed a follow-up (#46) for an optional successor
picker.
- API contract for /leave is unchanged (still POST with no body), so
no openapi.yaml or codegen changes were needed.
- Pre-existing TypeScript errors in auth.ts, admin.tsx, etc. are
unrelated codegen drift and were left alone.
Replit-Task-Id: 026e59a5-90c0-4faa-9080-aee0aee0a631
riyadhafraa
a52c1659fc