"Project" renamed to "Matter" in user-facing copy across 21 files
foolish-bandit renamed "Project"/"Projects" to "Matter"/"Matters" in user-visible strings across 21 frontend files. Route names, identifiers (`projectId`, `useProjects`, the `/projects` route), and backend contracts were left unchanged - this is a label-layer change only.
The rename hits the project chat breadcrumb, the project-page assistant header ("Project Assistant" -> "Matter Assistant"), the in-chat pro-tip ("Project Explorer" -> "Matter Documents"), and the tabular reviews filter/tab/column header ("All Projects" / "In Project" / "Filter by project" -> "All Matters" / "In Matter" / "Filter by matter"). Modals, overview pages, and the AddDocButton upload label ("Upload files" -> "Upload documents") are swept in the same commit.
"Matter" is the standard legal term for a discrete engagement. This is the right vocabulary if the product targets practicing lawyers. The rename is well-scoped and mechanically clean.
The identifier/route layer still reads "project" throughout. Internal code search for "matter handling" will come up empty; you'd need to search "project" instead. foolish-bandit acknowledged this debt in the commit - same pattern as the Mike-to-Gary rebrand earlier in the fork. A follow-up commit (b112958) added @fontsource/inter to frontend/package-lock.json, a lockfile fixup from the font migration in the larger polish pass.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?