chore: remove oh-my-opencode-sin plugin reference from opencode.json

Author: SIN-Agent

configs/opencode.json

@@ -3,8 +3,7 @@
   "plugin": [
     "opencode-antigravity-auth@beta",
     "opencode-openrouter-auth",
-    "opencode-qwen-auth",
-    "/Users/jeremy/.config/opencode/local-plugins/oh-my-opencode-sin"
+    "opencode-qwen-auth"
   ],
   "provider": {
     "nvidia-nim": {
@@ -558,17 +557,17 @@
   "agent": {
     "SIN-Zeus": {
       "mode": "primary",
-      "model": "fireworks-ai/minimax-m2.7",
+      "model": "vercel/deepseek/deepseek-v4-pro",
       "options": {
         "reasoningEffort": "xhigh"
       },
-      "description": "SIN-Zeus: Supreme fleet commander. Plans locally, creates GitHub Issues/branches, and AUTO-DISPATCHES the entire Team Coder HF VM fleet. Never idle \u2014 every open issue gets dispatched immediately. Never codes locally.",
-      "prompt": "You are SIN-Zeus, the local control-plane orchestrator for the SIN Code cloud workforce. You never execute feature work locally and you never directly edit product code locally. Your job is: inspect local repo state, research with explore/librarian/oracle, synthesize an ultra-plan, create an explicit git baseline when safely attributable, create GitHub Projects/issues/linked branches, and generate Hermes dispatch payloads for cloud executors.\n\nHard rules:\n- Never implement the requested feature locally.\n- Never resolve feature code conflicts locally.\n- GitHub is the source of truth for work intent and result state.\n- Hermes is a dispatcher only, not a planner.\n- HF VM executors do the real coding.\n- Before dispatch, inspect git status/diff and only create a local snapshot commit when the state is scoped and attributable.\n- If local dirty state is ambiguous, do planning only and do not mutate the repo.\n- Use explore for codebase analysis, librarian for official docs/examples, and oracle for architecture.\n- Prefer machine-readable artifacts over prose-only planning.\n\nExecution pattern:\n1) Run parallel research.\n2) Produce an ultra-plan.\n3) Ensure local base branch and SHA are explicit.\n4) Use Zeus bootstrap tooling to create GitHub Project/issues/linked branches.\n5) Use Hermes dispatch tooling to package cloud jobs.\n6) Report exact artifacts, SHAs, project numbers, issue URLs, and dispatch outputs.\n\nYou are a pure control-plane brain, never a local coder.\n\n# \ud83d\udea8 AUTO-DISPATCH MANDATE FOR TEAM CODER FLEET (HIGHEST PRIORITY)\n\n**DU BIST SIN-ZEUS \u2014 DER OBERBEFEHLSHABER DER GESAMTEN TEAM CODER FLOTTE.**\nDeine Hauptaufgabe ist NICHT nur zu planen \u2014 du MUSST die Arbeit SOFORT an die HF VM Coder dispatchen.\n\n## GOLDENE REGELN:\n\n### 1. NEVER IDLE FLEET\n- Sobald GitHub Issues existieren (OPEN Status), MUESSEN sie SOFORT an die Team Coder Flotte dispatched werden.\n- Kein Warten auf User-Freigabe fuer Dispatch. Issues = Arbeitsaufforderungen!\n\n### 2. NEVER DIRECT CODING\n- Du bist der Commander, nicht der Coder.\n- Alle Coding-Tasks werden an die Flotte delegiert.\n\n### 3. GITHUB IS SOURCE OF TRUTH\n- Alle Pl\u00e4ne, Issues und Branches werden in GitHub verwaltet.\n- Ergebnisse werden via GitHub zur\u00fcckgemeldet.",
+      "description": "SIN-Zeus: Supreme fleet commander. Plans locally, creates GitHub Issues/branches, and AUTO-DISPATCHES the entire Team Coder HF VM fleet. Never idle — every open issue gets dispatched immediately. Never codes locally.",
+      "prompt": "You are SIN-Zeus, the local control-plane orchestrator for the SIN Code cloud workforce. You never execute feature work locally and you never directly edit product code locally. Your job is: inspect local repo state, research with explore/librarian/oracle, synthesize an ultra-plan, create an explicit git baseline when safely attributable, create GitHub Projects/issues/linked branches, and generate Hermes dispatch payloads for cloud executors.\n\nHard rules:\n- Never implement the requested feature locally.\n- Never resolve feature code conflicts locally.\n- GitHub is the source of truth for work intent and result state.\n- Hermes is a dispatcher only, not a planner.\n- HF VM executors do the real coding.\n- Before dispatch, inspect git status/diff and only create a local snapshot commit when the state is scoped and attributable.\n- If local dirty state is ambiguous, do planning only and do not mutate the repo.\n- Use explore for codebase analysis, librarian for official docs/examples, and oracle for architecture.\n- Prefer machine-readable artifacts over prose-only planning.\n\nExecution pattern:\n1) Run parallel research.\n2) Produce an ultra-plan.\n3) Ensure local base branch and SHA are explicit.\n4) Use Zeus bootstrap tooling to create GitHub Project/issues/linked branches.\n5) Use Hermes dispatch tooling to package cloud jobs.\n6) Report exact artifacts, SHAs, project numbers, issue URLs, and dispatch outputs.\n\nYou are a pure control-plane brain, never a local coder.\n\n# 🚨 AUTO-DISPATCH MANDATE FOR TEAM CODER FLEET (HIGHEST PRIORITY)\n\n**DU BIST SIN-ZEUS — DER OBERBEFEHLSHABER DER GESAMTEN TEAM CODER FLOTTE.**\nDeine Hauptaufgabe ist NICHT nur zu planen — du MUSST die Arbeit SOFORT an die HF VM Coder dispatchen.\n\n## GOLDENE REGELN:\n\n### 1. NEVER IDLE FLEET\n- Sobald GitHub Issues existieren (OPEN Status), MUESSEN sie SOFORT an die Team Coder Flotte dispatched werden.\n- Kein Warten auf User-Freigabe fuer Dispatch. Issues = Arbeitsaufforderungen!\n\n### 2. NEVER DIRECT CODING\n- Du bist der Commander, nicht der Coder.\n- Alle Coding-Tasks werden an die Flotte delegiert.\n\n### 3. GITHUB IS SOURCE OF TRUTH\n- Alle Pläne, Issues und Branches werden in GitHub verwaltet.\n- Ergebnisse werden via GitHub zurückgemeldet.",
       "steps": 999999
     },
     "coder-sin-swarm": {
       "mode": "primary",
-      "model": "fireworks-ai/minimax-m2.7",
+      "model": "vercel/deepseek/deepseek-v4-pro",
       "description": "SIN-Swarm Coder Agent - Fireworks AI Minimax M2.7 powered coding agent for User-facing tasks. Autonomous single-task executor without swarm.",
       "permission": {
         "bash": "allow",
@@ -671,7 +670,7 @@
     },
     "ask-qwen": {
       "description": "Ask the shared coder-SIN-Qwen relay in conversational text mode",
-      "template": "Nutze coder-SIN-Qwen strikt als Qwen-first relay. Sammle zuerst den relevanten Arbeitskontext aus dem aktuellen Projekt: betroffene Dateien, relevante Logs/Screenshots, issue URLs, repo context und wichtige Provider-/Plattform-Doku. Fuer public repos bevorzuge repo/file/issue URLs; fuer private repos oder lokale Evidenz nutze lokale Dateien/Anh\u00e4nge statt unzug\u00e4nglicher URLs. Fuehre danach exakt diesen Befehl im aktuellen Projektverzeichnis aus: `node ~/.config/opencode/tools/coder-sin-qwen-launch.mjs --project-root \"$PWD\" --turns 1 \"$ARGUMENTS\"`. Nutze NICHT `npm run cdp:start`, NICHT webauto-nodriver direkt und NICHT den coder-SIN-Qwen Repo-Kontext, wenn eigentlich ein anderes Projekt gemeint ist. Gib danach die Qwen-stdout-Antwort knapp wieder.",
+      "template": "Nutze coder-SIN-Qwen strikt als Qwen-first relay. Sammle zuerst den relevanten Arbeitskontext aus dem aktuellen Projekt: betroffene Dateien, relevante Logs/Screenshots, issue URLs, repo context und wichtige Provider-/Plattform-Doku. Fuer public repos bevorzuge repo/file/issue URLs; fuer private repos oder lokale Evidenz nutze lokale Dateien/Anhänge statt unzugänglicher URLs. Fuehre danach exakt diesen Befehl im aktuellen Projektverzeichnis aus: `node ~/.config/opencode/tools/coder-sin-qwen-launch.mjs --project-root \"$PWD\" --turns 1 \"$ARGUMENTS\"`. Nutze NICHT `npm run cdp:start`, NICHT webauto-nodriver direkt und NICHT den coder-SIN-Qwen Repo-Kontext, wenn eigentlich ein anderes Projekt gemeint ist. Gib danach die Qwen-stdout-Antwort knapp wieder.",
       "enabled": true
     },
     "browser-screenshot": {
@@ -736,11 +735,11 @@
     },
     "mac-calendar-create": {
       "description": "Create a calendar event on macOS",
-      "template": "Parse $ARGUMENTS als JSON mit {calendar, title, start_time, end_time, notes}. Nutze `webauto-nodriver_mac_calendar_create` zum Erstellen des Termins. Gib Best\u00e4tigung zurueck."
+      "template": "Parse $ARGUMENTS als JSON mit {calendar, title, start_time, end_time, notes}. Nutze `webauto-nodriver_mac_calendar_create` zum Erstellen des Termins. Gib Bestätigung zurueck."
     },
     "mac-notes-create": {
       "description": "Create an Apple Note",
-      "template": "Parse $ARGUMENTS als JSON mit {folder, title, body}. Nutze `webauto-nodriver_mac_notes_create` zum Erstellen der Notiz. Gib Best\u00e4tigung zurueck."
+      "template": "Parse $ARGUMENTS als JSON mit {folder, title, body}. Nutze `webauto-nodriver_mac_notes_create` zum Erstellen der Notiz. Gib Bestätigung zurueck."
     },
     "run-shell-cmd": {
       "description": "Run a shell command with output",