feat: add PATCH endpoint for updating spec metadata; update API tests and README

Author: tikazyq

packages/http-server/README.md

@@ -70,6 +70,7 @@ The server reads configuration from `~/.lean-spec/config.json`:
 ### Specs
 - `GET /api/specs` - List specs (with filters)
 - `GET /api/specs/:spec` - Get spec detail
+- `PATCH /api/specs/:spec/metadata` - Update spec metadata
 - `POST /api/search` - Search specs
 - `GET /api/stats` - Project statistics
 - `GET /api/deps/:spec` - Dependency graph

packages/ui-vite/src/lib/api.test.ts

@@ -143,7 +143,7 @@ describe('API Client', () => {
       await api.updateSpec('spec-001', updates);
 
       expect(mockFetch).toHaveBeenCalledWith(
-        expect.stringContaining('/api/specs/spec-001'),
+        expect.stringContaining('/api/specs/spec-001/metadata'),
         expect.objectContaining({
           method: 'PATCH',
           body: JSON.stringify(updates),

packages/ui-vite/src/lib/backend-adapter.ts

@@ -99,7 +99,7 @@ export class HttpBackendAdapter implements BackendAdapter {
     name: string,
     updates: Partial<Pick<Spec, 'status' | 'priority' | 'tags'>>
   ): Promise<void> {
-    await this.fetchAPI(`/api/specs/${encodeURIComponent(name)}`, {
+    await this.fetchAPI(`/api/specs/${encodeURIComponent(name)}/metadata`, {
       method: 'PATCH',
       body: JSON.stringify(updates),
     });

specs/198-ui-vite-remaining-issues/README.md

@@ -10,12 +10,11 @@ tags:
 depends_on:
 - 193-frontend-ui-parity
 created_at: 2025-12-26T06:32:10.135558Z
-updated_at: 2025-12-26T06:33:23.302928Z
+updated_at: 2026-01-06T14:59:35.350392Z
 transitions:
 - status: in-progress
   at: 2025-12-26T06:33:23.302928Z
 ---
-
 ## Overview
 
 After implementing initial UI parity between Next.js and Vite apps in spec 193, several critical issues remain that prevent full feature parity and usability. These issues affect navigation, routing, project management, and layout consistency.