feat: Add AI-powered issue triage and PR review bot

[sudsali]

Summary

Adds a GitHub Actions bot that automatically triages issues and reviews PRs using Amazon Bedrock. Runs on issue open/reopen, issue comments, and PR open/reopen/synchronize events.

Issue Handling

• Classifies issues (bug, question, feature request, off-topic) using a two-phase LLM call
• First pass classifies and selects source files to read; second pass responds with full code context
• Follows up on user replies (capped at 2 bot replies per issue)
• Detects user dissatisfaction and escalates to maintainers via Slack
• Escalates reopened issues directly to Slack
• Labels issues automatically

PR Review

• Posts inline review comments on specific diff lines via GitHub review API
• Validates line numbers against diff hunks before submitting
• Uses REQUEST_CHANGES when findings exist
• Re-reviews on new commits (synchronize trigger)
• Reads existing review comments to avoid duplicates

Architecture

GitHub Event → Job 1: analyze (read-only, AWS creds)
                ├── Load KB from S3
                ├── Generate codebase map
                ├── Fetch issue/PR + comments
                ├── Bedrock Converse API (system prompt cached, user content guarded)
                ├── Structured JSON output
                ├── Sanitize output
                └── Write JSON artifact
              → Job 2: act (write-only, no AWS creds)
                ├── Post comment/review to GitHub
                ├── Add labels
                └── Notify Slack

Security

• Bedrock Guardrails — prompt injection detection + sensitive info blocking (replaces regex-based sanitizer)
  Trusted/untrusted split — instructions + KB + diffs go in system prompt (cached, not scanned); user-authored content (issue title/body, PR title/body, comments) wrapped in guardContent and scanned by guardrail
  Template injection prevention — per-invocation UUID-token rendering prevents cross-variable injection
• Two-job architecture — read-only analyze job (AWS creds, no GitHub write), write-only act job (GitHub write, no AWS creds)
• Fork PR blocking — fork PRs are not processed
• Output sanitization — backup injection markers + #N references wrapped in backticks to prevent auto-linking

Files

File	Purpose
issue-bot.yml	GitHub Actions workflow
main.py	Two-phase orchestrator (analyze/act)
config.py	Environment variable loading + allowed labels
bedrock_client.py	Bedrock Converse API with prompt caching, guardrails, structured output, circuit breaker
github_client.py	GitHub API + local file reads + codebase map + diff line validation
knowledge_base.py	S3-backed KB with relevance truncation
slack_client.py	Slack webhook notifications
sanitizer.py	Backup injection blocking + issue ref formatting
prompts.py	Prompt loading from env vars
schemas/*.json	JSON schemas for structured LLM output (issue, PR review, followup)
tests/test_bot.py	57 unit tests for parsing, validation, and sanitization

Required GitHub Secrets

AWS_ROLE_ARN, KB_S3_BUCKET, KB_S3_KEY, BEDROCK_MODEL_ID, GUARDRAIL_ID, GUARDRAIL_VERSION, SLACK_WEBHOOK_URL, ISSUE_CLASSIFY_PROMPT, ISSUE_RESPOND_PROMPT, PR_FILE_REVIEW_PROMPT, FOLLOWUP_PROMPT

Testing

Supports workflow_dispatch with dry_run: true. Tested on the fork against bug reports, usage questions, feature requests, follow-ups, dissatisfaction escalation, prompt injection, duplicate runs, PR inline reviews, and re-reviews on new commits.

Tested with various Issues:

• VerificationSuite crashes with Py4JJavaError on Spark 3.3 sudsali/python-deequ#13
• How to serialize PyDeequ check results to JSON for downstream processing? sudsali/python-deequ#14
• How do I run ColumnProfiler on a subset of columns? sudsali/python-deequ#15
• Bug in VerificationSuite - please read carefully before responding sudsali/python-deequ#18

Tested on PR:

• Spark4 support sudsali/python-deequ#17

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[SamPom100]

nit: would be nice to have testing evidence in the PR description