Move project renaming from the project view to configuration

- ProjectView: title is now a plain <h1>, no longer inline-editable
  (dropped titleDraft/saveTitle/patchProject and the input markup --
  nothing else used patchProject).
- ProjectConfigureView: new 'Project name' section above 'Statuses',
  a small PATCH /api/projects/:id form. On success it also calls the
  projects store's fetchProjects(), since the dashboard grid and the
  sidebar's project dropdown read from that store and otherwise
  wouldn't pick up the new name (or the project's new alphabetical
  position) until some unrelated reload.
- style.css: dropped the now-dead .project-head__title input rules
  (both views render a plain heading now); .project-head__title gains
  word-break so a long static title still wraps instead of overflowing.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

web/README.md

@@ -99,11 +99,11 @@ ghost. The same rule covers every kanban status column too (below).
 
 `/projects/:id` shows one project. It renders on a **full-width** layout (the
 route sets `meta.wide`, which widens `.app__main` in `App.vue`), so the header
-spans the full width and the **Manage** menu sits top right. The title is
-inline-editable (saved on blur via `PATCH /api/projects/:id`). Manage
-(`ProjectManageMenu.vue`) has a **Configure** link (to the status-management
-view below) and a **Delete project** action that opens a confirmation modal;
-confirming calls `DELETE /api/projects/:id` and returns to the dashboard.
+spans the full width and the **Manage** menu sits top right. The title is a
+plain heading here -- renaming lives on the configuration view (below). Manage
+(`ProjectManageMenu.vue`) has a **Configure** link (to that view) and a
+**Delete project** action that opens a confirmation modal; confirming calls
+`DELETE /api/projects/:id` and returns to the dashboard.
 
 Below the header are two tabs (local `activeTab` state, `v-show` so both stay
 mounted). The tab order is fixed — **All tasks** first, **Kanban** second — but
@@ -139,6 +139,14 @@ statuses. The header mirrors the project view's — title, then a
 alike (both `.menu__toggle`) (Manage's own Configure link is hidden here,
 since it would just point at the current page).
 
+A **Project name** section (a plain `PATCH /api/projects/:id` form,
+`{ title }`) sits above **Statuses**. On success it also calls the
+`projects` store's `fetchProjects()` -- the local `project` ref (and this
+view's own header) update from the PATCH response directly, but the
+dashboard grid and the sidebar's project dropdown read from that store, so
+without the extra fetch the new name (and alphabetical position -- projects
+are API-ordered by title) wouldn't show up there until some other reload.
+
 The status list is a `vuedraggable` list (its own list, no shared drag group
 with the kanban board) bound directly to a local `statuses` ref; dragging
 mutates it in place, and `@change` persists the whole new order via