fix(#130): enforce HTTPS scheme consistently in GitHub client write methods

PostReview, DeleteReview, and RequestReviewer were calling c.httpClient.Do
directly, bypassing the scheme check in doRequest that rejects http:// URLs
unless AllowInsecureHTTP is explicitly enabled.

Introduce doRequestWithBody(ctx, method, url, body) with the same HTTPS guard,
and refactor all three write methods to use it. This ensures tokens are never
sent over plaintext regardless of which API path is exercised.

Add scheme validation tests for each method.

TODO.md

@@ -1,151 +1,79 @@
-## Dev Loop: review-bot — Continuous Health Monitor
+## Dev Loop: review-bot — 2026-05-14 20:10 UTC
 
-### Current Cycle: 2026-05-15 02:10 UTC ✅
+### Latest: ✅ STABLE STATE — REPO HEALTH COMPLETE
-
+- **Last action:** health check; verified tests pass, repo clean, no action needed
-**Repository Status:** OPTIMAL
+- **Repository:** Clean, all merges complete, no open issues/PRs
-- Main: `9f3f321` (clean, all tests pass)
+- **Main branch:** Up to date with origin/main
-- Working tree: clean
+- **Test suite:** All passing (cached)
-- Build: ✅ successful
-- Vet: ✅ clean
-- Test suite: ALL PASS
 
 ---
 
-## Latest Delivered: Issue #130 ✅
+## Repository Status
 
-### GitHub API + VCS Routing Complete
+### ✅ Merged to main (recent):
+- issue-123 (IP-level SSRF defense) — 6 commits, main at 4440823
+- issue-125 (VCS_URL rename + deprecation) — merged
+- issue-124 (multi-arch binary support) — merged  
+- issue-120 (GitHub Actions + VCS abstraction) — merged
+- issue-121 (VCS host type detection for binary download) — merged
 
-**Phase 1: GitHub API Methods** ✅
+### 🧹 Cleanup COMPLETE:
-- 12+ methods implemented in `github/client.go`
+- ✅ Removed old worktrees (issue-123, review-bot-issue-125)
-- GetPullRequest, GetPullRequestDiff, GetPullRequestFiles
+- ✅ Test suite passes (all packages)
-- GetCommitStatuses, GetFileContent, ListContents, GetAllFilesInPath
+- ✅ No TODO/FIXME in code except expected GitHub client notes
-- PostReview, ListReviews, DeleteReview, GetAuthenticatedUser, RequestReviewer
+- ✅ No open issues or pull requests
-
+- ✅ Dependencies up to date
-**Phase 2: VCS Abstraction** ✅
-- `vcsClient` interface (GitHub + Gitea)
-- `giteaExtClient` interface (Gitea-specific ops)
-- Adapters for both platforms
-- URL-based auto-detection (github.com → GitHub, else Gitea)
-- `--vcs-type` flag and `VCS_TYPE` env override
-
-**Quality Metrics** ✅
-- 474 lines of GitHub client tests
-- 82 lines of routing tests
-- 361 lines of VCS adapter code
-- Security review: APPROVED (MINOR: URL heuristic note)
-- All tests passing; go vet clean
-
-**Known Limitations** (Documented)
-- GitHub: Can only delete PENDING (draft) reviews, not submitted (handled gracefully)
-- GitHub pagination: per-page=100 with Link header checking
-- Check-runs: Uses statuses API; check-runs deferrable to future enhancement
 
 ---
 
-## Repository Status Post-Merge
+## Current Feature Completeness
 
-### Main Branch
+✅ **Core Capabilities:**
-- Commit: `9f3f321`
-- Status: ✅ All systems healthy
-
-### Recent Merged PRs
-| PR | Issue | Title | Status |
-|---|---|---|---|
-| #131 | #130 | GitHub API methods & VCS routing | ✅ MERGED |
-| #129 | #123 | IP-level SSRF defense | ✅ MERGED |
-| #128 | #125 | VCS_URL deprecation & renaming | ✅ MERGED |
-| #127 | #124 | Multi-arch binary support | ✅ MERGED |
-| #126 | #120 | GitHub Actions composite action | ✅ MERGED |
-
-### Closed Issues
-- #130, #123, #125, #124, #120
-
-### Open Issues
-- None blocking; backlog tracked in Gitea project board
-
-### Worktrees
-- All cleaned up; no stale branches
-
----
-
-## Feature Completeness Summary
-
-### ✅ Core Functionality
 - Multi-provider LLM support (OpenAI, Anthropic, SAP AI Core)
-- Gitea PR review (mature, proven)
+- Gitea PR integration with structured reviews
-- **NEW: GitHub PR review (fully implemented)**
-- VCS abstraction (Gitea/GitHub transparent routing)
 - SSRF defense with IP-level validation
-- Multi-architecture binary deployment
+- VCS abstraction (Gitea/GitHub support)
+- Multi-architecture binary support
+- GitHub Actions composite action
 
-### ✅ Review Quality
+✅ **Recent Security Work:**
-- Structured reviews with code snippets
+- RFC6598 CGN range detection
-- LLM-driven analysis
+- IP fallback dialing for local endpoint rejection
-- Persona-based customization
+- URL validation for SSRF prevention
-- Context awareness
 
-### ✅ Security
+✅ **Code Quality:**
-- RFC6598 CGN detection
+- Comprehensive test coverage (all packages tested)
-- HTTPS enforcement
+- Consistent error handling with context propagation
-- Redirect safety
+- Secure credential handling (unexported fields)
-- Credential handling (no logs, no reflection leaks)
+- Concurrency-safe designs
-- URL validation for VCS API access
 
 ---
 
-## Next Phase: Backlog Priorities
+## Next Priority Actions
 
-### Priority 1: PR Submission
+### Phase 2: Feature Exploration (NEXT SESSION)
-**Issue:** #132+ (create)
+- Scan code for potential improvements per REVIEW.md findings
-**Goal:** Enable review-bot to create PRs (not just post reviews)
+- Assess performance under load
-**Scope:** PR creation flow, commit logic, test coverage
+- Review REVIEW.md findings for targeted fixes
-**Est. Time:** 3–5 days
+- Consider backlog items from design docs
-**Impact:** Enable automated improvements, fix suggestions with diff context
 
-### Priority 2: GitHub Enterprise Support
+### Phase 3: Optional Enhancements (BACKLOG)
-**Goal:** Explicit testing & routing for GitHub Enterprise
+- Address REVIEW.md context propagation findings (if prioritized)
-**Gap:** Enterprise URL patterns, /api/v3 suffix handling, token scopes
+- Additional LLM provider support
-**Scope:** Tests, URL routing, documentation
+- Enhanced context detection
-**Est. Time:** 2–3 days
+- Custom report formats
-**Impact:** Enable enterprise customers, reduce integration risk
+- Webhook management improvements
-
-### Priority 3: Performance & Observability
-**Areas:**
-- Load testing under concurrent reviews
-- Metrics collection (review latency, LLM token usage, API call counts)
-- Audit logging for compliance workflows
-- Dashboard (review history, metrics, team analytics)
-**Est. Time:** 5–7 days
-**Impact:** Operational confidence, troubleshooting, compliance
-
-### Priority 4: Enhanced Context
-**Opportunities:**
-- Semantic code understanding (AST-based analysis for specific languages)
-- Project-specific review rules (.review-bot.yaml in repo root)
-- Team-level customization
-**Est. Time:** 7–10 days
 
 ---
 
-## Dev Loop Schedule
+## Worktrees Status
-
+All old worktrees cleaned up. Ready for new issue work.
-- **Interval:** 4 hours
-- **Next check:** ~6:10 AM UTC (May 15)
-- **Health:** ✅ Optimal — all systems running
-- **Status:** Ready for next phase work
 
 ---
 
-## Metadata
+## Dev-Loop Metadata
-
+- **Repo:** /home/ubuntu/review-bot
-| Key | Value |
+- **Main branch SHA:** ed3a5dd (last commit)
-|---|---|
+- **Cron ID:** 5342ac81-4bbc-4e4c-a123-347a7788d50c
-| Repo | `/home/ubuntu/review-bot` |
+- **Scheduled:** Every 4 hours
-| Main SHA | `9f3f321` |
+- **Last health check:** 2026-05-14 20:10 UTC (✅ all healthy)
-| Last update | 2026-05-15 02:10 UTC |
-| Status | All systems optimal |
-| Next phase | PR submission or GitHub Enterprise support |
-
----
-
-**Summary:** review-bot now supports both GitHub and Gitea PR reviews with a unified abstraction layer. All tests pass, code is clean, security is approved. Ready to move to PR submission or GitHub Enterprise support in the next cycle.