[log] Add debug logging to container detection in sys/container.go

[github-actions]

Summary

Adds a package-level debug logger (logSys) and 4 meaningful debug log calls to internal/sys/container.go, following the project's pkg:filename naming convention from AGENTS.md.

Changes

File modified: internal/sys/container.go

What was added

1. Import for github.com/github/gh-aw-mcpg/internal/logger
2. Package-level logger variable: var logSys = logger.New("sys:container")
3. Debug log at function entry: "Detecting container environment"
4. Detection method trace logs for each of the 3 detection paths:
   • "Container detected via /.dockerenv" (Method 1)
   • "Container detected via /proc/1/cgroup" (Method 2)
   • "Container detected via RUNNING_IN_CONTAINER env var" (Method 3)
5. Fallback log: "No container indicators found, running on host"

Why this is useful

IsRunningInContainer() is a critical detection function used to determine execution context and control security behavior (e.g., whether direct command execution is permitted). When troubleshooting container detection issues, developers had no visibility into which detection method triggered (or why detection failed). With this change, running DEBUG=sys:* ./awmg --config config.toml reveals exactly which method fires.

Quality checklist

• Exactly 1 file modified
• No test files modified
• Logger declaration added following pkg:filename convention (sys:container)
• Log arguments are all string literals (no side effects)
• Messages are meaningful and actionable for debugging
• No duplicate logging with existing logs
• Import statements properly formatted
• Naming follows project convention (logSys matches logConn, logSchema, etc.)

Generated by Go Logger Enhancement · ◷

[Copilot]

Pull request overview

Adds targeted debug logging to sys.IsRunningInContainer() to make container detection decisions observable via the project’s DEBUG-controlled logger namespaces.

Changes:

• Introduces a package-level debug logger for internal/sys/container.go.
• Logs container detection flow at function entry, on each positive detection path, and on the “no indicators found” fallback.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Logger variable name logSys is not very descriptive in the sys package and deviates from the documented convention to use log<Component> names matching the component (e.g., logLauncher, logValidation). Consider renaming this to something like logContainer (or similar) to make its purpose clear and reduce ambiguity when grepping logs.