feat: Add comprehensive LLM exchange logging

[gary-van-woerkens]

• Add LLMLogEntry interface for structured logging
• Implement configurable log levels: disabled, metadata, truncated, full
• Add logLLMRequestSent, logLLMResponseReceived, logLLMRequestFailed functions
• Integrate logging in line-comments-sender with automatic timing and token tracking
• Add LOG_LLM_EXCHANGES environment variable for configuration
• Include comprehensive tests for all logging levels and scenarios
• Update README with complete logging documentation and security considerations
• Add .env.example configuration for the new logging feature

This enables full visibility into LLM exchanges while maintaining security and performance controls.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[revu-bot]

An error occurred: Error processing line comments: Invalid analysis format: [
{
"expected": "array",
"code": "invalid_type",
"path": [
"comments"
],
"message": "Invalid input: expected array, received string"
}
]

Revu logs

[tokenbureau]

🎉 Deployment for commit 5b1d04d :

Ingresses

• 🚀 https://revu.fabrique.social.gouv.fr/

Docker images

• 📦 docker pull harbor.fabrique.social.gouv.fr/fabrique/revu/app:v1.11.0

Debug

• 📕 Loki logs for namespace revu
• 📈 Pods monitoring for namespace revu
• 📈 Workloads monitoring for namespace revu

[roomote-v0]

Rooviewer   See task on Roo Cloud

Review completed. Found 2 issues that need attention:

• Missing PR context in LLM logging calls
• Invalid YAML syntax in Kubernetes ConfigMap

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[roomote-v0]

The LLM logging functions are called without PR context (pr_number, repository), even though this information is available in the call chain. The sendToAnthropic function receives a PlatformContext containing prNumber, repoOwner, and repoName, but this context isn't passed to lineCommentsSender. This makes it difficult to correlate LLM logs with specific PRs in production environments where multiple PRs may be processed concurrently.

_{Fix it with Roo Code or mention @roomote and request a fix.}

[roomote-v0]

These comment lines use # which is invalid YAML syntax within the data section of a ConfigMap. YAML comments must be outside of string values or the ConfigMap will fail to parse during deployment. Either remove these lines or move them outside the data section as proper YAML comments.

Suggested change

	REPOSITORY_FOLDER: "/app/repos"
	LOG_LLM_EXCHANGES: "full"
	#LOG_LLM_EXCHANGES=metadata # production mode
	#LOG_LLM_EXCHANGES=truncated # quick review
	#LOG_LLM_EXCHANGES=full # full LLM data
	#LOG_LLM_EXCHANGES=disabled # no LLM logs
	# Configuration options for LOG_LLM_EXCHANGES:
	# - metadata: production mode (logs only metadata)
	# - truncated: quick review (logs metadata + truncated content)
	# - full: full LLM data (logs complete prompts and responses)
	# - disabled: no LLM logs
	data:
	REPOSITORY_FOLDER: "/app/repos"
	LOG_LLM_EXCHANGES: "full"

_{Fix it with Roo Code or mention @roomote and request a fix.}