Workspace data on one page; settings laid out like GitHub's, opening on a Profile

Two workspace pages show overlapping "how is the workspace doing" data, split across two addresses:

• /:owner/-/overview: Code's Overview (routes/workspace/code-overview.tsx, laid out by components/mission-control.tsx): what needs you and what landed, the week's numbers, activity.
• /:owner/-/workspace: the workspace at a glance (routes/workspace/workspace-overview.tsx): ground truth from lib/signals.ts (the past week, the quarter's agent spend tied to the work it produced, what's moving and waiting team by team), provider-reported spend, members, projects, usage against plan.

What we want

1. The data on one page

• The data output (activity, the week's numbers, ground truth, agent spend, what's moving/waiting, usage) lives on one page, not two.
• The address that stops hosting the data redirects to the one that does, so existing links (e.g. -/overview?tab=needs#work from components/ground-truth.tsx) keep working.
• Nav (lib/apps.ts, components/mobile.tsx, the chrome) shows one entry for the consolidated page.

2. Settings open on the workspace's Profile, not an overview

The base of the workspace's settings is a Profile (a "General" page), the way GitHub's organization settings open, not an overview of data. It is the root of settings: /:owner/-/settings redirects to /:owner/-/settings/profile, as github.com/organizations/flagon-io/settings redirects to …/settings/profile. Every other settings page sits under -/settings/… beside it. It edits who the workspace is:

• Display name
• Avatar / profile picture (upload a new one)
• Description
• URL
• Public email
• Social accounts (a few links)
• Location
• Billing email (private), with a link to billing for more recipients

3. Settings laid out like GitHub's

Settings get GitHub's separation and placement: one sidebar under -/settings/…, Profile on top, then sections with headings and dividers, and pages with sub-pages that expand in place. Today our settings pages are scattered at the workspace root. A first mapping of ours onto GitHub's sections (to confirm while building; anything without a page of ours is left out, not stubbed):

Each page moves under -/settings/…, and its old address redirects there. Product pages (Work, Security's alerts, Packages' listing, Insights) stay where they are; only their settings move.

Open questions

• Which address keeps the data: -/workspace or -/overview?
• Where does what today's -/settings page holds go: into the Profile, or its own -/settings/… page?
• Confirm the mapping above, page by page.
• Which profile fields does the workspace already store, and which are new?