6.5.3 Details landing at `/settings/project` — read-only project identity + the re-homed Archive danger zone (the 6.8 seam)

Estimate: 24m · Depends on: 6.5.1, 6.5.2

The Details page the area lands on (the verified mirror rule: settings opens on Details; Details owns identity + the danger zone), per the 6.5.1 design.

Build: /settings/project (the retired hub route) becomes the Details page: read-only identity rows — avatar, name, key (PROD), workspace, created — rendered with the designed "editing arrives with project-details editing" presentation (the 6.8 seam: 6.8 swaps these rows for its edit forms + the key-change flow; no edit affordances are improvised here); the ArchiveProjectCard re-homed as the page’s danger zone (its modal + behaviour unchanged — a move, not a rebuild); the registry’s details entry active in the nav. No new schema, no new service writes — the page reads the active-project context the hub already read.

Acceptance criteria

• /settings/project renders Details inside the area chrome per the design: identity rows read-only, the 6.8 seam presentation, the danger zone with the existing archive flow working end-to-end (archive → the shipped post-archive behaviour).
• Entering settings from the app sidebar lands here with the Details nav entry active; the no-active-project empty state still renders on the route.
• Non-admin members see Details read-only WITHOUT the danger zone (archive is admin-gated — the shipped 1.3.4 rule); axe-clean; token tiers; next-intl.
• Integration tests over the role split + archive flow; coverage ≥90%.

Context refs

• design/projects/settings-area.mock.html (the Details panel) — THE authority
• app/(authed)/settings/project/_components/ArchiveProjectCard.tsx + ArchiveProjectModal.tsx (re-homed, not rebuilt); lib/projects active-project context
• The 6.8 stub (stubs.ts) — the story that grows this page (edit + key change); keep the seam aligned with its description
• 6.5.2 (the chrome + registry this page mounts into)