feat: Add role specifications for 三省六部 architecture

- Introduced role specifications for 尚书省 (shangshu), 刑部 (xingbu), and 中书省 (zhongshu) to facilitate task management and execution flow.
- Implemented quality gates for each phase of the process to ensure compliance and quality assurance.
- Established a coordinator role to manage the overall workflow and task distribution among the departments.
- Created a team configuration file to define roles, responsibilities, and routing rules for task execution.
- Added localization support for DeepWiki in both English and Chinese, enhancing accessibility for users.

.ccw/specs/architecture-constraints.md

@@ -1,33 +0,0 @@
----
-title: "Architecture Constraints"
-dimension: specs
-category: planning
-keywords:
-  - architecture
-  - module
-  - layer
-  - pattern
-readMode: required
-priority: high
-scope: project
----
-
-# Architecture Constraints
-
-## Module Boundaries
-
-- Each module owns its data and exposes a public API
-- No circular dependencies between modules
-- Shared utilities live in a dedicated shared layer
-
-## Layer Separation
-
-- Presentation layer must not import data layer directly
-- Business logic must be independent of framework specifics
-- Configuration must be externalized, not hardcoded
-
-## Dependency Rules
-
-- External dependencies require justification
-- Prefer standard library when available
-- Pin dependency versions for reproducibility

.ccw/specs/coding-conventions.md

@@ -1,39 +0,0 @@
----
-title: "Coding Conventions"
-dimension: specs
-category: general
-keywords:
-  - typescript
-  - naming
-  - style
-  - convention
-readMode: required
-priority: high
-scope: project
----
-
-# Coding Conventions
-
-## Naming
-
-- Use camelCase for variables and functions
-- Use PascalCase for classes and interfaces
-- Use UPPER_SNAKE_CASE for constants
-
-## Formatting
-
-- 2-space indentation
-- Single quotes for strings
-- Trailing commas in multi-line constructs
-
-## Patterns
-
-- Prefer composition over inheritance
-- Use early returns to reduce nesting
-- Keep functions under 30 lines when practical
-
-## Error Handling
-
-- Always handle errors explicitly
-- Prefer typed errors over generic catch-all
-- Log errors with sufficient context