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-test-fix/phases/02-test-context-gather.md

@@ -345,7 +345,7 @@ Execute complete context-search-agent workflow for 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-test-fix/phases/05-test-cycle-execute.md

@@ -244,7 +244,7 @@ Task(
     ${selectedStrategy} - ${strategyDescription}
 
     ## PROJECT CONTEXT (MANDATORY)
-    1. Run: \`ccw spec load --keywords execution\` (tech stack, test framework, build system, constraints)
+    1. Run: \`ccw spec load --category execution\` (tech stack, test framework, build system, constraints)
 
     ## MANDATORY FIRST STEPS
     1. Read test results: ${session.test_results_path}