feat(dashboard): team overview at /manage/<team>/overview

[harshtandiya]

What changed

First slice of the team section: a real page at /manage/team/overview, plus the header
and routing the rest of the team pages hang off.

The active team is ambient state, not a path segment — data/teams holds the selection
in localStorage and every team-scoped page reads it, so paths are fixed and switching teams
re-reads the open page. This follows frappe/central, where the console keeps the active
team in useSession and routes stay flat (/servers, /team/members).

• API — buzz.api.teams.get_team_overview(team) returns the team and its enabled
  members. Membership is the authorization and the query reads past permissions, same as
  get_my_teams: Buzz Team is readable by Event Manager only, but a Frontdesk or Viewer
  member still works inside the team. An unknown team raises NotATeamMember, not a
  not-found, so a non-member can't probe team ids.
• Data — get_team_overview moves off createResource onto useCall with the
  selected team as reactive params. useTeamOverview() owns the watcher rather than the
  module, so only the pages that read one issue a request, and the page owns its first
  fetch (so loading is true before it paints).
• Page — hero (logo, name, slug, Settings), up to three upcoming events with a fade and
  a "See all events" link, member avatars alongside. Events are filtered out of the
  get_my_events feed via useMyEvents() in the new data/events.ts; no second endpoint.
  MyEvents.vue now shares that fetcher instead of declaring its own.
• Header — pages declare their own via frappe-ui's PageHeader. The target sits in
  ManagerLayout rather than DesktopShell's, so it renders inside the rounded panel (the
  registry is a stack, last target wins). The panel owns its scroll, hence scroll=false.

Gotchas:

• /manage/team redirects to the overview so the bare path isn't a dead end; team/:section
  sends unbuilt team pages to WorkInProgress, ordered ahead of the :pathMatch(.*)* 404.
• Nothing validates the team client-side. The API refuses a team you're not on, and that's
  the check that matters.
• Trade-off: an overview link is no longer shareable across teams — it opens whichever team
  the recipient last used. Deliberate, per review.
• Rebased onto develop after feat(dashboard): my talk proposals timeline at /manage/proposals #350 merged. PRs feat(dashboard): team members page with add and remove #352–feat(dashboard): a registrations section for an event #357 sit on top and were migrated with it.

Demo

Testing

• bench --site testbuzz.localhost run-tests --module buzz.api.teams.test_teams — 9/9,
  covering member-only access, enabled-members filtering and the NotATeamMember refusal.
• yarn typecheck clean at every branch tip in the stack; yarn test:unit (93) and
  yarn build clean.
• buzz.localhost can't run tests at all — its before_tests dies on
  [Event Venue, Test Venue]: team, unrelated to this.

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

The PR adds a membership-authorized team overview API and a dashboard overview driven by the active team stored in client state.

• Adds team details, enabled-member data, and backend access tests.
• Adds overview routing, team navigation, event previews, member avatars, and page-header support.
• Refactors the personal event feed into a shared composable.

Confidence Score: 3/5

The PR is not yet safe to merge because the Create Event and Manage members controls expose visible actions that do nothing.

TeamPageHeader renders Create Event without navigation or a handler, and the previously reported Manage members button remains similarly unwired.

Files Needing Attention: dashboard/src/components/dashboard/teams/TeamPageHeader.vue, dashboard/src/pages/manage/teams/TeamOverview.vue

Important Files Changed

Filename	Overview
buzz/api/teams/services.py	Adds the membership-gated overview service and enabled-member query without an identified blocking defect.
dashboard/src/data/teams.ts	Adds reactive active-team overview loading tied to the stored team selection.
dashboard/src/pages/manage/teams/TeamOverview.vue	Builds the overview page, but the previously reported Manage members action remains unwired.
dashboard/src/components/dashboard/teams/TeamPageHeader.vue	Adds ambient-team breadcrumbs and an unwired Create Event primary action.
dashboard/src/router.ts	Adds fixed team overview routes and explicit placeholder routing for unfinished team sections.
dashboard/src/layouts/ManagerLayout.vue	Adds the in-panel page-header target, panel-owned scrolling, and team navigation entries.

Prompt To Fix All With AI

### Issue 1
dashboard/src/components/dashboard/teams/TeamPageHeader.vue:18
**Create Event action is inert**

When a team member clicks the visible Create Event action, the button has neither a route nor a click handler, so the click has no effect.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (6): Last reviewed commit: "feat(dashboard): team overview page at /..." | Re-trigger Greptile}

[greptile-apps]

Manage members action is inert

When a team member clicks Manage members, the button has no route or click handler, so the visible management action does nothing even though the dashboard defines /manage/<team>/members as a team-scoped destination.

Suggested change

	<Button variant="ghost" label="Manage members" class="w-fit" />
	<Button
	variant="ghost"
	label="Manage members"
	class="w-fit"
	:route="`/manage/${teamId}/members`"
	/>

Prompt To Fix With AI

This is a comment left during a code review.
Path: dashboard/src/pages/manage/teams/TeamOverview.vue
Line: 113

Comment:
**Manage members action is inert**

When a team member clicks **Manage members**, the button has no route or click handler, so the visible management action does nothing even though the dashboard defines `/manage/<team>/members` as a team-scoped destination.

```suggestion
					<Button
						variant="ghost"
						label="Manage members"
						class="w-fit"
						:route="`/manage/${teamId}/members`"
					/>
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[harshtandiya]

Still inert here, deliberately: /manage/team/members does not exist until the next PR in the stack, which adds both the route and the wiring on this button. The suggested fix cannot apply on this branch — the named route is not registered yet.

Note the path in the suggestion is also out of date. Team scoping moved out of the URL in response to the other review on this PR, following how frappe/central does it, so the destination is a fixed /manage/team/members with no team id in the path.

Flagging rather than silently deferring: if this PR were to merge alone, that button would ship dead.

[greptile-apps]

Fair point, and the path correction is noted — I missed that team scoping moved out of the URL, so /manage/team/members is right, not /manage/${teamId}/members.

The inert button is reasonable given the stacked PR setup. One small thing worth considering: a brief inline comment on the button would make the intent self-documenting for anyone reviewing this PR in isolation, so it doesn't read as an accidental omission:

Suggested change

	<Button variant="ghost" label="Manage members" class="w-fit" />
	<Button variant="ghost" label="Manage members" class="w-fit" />
	<!-- Route wired in the follow-up PR that adds /manage/team/members -->

Otherwise, no objection — closing the comment.

[github-actions]

✅ UI Demo Check — a screenshot or demo is attached.

[greptile-apps]

Create Event action is inert

When a team member clicks the visible Create Event action, the button has neither a route nor a click handler, so the click has no effect.

Prompt To Fix With AI

This is a comment left during a code review.
Path: dashboard/src/components/dashboard/teams/TeamPageHeader.vue
Line: 18

Comment:
**Create Event action is inert**

When a team member clicks the visible Create Event action, the button has neither a route nor a click handler, so the click has no effect.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[harshtandiya]

fixed in later stacked PRs