feat: add category and scope to specs for enhanced filtering and organization

- Introduced SpecCategory and SpecScope types to categorize specs by workflow stage and scope (global/project).
- Updated Spec interface to include category and scope properties.
- Enhanced SpecCard component to display category and scope badges.
- Implemented category and scope filtering in SpecsSettingsPage.
- Updated localization files to support new category and scope labels.
- Modified spec loading commands to utilize category instead of keywords.
- Adjusted spec index builder to handle category and scope during spec parsing.
- Updated seed documents to include category information.

.claude/skills/workflow-tdd/phases/02-context-gathering.md

@@ -221,7 +221,7 @@ Execute complete context-search-agent workflow for TDD implementation planning:
 
 ### Phase 1: Initialization & Pre-Analysis
 1. **Project State Loading**:
-   - Run: \`ccw spec load --keywords execution\` to load project context, tech stack, and guidelines.
+   - Run: \`ccw spec load --category execution\` to load project context, tech stack, and guidelines.
    - If files don't exist, proceed with fresh analysis.
 2. **Detection**: Check for existing context-package (early exit if valid)
 3. **Foundation**: Initialize CodexLens, get project structure, load docs

.claude/skills/workflow-tdd/phases/05-tdd-task-generation.md

@@ -231,14 +231,14 @@ MCP Capabilities: {exa_code, exa_web, code_index}
 ## PROJECT CONTEXT (MANDATORY - load before planning-notes)
 These files provide project-level constraints that apply to ALL tasks:
 
-1. **ccw spec load --keywords execution** (project specs and tech analysis)
+1. **ccw spec load --category execution** (project specs and tech analysis)
    - Contains: tech_stack, architecture_type, key_components, build_system, test_framework, coding_conventions, naming_rules, forbidden_patterns, quality_gates, custom_constraints
    - Usage: Populate plan.json shared_context, align task tech choices, set correct test commands
    - Apply as HARD CONSTRAINTS on all generated tasks — task implementation steps,
      acceptance criteria, and convergence.verification MUST respect these guidelines
    - If empty/missing: No additional constraints (proceed normally)
 
-Loading order: \`ccw spec load --keywords execution\` → planning-notes.md → context-package.json
+Loading order: \`ccw spec load --category execution\` → planning-notes.md → context-package.json
 
 ## USER CONFIGURATION (from Phase 0)
 Execution Method: ${userConfig.executionMethod}  // agent|hybrid|cli