PR: #354: [Story-1383] Wire matter-shell chrome into live /matters/[id] by @ankitmaheshwari-com
View PR →
Story 1383 · EPIC-006 Matter Shell

Wire the matter-shell chrome into the live /matters/[id]

Story-1382 built MatterDetailHeader + MatterRightRail in Storybook. This puts them on the live matter-detail route against real MatterDetailView data, replacing the old LiveMatterDetailPage header + summary. No faked data.

Composition

Data mapping — MatterDetailView → chrome

PropSource
header matterRef / title / statusmatter.matterRef / .title / .status (enum is identical, no map)
header proceedingCount · lens labelmatter.proceedings.length · localized "All proceedings"
header agentomitted (not in payload — follow-up)
rail caseRef / status / proceedingsCountdirect; lifecycle = status==="closed" ? closed : active
rail leadCounsel / forumnull → em-dash (team + per-proceeding forum not in payload — follow-up)

Brief body — intentionally blank

Per the matter-shell design the tab bodies are TipTap surfaces built later; for this PR the Brief body renders empty (the old summary / operating-model / proceedings / related-matters / carry-forward UI was removed from this route). Other tabs show a localized placeholder. briefBody stays as the documented seam for when the brief content lands.

Verification live

Out of scope (later PRs)

URL-driven tab routing; per-tab body content (sub-nav + TipTap); wiring the matter-type-lead agent, lead counsel, and per-proceeding forum once they land in the detail payload.

Files changed

6 file(s), +91 / -104 lines

Path Role + -
messages/en.jsonConfig+2-0
messages/hi.jsonConfig+2-0
src/app/[locale]/(workspace)/matters/[matterId]/page.tsxApp route+9-80
src/components/matter-detail/matter-detail-header.tsxComponent+4-1
src/components/matters/live-matter-shell.tsxComponent+69-0
tests/unit/matter-detail-route.test.tsxTest+5-23