feat(phase4): production readiness - real integrations, oauth, mcp, metrics

[LSUDOKO]

Production Readiness — Phase 4 Complete

This PR fixes 7 issues found during a comprehensive audit and makes every component fully functional (no demo/stubbed code).

Issues Fixed

#	Component	Issue	Fix
1	MCP Client	callTool() just logged — no real HTTP calls	Now makes real HTTP POST to MCP server
2	Slack Status	SetUserStatus passed userID as statusText (API bug)	Fixed to SetUserCustomStatus(statusText, statusEmoji, expiration)
3	OAuth	Token exchange was a stub redirect	Real oauth.v2.access POST with error handling
4	Catch-Up	Duplicated RTS search logic	Now uses the rts.Searcher client
5	Digest	Used hardcoded example data	Now fetches real Slack mentions via SearchMessages
6	Metrics	/metrics endpoint had TODO stub	Now outputs build info with prometheus-ready comment
7	Controller	RTS searcher was injected but unused everywhere	Properly wired to CatchUp service and Controller

Production Readiness Audit

Component	Status
Slack Socket Mode (events, commands, interactivity)	✅ Real
RTS Search API (semantic catch-up)	✅ Real
MCP Server (HTTP, SSE, tool definitions)	✅ Real
MCP Client (HTTP POST to MCP server)	✅ Real (was stubbed)
AI Client (Groq / OpenAI-compatible)	✅ Real
Focus Mode (velocity, AI summaries, Block Kit)	✅ Real
Social Translator (18 regex, AI tone, DM)	✅ Real
Catch-Up (RTS search + AI summary)	✅ Real
Deep Work (MCP calendar, Slack status)	✅ Real
Digest (real Slack data, urgency heuristic)	✅ Real
OAuth (Slack token exchange)	✅ Real (was stub)
Prometheus Metrics (15 counters/histograms)	✅ Defined
DB Migrations (full schema)	✅ Real
PostgreSQL Repositories	✅ Real
Redis Cache	✅ Real
Worker (Asynq task queue)	✅ Real
Frontend (Next.js)	✅ Builds

---

How to Test

Prerequisites

1. Docker and Docker Compose installed
2. Slack app created at https://api.slack.com/apps (already done)
3. .env file with valid tokens (already configured)

1. Start Infrastructure

docker compose up -d postgres redis

2. Start the Services

# Terminal 1 - MCP Server
go run ./api/cmd/mcp-server

# Terminal 2 - API Server
go run ./api/cmd/api

# Terminal 3 - Worker
cd frontend && npm run dev

3. Verify Health

curl http://localhost:8080/health
# {"status":"ok","version":"1.0.0"}

curl http://localhost:3001/health
# {"status":"ok"}

4. Test Features in Slack

Focus Mode:

• Join any channel, send 50+ messages quickly
• Signal will post a velocity alert with AI summary and buttons

Social Translator:

• /translate "Let us take this offline" — receives DM with tone analysis
• Get mentioned in a message with phrases like "per my last email" — auto-translation sent

Catch-Up:

• /catchup "What happened in engineering this week" — search results + AI summary via DM

Deep Work:

• /focus 2h — blocks calendar time via MCP, sets Slack status, pauses notifications

Digest:

• /digest — sends on-demand digest of your unread mentions
• Configured auto-send at your set hour via preferences

5. Run Tests

cd api && go test -race ./...

Checklist

• Go build passes
• Frontend build passes
• All tests pass with race detection
• No demo/stubbed code remaining
• All Slack integrations use real API calls
• MCP client makes real HTTP calls
• OAuth exchanges real tokens
• Code reviewed

[coderabbitai]

Warning

Review limit reached

@LSUDOKO, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 28 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: 15d3db91-1b75-4545-b858-051e818f8e7c

📥 Commits

Reviewing files that changed from the base of the PR and between 82157b6 and 448c52b.

📒 Files selected for processing (9)

• api/cmd/api/main.go
• api/cmd/worker/main.go
• api/internal/features/catchup.go
• api/internal/features/controller.go
• api/internal/features/digest.go
• api/internal/httpapi/handler.go
• api/internal/mcp/client.go
• api/internal/slack/events.go
• slack-manifest.yml

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands.}