feat: Enhance spec management with new hooks and settings features

- Updated test cycle execution steps to streamline agent execution.
- Improved HookDialog component with enhanced validation messages and localization.
- Introduced SpecDialog component for better spec management.
- Added new hooks for fetching and updating specs list and frontmatter.
- Implemented API functions for specs list retrieval and index rebuilding.
- Added localization support for new specs settings and hooks.
- Enhanced SpecsSettingsPage to manage project and personal specs effectively.
- Updated CLI commands to support keyword-based spec loading.
- Improved spec index builder to categorize specs by workflow stages.

.claude/agents/cli-explore-agent.md

@@ -54,14 +54,11 @@ Phase 4: Output Generation
    - Other schemas as specified in prompt
    Read and memorize schema requirements BEFORE any analysis begins (feeds Phase 3 validation).
 
-3. **Project Context Loading** (from init.md products):
-   - Read `.workflow/project-tech.json` (if exists):
+3. **Project Context Loading** (from spec system):
+   - Load exploration specs using: `ccw spec load --keywords exploration`
      - Extract: `tech_stack`, `architecture`, `key_components`, `overview`
      - Usage: Align analysis scope and patterns with actual project technology choices
-   - Read `.workflow/specs/*.md` (if exists):
-     - Extract: `conventions`, `constraints`, `quality_rules`, `learnings`
-     - Usage: Apply as constraints during pattern analysis, integration point evaluation, and recommendations
-   - If either file does not exist, proceed with fresh analysis (no error).
+   - If no specs are returned, proceed with fresh analysis (no error).
 
 4. **Task Keyword Search** (initial file discovery):
    ```bash

.claude/agents/cli-lite-planning-agent.md

@@ -54,9 +54,8 @@ When invoked with `process_docs: true` in input context:
 
 ## Input Context
 
-**Project Context** (read from init.md products at startup):
-- `.workflow/project-tech.json` → tech_stack, architecture, key_components
-- `.workflow/specs/*.md` → conventions, constraints, quality_rules
+**Project Context** (loaded from spec system at startup):
+- Load specs using: `ccw spec load --keywords "exploration architecture"` → tech_stack, architecture, key_components, conventions, constraints, quality_rules
 
 ```javascript
 {

.claude/agents/context-search-agent.md

@@ -77,14 +77,11 @@ if (file_exists(contextPackagePath)) {
 
 **1.1b Project Context Loading** (MANDATORY):
 ```javascript
-// Load project-level context (from workflow:init products)
+// Load project-level context (from spec system)
 // These provide foundational constraints for ALL context gathering
-const projectTech = file_exists('.workflow/project-tech.json')
-  ? JSON.parse(Read('.workflow/project-tech.json'))    // tech_stack, architecture_type, key_components, build_system, test_framework
-  : null;
-const projectGuidelines = file_exists('.workflow/specs/*.md')
-  ? JSON.parse(Read('.workflow/specs/*.md')) // coding_conventions, naming_rules, forbidden_patterns, quality_gates
-  : null;
+const projectSpecs = Bash('ccw spec load --keywords "exploration architecture" --stdin');
+const projectTech = projectSpecs?.tech_stack ? projectSpecs : null;
+const projectGuidelines = projectSpecs?.coding_conventions ? projectSpecs : null;
 
 // Usage:
 // - projectTech → Populate project_context fields (tech_stack, architecture_patterns)

.claude/agents/debug-explore-agent.md

@@ -35,9 +35,8 @@ Phase 5: Fix & Verification
 
 ## Phase 1: Bug Analysis
 
-**Load Project Context** (from init.md products):
-- Read `.workflow/project-tech.json` (if exists) for tech stack context
-- Read `.workflow/specs/*.md` (if exists) for coding constraints
+**Load Project Context** (from spec system):
+- Load exploration specs using: `ccw spec load --keywords exploration` for tech stack context and coding constraints
 
 **Session Setup**:
 ```javascript