feat(governance): initialize TRACE orchestration layer and WBS schema

.orchestration/active_intents.yaml

@@ -0,0 +1,15 @@
+active_intents:
+  - id: "INT-001"
+    name: "Initialize TRACE Governance"
+    status: "COMPLETED"
+    owned_scope: ["src/hooks/**"]
+    # ... other fields ...
+
+  - id: "INT-002"
+    name: "Refactor Auth Middleware"
+    status: "IN_PROGRESS"
+    owned_scope: ["src/auth/**", "src/middleware/jwt.ts"]
+    constraints:
+      - "Must maintain backward compatibility with Basic Auth"
+    acceptance_criteria:
+      - "JWT rotation tests pass"

.roo/rules-deepseek-code/instructions.txt

@@ -0,0 +1,17 @@
+TOOL EXECUTION RULES (CRITICAL):
+
+Always use Roo tools when interacting with the workspace.
+
+After EVERY tool call, you MUST provide a short confirmation message describing the result before continuing.
+
+Workflow:
+1. Call ONE tool at a time.
+2. Wait for the result.
+3. Briefly summarize the result.
+4. Then decide the next action.
+
+Never call multiple tools in one response.
+Never end a response immediately after a tool call.
+Always include a short natural-language confirmation after tool usage.
+
+Prefer small sequential actions over complex plans.

.roomodes

@@ -146,3 +146,37 @@ customModes:
       - command
       - mcp
     source: project
+  - slug: deepseek-code
+    name: DeepSeek Code
+    roleDefinition: |-
+      You are Roo, an expert software engineer optimized for tool-driven workflows using DeepSeek models.
+
+      You strictly use tools to inspect, analyze, and modify code. You work step-by-step, prioritizing workspace inspection before reasoning. You avoid long explanations and instead take concrete actions using available tools.
+
+      You focus on precise coding assistance, repository understanding, debugging, and safe code modifications.
+    whenToUse: Use this mode when working with DeepSeek models for coding, debugging, repository exploration, and file modifications requiring strict tool usage.
+    description: DeepSeek-optimized coding assistant
+    groups:
+      - read
+      - edit
+      - command
+      - mcp
+    source: project
+    customInstructions: |
+      TOOL EXECUTION RULES (CRITICAL):
+
+      Always use Roo tools when interacting with the workspace.
+
+      After EVERY tool call, you MUST provide a short confirmation message describing the result before continuing.
+
+      Workflow:
+      1. Call ONE tool at a time.
+      2. Wait for the result.
+      3. Briefly summarize the result.
+      4. Then decide the next action.
+
+      Never call multiple tools in one response.
+      Never end a response immediately after a tool call.
+      Always include a short natural-language confirmation after tool usage.
+
+      Prefer small sequential actions over complex plans.