fix: implement keyword-based routing in getTaskRoutingRecommendation

[htafolla]

Summary

• Implement keyword-based task routing in getTaskRoutingRecommendation
• Add Node.js type declarations to tsconfig.json

Problem

The getTaskRoutingRecommendation function insrc/enforcement/enforcer-tools.ts was a stub that returned empty suggestedSkill regardless of task complexity. This meant tasks were not being routed to appropriate agents/skills.

Additionally, the tsconfig.json was missing Node.js type declarations, causing hundreds of TS2307/TS2580 errors for built-in modules like fs, path, crypto, process, Buffer, and require.

Solution

Part 1: Keyword-based routing

• Implemented keyword matching using the existing ROUTING_MAPPINGS array
• Routes tasks to appropriate skills based on keywords (e.g., "test" → testing-lead, "security" → security-auditor)
• Preserves fallback to orchestrator for unrecognized tasks

Part 2: TypeScript configuration

• Added "types": ["node"] to tsconfig.json compilerOptions
• Resolves all Node.js type declaration errors

Test plan

• TypeScript typecheck passes with no errors
• Existing tests continue to pass
• Keyword routing correctly matches task descriptions to skills