feat: add Rust HTTP API test suite (Spec 191)

- Created comprehensive integration test suite for Rust HTTP server APIs.
- Covered all implemented endpoints, error handling, edge cases, and multi-project scenarios.
- Established test architecture and strategy with detailed phases for implementation.
- Included examples of integration tests for project management and spec operations.

feat: implement backend API parity (Spec 192)

- Added missing Rust HTTP API endpoints to achieve parity with Next.js API routes.
- Implemented endpoints for metadata updates, project discovery, directory listing, context management, and project validation.
- Defined implementation requirements and design for each endpoint.
- Created a detailed plan for phased implementation and testing.

feat: port frontend UI components to ui-vite (Spec 193)

- Achieved identical UI/UX between @leanspec/ui (Next.js) and @leanspec/ui-vite (Vite SPA).
- Ported critical components and pages, enhancing existing ones for better functionality.
- Established a component porting strategy and outlined dependencies needed for the new UI.
- Created a comprehensive plan for implementation, testing, and success criteria.

Author: tikazyq

rust/leanspec-mcp/src/tools.rs

@@ -61,7 +61,7 @@ pub fn get_tool_definitions() -> Vec<ToolDefinition> {
                 "properties": {
                     "name": {
                         "type": "string",
-                        "description": "Spec name in kebab-case (e.g., 'my-feature')"
+                        "description": "Short spec name in kebab-case (e.g., 'my-feature'). NOTE: DO NOT add spec number (NNN), it will be auto-generated."
                     },
                     "title": {
                         "type": "string",