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-lite-plan/phases/01-lite-plan.md

@@ -495,7 +495,7 @@ Generate implementation plan and write plan.json.
 Execute: cat ~/.ccw/workflows/cli-templates/schemas/plan-overview-base-schema.json (get schema reference before generating plan)
 
 ## Project Context (MANDATORY - Load via ccw spec)
-Execute: ccw spec load --keywords planning
+Execute: ccw spec load --category planning
 This loads technology stack, architecture, key components, and user-defined constraints/conventions.
 
 **CRITICAL**: All generated tasks MUST comply with constraints in specs/*.md

.claude/skills/workflow-lite-plan/phases/02-lite-execute.md

@@ -485,8 +485,8 @@ ${(t.test?.success_metrics || []).length > 0 ? `\n**Success metrics**: ${t.test.
     context.push(`### Artifacts\nPlan: ${executionContext.session.artifacts.plan}`)
   }
   // Project guidelines (user-defined constraints from /workflow:session:solidify)
-  // Loaded via: ccw spec load --keywords planning
-  context.push(`### Project Guidelines\n(Loaded via ccw spec load --keywords planning)`)
+  // Loaded via: ccw spec load --category planning
+  context.push(`### Project Guidelines\n(Loaded via ccw spec load --category planning)`)
   if (context.length > 0) sections.push(`## Context\n${context.join('\n\n')}`)
 
   sections.push(`Complete each task according to its "Done when" checklist.`)