fix: Correct provider names for pragmatist and backend

- pragmatist: deepseek -> opencode-deepseek (provider name was wrong)
- backend: opencode-reasoner -> opencode-deepseek (reasoner too slow for turns)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

cmdforge/discussion-backend/config.yaml

@@ -18,7 +18,7 @@ meta:
   - Are there data integrity risks?
   - Is the storage strategy appropriate for the use case?
   voice: en-AU-Neural2-B
-  provider: opencode-reasoner
+  provider: opencode-deepseek
   color:
   - 100
   - 200
@@ -113,7 +113,7 @@ steps:
     \ needed\n- REJECT: Significant backend issues\n- null: Comment only, no vote\
     \ change\n\nIf you have nothing meaningful to add, respond: {{\"sentinel\": \"\
     NO_RESPONSE\"}}\n"
-  provider: opencode-reasoner
+  provider: opencode-deepseek
   output_var: response
 - type: code
   code: "import sys\nimport datetime as dt\ntimestamp = dt.datetime.now().strftime(\"\

cmdforge/discussion-pragmatist/config.yaml

@@ -20,7 +20,7 @@ meta:
     - "Are we over-engineering this?"
     - "What's the simplest thing that could work?"
     - "Is this scope creep?"
-  provider: deepseek
+  provider: opencode-deepseek
 
 arguments:
   - flag: --callout
@@ -193,7 +193,7 @@ steps:
       - null: Comment only, no vote change
 
       If you have nothing meaningful to add, respond: {{"sentinel": "NO_RESPONSE"}}
-    provider: deepseek
+    provider: opencode-deepseek
     output_var: response
 
   # Step 5: Log progress after AI call