Hearings tab: events, not documents

What shipped

• New route /matters/[matterId]/hearings mirroring the Filings sub-route — same LiveMatterDetailPage chrome + MatterSubnav, reachable from the matter Worknav and the subnav. The subnav's old #hearings hash anchor is now a real route.
• Hearing Sessions grid: session label, type, forum/bench, date, status — a segmented subtab with a live count.
• Orders & Directions: the proceeding's orders and procedural directions, newest first, each with who issued it and when.
• Data follows the forum pattern: RSC server-prefetch → dehydrate → hydrate → generated TanStack hooks. Read-only — no mutations.

Contract reality — what powers each subtab (and the gaps)

The brief was explicit: do not invent an endpoint. There is no dedicated hearing_session / order entity in the synced src/gen contract yet (it lands in v2). So v1 reads the closest truthful sources and names every gap:

Note the two matter ids: the stages path keys the matter by its firm-scoped number, the audit-timeline path by its UUID. They are different ids by contract — the page passes numericMatterId to sessions and matter.id to orders.

Explicitly deferred (not faked)

• DL-08 exhibit deep-link chips — the mockup's "Exhibits marked" column of clickable C-1 chips that jump to Filings → Exhibit Register. Deferred to v2. They need a hearing_session_id to anchor each marking to a session, which does not exist until the hearing-session entity lands. No chips are built; the column is omitted.
• Forum / Bench value — surfaced as a column (it is part of the session identity) but em-dashed pending a contract field.

Out of scope

Filings / registers (#1886, already merged), Annexure Index export (#1888), and the Blake review surface (#1889). This Story is only the Hearings tab's two event subtabs.

Empty / first-run state

The real deliverable is the zero-row first run — a brand-new matter whose main proceeding has no recorded sessions or orders yet. Both subtabs render an explicit, honest empty panel (never a broken-looking blank), plus loading and error states, all sharing the register chrome. Verified in Storybook (Matters/Hearings/States) and against the real src/gen types — imports from src/gen only; no pnpm codegen run (off current main after Chore-1885).

Trust boundary & surface registry

• New BFF proxies keep the browser on /api/internal/*: Sessions reuse the Filings proceedingProxyHandler; Orders get a proceeding-audit proxy. toBrowserRoute maps both new paths. Every gateway read is parsed through assertContract against the generated schema (HR-21).
• page.tsx exports agentSurface (key: "matter.hearings", agent matter); the route registry regenerated to 30 surfaces.

Verify

• pnpm lint — 0 errors (1 pre-existing warning in add-matter/avatar.tsx).
• pnpm exec tsc --noEmit — clean.
• pnpm test — 949 passing (incl. route-registry freshness + i18n parity).
• pnpm build — green; /matters/[matterId]/hearings + both proxies registered.
• pnpm check:routes — surface registry fresh (30 surfaces; matter.hearings added).
• i18n: Hearings namespace + AgentSurfaces.matterHearings in both en and hi. No color literals introduced.

Files changed

19 file(s), +762 / -7 lines