[Fall 26] Project services hub page #89

Context

/projects/[projectId]/services currently renders an empty page (return <></>). Sidebar already deep-links to Email and Files, but there’s no landing that tells you what’s configured for the project.

Relevant API routes (api-gateway)

Use these to drive “configured or not” status on each card. Base: http://localhost:8888 (or JUNO_BASE_URL). Docs: /docs.

Email

Files

Analytics

API keys

404 / empty → show “Not configured” and link to the setup page.

What to build

Turn /projects/[projectId]/services into a real hub.

Cards for each service:

• Email — configured or not → /projects/[id]/services/email
• Files — configured or not → /projects/[id]/services/files
• Analytics — configured or not → analytics (#88 config, events viewer follow-up; stub link ok if not merged)
• API Keys — count or “manage keys” → #87

“Configured” can be lightweight for v1. Don’t need fancy health checks.

Done when

• Visiting /projects/[id]/services shows a useful overview, not a blank page
• Each card links to the right subpage
• Status is at least roughly correct for the current project
• Looks consistent with the rest of the dash (shadcn cards, etc.)

Notes

• Good parallel ticket with #87, #88 (config), and the analytics events viewer issue
• Mostly frontend; reuse existing SDK actions where possible