Admin drops the orphaned matter and filing type Storybook surfaces
The app-owned matter configuration experience stays in pramaan-app. Admin only carried isolated Storybook component copies, so this change removes the unused code without touching live admin routes or shared table infrastructure.
What was deleted
The full Storybook-only component directories were removed from admin:
src/components/matter-types/, including catalog, detail, tabs, sheets, dialogs, fixtures, stories, and README.src/components/filing-types/, including catalog, list, sheet, archive dialog, fixtures, stories, and README.
Orphan evidence
A path-specific import search outside those directories found no admin routes, barrels, indexes, or feature surfaces importing matter-types or filing-types. The only excluded-surface text hit was suggestedMatterType in src/components/agent-activity/agent-activity-fixtures.ts, which is a JSON fixture string and not a component import.
The issue records the ownership boundary: the real feature is routed in pramaan-app under settings/matter-configuration/{matter-types,filing-types}. Admin's copies came from the prior Storybook surface work and had no admin route wiring.
Scope guardrails
No pramaan-app files, generated contracts, backend code, shared use-data-table hook, server-backed admin lists, NuqsAdapter mounts, nuqs dependency, or @tanstack/react-table dependency were changed.
pramaan-docs ADR-124: dead-code deletion only; instrumentation-exempt.
Verification proof
Required local verification: pnpm lint, pnpm exec tsc --noEmit, pnpm test, NEXT_PUBLIC_ENV=local pnpm build, pnpm build-storybook, and git diff --check.
Reference checks: grep -rn "components/matter-types\|components/filing-types" src returns no dangling references, and both deleted component directories are absent from the worktree.