Adds clojure agent

.envrc

@@ -1 +1,2 @@
 export OPENROUTER_API_KEY=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
+export AWS_PROFILE=integreat

opencode.json

@@ -1,5 +1,11 @@
 {
   "$schema": "https://opencode.ai/config.json",
+  "agent": {
+	  "clojure-author": {
+		  "prompt": "You are an expert Clojure developer. Follow these rules:\n\nStructural Editing: Use the clojure-mcp tools for all code changes. When editing clojure, you may only use clojure_edit, clojure_edit_replace_sexp, file_edit, file_write, for modifications from the clojure mcp server. You should also prefer to use read_file from the clojure mcp server. Never use\n sed, Write, or raw text replacement for Clojure files. Use clj-repair-parens (via clojure_mcp_paren_repair) whenever a file has unbalanced delimiters\n before making other edits.\n Code Style: Write pure functions by default. Avoid side effects, mutable state, and overly clever code. Favor let bindings over nested calls. Keep\n functions small and composable.\nKnowledge: When you need to verify a library API, standard library behavior, or Clojure semantics, consult context7 first. Use web search as a\n fallback when context7 lacks coverage.\n Evaluation: Use clojure_mcp_clojure_eval to test expressions and verify behavior before suggesting code changes.",
+		  "permission": {"edit": "deny", "bash": "deny"}
+	  }
+  },
   "command": {
     "resolve_pr_parallel": {
       "description": "Resolve all PR comments using parallel processing",
@@ -108,7 +114,11 @@
       "url": "https://mcp.context7.com/mcp",
       "enabled": true
     },
-  
+   "clojure-mcp": {
+      "type": "local",
+      "command": ["clojure", "-Tmcp", "start", ":config-profile", ":cli-assist"],
+      "enabled": true
+    } 
   },
   "permission": {
     "read": "allow",