Profile events: "Hosting" section duplicates events already in Upcoming

## What's confusing The profile page's events area splits the user's events into three subsections — **Upcoming**, **Past**, **Hosting** — but events the user hosts that are upcoming appear in **both Upcoming and Hosting**, with the same `HOST` badge in each place. The `HOST` badge already tells you the user is the host, so the dedicated "Hosting" subsection adds duplication and noise without adding information. See the screenshot: - **Upcoming (1)** — *Skeptics in the Pub* (May 9) with `GOING` and `HOST` badges. - **Past (1)** — *Lightning Talks* (May 1) with `GOING` badge. - **Hosting (6)** — includes *Skeptics in the Pub* (May 9) again, plus 5 other future events the user hosts. *Skeptics in the Pub* shows up twice on the same page, identical card. That's the bug. ## Expected Pick one of: ### Option A — drop the Hosting section entirely (Recommended) Keep just **Upcoming** and **Past**. The `HOST` badge on the cards is enough; users who want to filter to hosting-only get a small filter chip strip (`All · Hosting · Going · Maybe`) above the list. Cleanest UX. Eliminates duplicates by construction. Mirrors what most event sites do (Meetup, Eventbrite — events page has a single chronological list with a filter). ### Option B — make sections mutually exclusive If a section split is desired: - **Upcoming** = events you're attending (not hosting). - **Past** = events you attended (not hosting). - **Hosting** = events you're hosting (regardless of date — split into Upcoming Hosting / Past Hosting if useful). No event ever appears in two sections. The split tells the viewer something meaningful. ### Option C — keep three sections but remove the duplication If the current taxonomy must stay, at minimum filter `Upcoming` and `Past` to **non-hosted** events; `Hosting` keeps everything you host. Worst of the three — sections feel arbitrary, but no duplication. ## Reproduction 1. Sign in as a user who is hosting at least one upcoming event. 2. Open your own profile page. 3. Scroll to the events section. 4. Observe: at least one event appears in both **Upcoming** and **Hosting** with identical content. ## Suggested fix direction Recommend Option A. Implementation sketch: - Frontend: replace the three `Upcoming / Past / Hosting` lists with a single chronological list (Upcoming on top, Past below) plus a filter chip group: `All · Hosting · Going · Maybe`. - Backend: the existing endpoint already returns `is_host: bool` per event row (or equivalent — verify); no schema change needed. Filter happens client-side. - Card rendering: keep the `HOST` and `GOING` badges as today. ## User-facing terminology The screenshot section headers ("Gathrings", "Hosting") are user-facing brand copy — keep as-is. The structural fix is what matters. ## Impact - Users see the same event twice on their own profile, which looks like a bug. - The page is longer than it needs to be — `Hosting (6)` adds 6 cards mostly redundant with what's elsewhere. - New users won't intuit why "Hosting" exists separately when the HOST badge is already shown. ## Found by Manual testing