feat: add SpecDialog component for editing spec frontmatter

- Implement SpecDialog for managing spec details including title, read mode, priority, and keywords.
- Add validation and keyword management functionality.
- Integrate SpecDialog into SpecsSettingsPage for editing specs.

feat: create index file for specs components

- Export SpecCard, SpecDialog, and related types from a new index file for better organization.

feat: implement SpecsSettingsPage for managing specs and hooks

- Create main settings page with tabs for Project Specs, Personal Specs, Hooks, Injection, and Settings.
- Integrate SpecDialog and HookDialog for editing specs and hooks.
- Add search functionality and mock data for specs and hooks.

feat: add spec management API routes

- Implement API endpoints for listing specs, getting spec details, updating frontmatter, rebuilding indices, and initializing the spec system.
- Handle errors and responses appropriately for each endpoint.

.codex/skills/collaborative-plan-with-file/SKILL.md

@@ -194,7 +194,7 @@ Use built-in tools directly to understand the task scope and identify sub-domain
 **Analysis Activities**:
 1. **Search for references** — Find related documentation, README files, and architecture guides
    - Use: `mcp__ace-tool__search_context`, Grep, Glob, Read
-   - Read: `.workflow/project-tech.json`, `.workflow/project-guidelines.json` (if exists)
+   - Read: `.workflow/project-tech.json`, `.workflow/specs/*.md` (if exists)
 2. **Extract task keywords** — Identify key terms and concepts from the task description
 3. **Identify ambiguities** — List any unclear points or multiple possible interpretations
 4. **Clarify with user** — If ambiguities found, use AskUserQuestion for clarification