[log] Add debug logging to internal/guard/context.go

[github-actions]

Summary

Enhanced internal/guard/context.go with debug logging to improve visibility into security context management and agent ID tracking.

Changes Made

Added debug logger with namespace guard:context and logging calls to 5 key functions:

1. GetAgentIDFromContext - Logs when agent ID is retrieved or defaults to "default"
2. SetAgentIDInContext - Logs when agent ID is stored in context
3. ExtractAgentIDFromAuthHeader - Logs deprecated path usage and extracted agent ID
4. GetRequestStateFromContext - Logs when request state is retrieved or not found
5. SetRequestStateInContext - Logs when request state is stored in context

Benefits

• Debugging: Traces agent ID flow through security context
• Visibility: Shows when deprecated authentication paths are used
• Troubleshooting: Helps diagnose authentication and authorization issues
• Monitoring: Provides insight into state management operations

Testing

The logging follows project guidelines from AGENTS.md:

• ✅ Uses pkg:filename naming convention (guard:context)
• ✅ No side effects in log arguments
• ✅ Meaningful messages for debugging
• ✅ Reuses existing logger infrastructure pattern

Enable with: DEBUG=guard:* ./awmg --config config.toml

Quality Checklist

• ✅ Exactly 1 file modified (focused PR)
• ✅ No test files modified
• ✅ Logger naming follows pkg:filename convention
• ✅ Logger arguments don't compute or cause side effects
• ✅ Messages are meaningful and helpful
• ✅ No duplicate logging
• ✅ Import statements properly formatted

AI generated by Go Logger Enhancement