Import into <matter> — drop your whole case into the Record

What shipped

• The sheet — import-into-matter-sheet.tsx: the matter as a fixed read-only breadcrumb (no selector → the wrong-matter footgun is removed), the §6 Evidentiary-Record warning, a three-bucket SegmentedFilter source axis, the folder/ZIP/file dropzone, promise + privacy lines, per-file rows, and a Run-in-background footer. Reuses BaseSheet, SegmentedFilter, UploadDropzone, UploadQueueItem, SecondaryButton.
• Source buckets — import-source.ts: Client documents · Opponent documents · Other / not sure (default). This is the SOURCE axis only — a weak declared hint, never privilege or side. Work-product privilege is caught downstream (Blake flags + counsel confirm).
• Folder import — folder-drop.ts recurses the webkitGetAsEntry tree so dragging a nested case folder flattens into every contained file; UploadDropzone gains a Choose folder picker (webkitdirectory). ZIPs ride through as one archive (the backend unpacks them on the Record).
• The §6 warning — evidentiary-record-notice.tsx resolves the legal WORDS (Record, privileged, work-product) through the canonical legal-lexicon module (Story-1854, merged) via useLegalTerm; the connective sentence is i18n with those labels interpolated. Legal vocabulary stays single-sourced, never i18n.
• Ledger mint (wired to the real backend) — useMatterImport mints the import on selection through the generated client appCreateDocumentImport → /api/internal/matters/[matterId]/documents/imports → mattersGateway.mintDocumentImport → POST /app/matters/{id}/documents/imports (functions Story-1855, PR #496). The server derives expected_count from the enumerated items; the response's per-item ids thread back into each file's presign as importItemId, so the ledger item walks expected → presigned → accounted. Files then stream via the existing presign → S3 PUT → finalize path (per-file progress, Retry, cancel).
• Hygiene — the superseded Story-1518 intake-upload-sheet + story were removed (the new sheet supersedes them and nothing else referenced them).

How uploads wire to the ledger

All upstream calls ride the shared gateway, so traceparent / correlation propagate automatically (pramaan-docs ADR-104 / ADR-065). No OTel SDK, manual spans, or ad-hoc headers were added on this surface.

System-boundary status (seam closed)

Reconciliation note

The issue AC listed per-file stages "uploaded → scanned → extracting". The canonical mockup (mockups/W1.md, 2026-06-28) supersedes that: W1 = upload only — scan/OCR/index move to the Record. Per repo doctrine (linked mockup > pasted brief), W1 shows transfer progress only; processing facts belong to the Record / matter-detail page.

Verification

• Storybook story with the four required states — Empty · Uploading · MixedProgress · FailedRetry (import-into-matter-sheet.stories.tsx); compiles under typecheck + build (visual pass via pnpm storybook).
• folder-drop.test.ts proves nested-folder recursion flattens; flat-list fallback covered.
• pnpm typecheck, pnpm lint, pnpm test (935), pnpm build, pnpm check:routes — all green; git diff --check clean; codegen idempotent against the synced mirror.
• i18n: every new non-legal key added to both messages/en.json and messages/hi.json; legal copy from the lexicon module, not i18n. Tokens only — no color/hex literals.

Files changed

68 file(s), +3552 / -185 lines