Merge pull request #2 from sourcegraph/sayans/refactor-job-processing

refactor: remove installation id from disk. add zod schemas, add bounded queue executor, remove extra tools causing issues

Author: karlclement

.gitignore

@@ -44,4 +44,7 @@ data/
 
 # Keys
 *.pem
-*.key
+*.key
+
+# Test files
+test_*.sh

README.md

@@ -224,9 +224,6 @@ The app includes a Model Context Protocol (MCP) server that exposes GitHub opera
 ### Available MCP Tools
 - `leave_general_comment` - Leave general comments on pull requests
 - `leave_inline_comment` - Leave inline comments on specific lines
-- `create_check_run` - Create or update check run status
-- `get_pr_info` - Get pull request details and optionally the diff
-- `trigger_review` - Start the code review process
 - `get_pr_comments` - Get all comments on a pull request
 
 ### Usage with AI Agents

config.yml

@@ -57,7 +57,6 @@ amp:
     1. Look at the pull request details to fetch the context before reviewing.
     2. Review the diff content to identify issues.
     3. Leave specific inline comments or code suggestions for each issue found.
-    4. Create check run status when the code review is complete.
 
     Always leave actionable, specific comments with suggested fixes.
 
@@ -129,28 +128,6 @@ amp:
         - "Required: message, owner, repo, pr_number, path, line"
         - "Optional: commit_sha (will be fetched from PR if not provided)"
         - "Example: Comment on line 25 of src/auth.js about missing error handling"
-    - name: create_check_run
-      description: Create or update GitHub check run status
-      instructions: 
-        - "Use to mark review completion with check run status"
-        - "Required: owner, repo, commit_sha, status ('queued', 'in_progress', 'completed')"
-        - "Optional: conclusion ('success', 'failure', 'neutral'), title, summary, details_url"
-        - "Use 'completed' status with 'success' conclusion when review is done"
-        - "Use 'completed' status with 'failure' conclusion for critical issues"
-    - name: get_pr_info
-      description: Get pull request details
-      instructions: 
-        - "Use to understand context about the pull request before reviewing the diff"
-        - "Required: owner, repo, pr_number"
-        - "Optional: include_diff (boolean) to also fetch the diff content"
-        - "Returns PR info, repository info, and optionally diff content"
-    - name: trigger_review
-      description: Start code review process
-      instructions: 
-        - "Usually called automatically, but available if needed to retrigger code review"
-        - "Required: owner, repo, pr_number"
-        - "Optional: commit_sha, force (boolean)"
-        - "Creates check run and initiates review process"
     - name: get_pr_comments
       description: Get all comments on a pull request
       instructions: 

package.json

@@ -31,7 +31,8 @@
     "js-yaml": "^4.1.0",
     "jsonwebtoken": "^9.0.2",
     "node-fetch": "^3.3.2",
-    "uuid": "^10.0.0"
+    "uuid": "^10.0.0",
+    "zod": "^3.25.76"
   },
   "devDependencies": {
     "@types/js-yaml": "^4.0.9",