[Repo Assist] fix(server): migrate guard_init.go DIFC logs to structured logger

[github-actions]

🤖 This PR was created by Repo Assist, an automated AI assistant.

Summary

Replaces all 24 log.Printf("[DIFC] ...") calls in internal/server/guard_init.go with logger.LogInfo/LogWarn/LogError calls so DIFC guard-initialization events are captured in mcp-gateway.log and per-server log files.

Closes #4175

Root Cause

guard_init.go used the standard library log.Printf with a manually-embedded [DIFC] prefix. These calls write only to stderr and are silently dropped from all log files (mcp-gateway.log, per-server .log files, gateway.md). The companion file difc_log.go already used logger.LogInfoWithServer correctly, making guard_init.go inconsistent.

Changes

• Remove "log" import — replaced entirely by the logger package already imported
• 24 call sites migrated:
  • "[DIFC] WARNING:" prefixed → logger.LogWarnWithServer(serverID, "difc", ...) / logger.LogWarn
  • Plain "[DIFC]" → logger.LogInfoWithServer(serverID, "difc", ...) / logger.LogInfo
  • Error path (label_agent failed, nil result) → logger.LogErrorWithServer
  • Redundant server='%s' / server=%s removed from format strings where the WithServer variant already carries the server ID

Impact

After this change, all DIFC guard-initialization events (guard registration, policy loading, label_agent calls and responses) are visible in:

• mcp-gateway.log (unified log)
• {serverID}.log (per-server log)
• gateway.md (markdown log for workflow previews)

Test Status

The environment has Go 1.24.13; the module requires Go 1.25.0 (network-restricted — toolchain download blocked). Build and tests could not be run locally. CI will provide authoritative results.

The change is a mechanical rename: same function calls, same arguments, same conditional structure. No logic has changed. Existing unit tests in internal/server/ cover the code paths through the migrated functions.

Warning

⚠️ Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• proxy.golang.org

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "proxy.golang.org"

See Network Configuration for more information.

Generated by Repo Assist · ● 6.2M · ◷

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@851905c06e905bf362a9f6cc54f912e3df747d55

[Copilot]

Pull request overview

Migrates DIFC guard-initialization logging in guard_init.go from log.Printf("[DIFC] ...") to the repository’s structured logger so events are emitted to the unified and per-server log files.

Changes:

• Removed the log import from internal/server/guard_init.go.
• Replaced DIFC-prefixed log.Printf calls with logger.LogInfo/LogWarn/LogError (and *WithServer) equivalents under category "difc".
• Reduced redundancy in log message formats by relying on WithServer for server context.

Show a summary per file

File	Description
internal/server/guard_init.go	Replaces DIFC log.Printf calls with structured logger calls to route messages into file-based logging.

Copilot's findings

Tip

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

• Files reviewed: 1/1 changed files
• Comments generated: 1

[Copilot]

Switching logServerGuardPolicies from log.Printf to logger.LogInfoWithServer changes the observable output: when the global file/server loggers aren’t initialized (common in unit tests), these calls are no-ops and nothing is written to the standard logger. Existing tests that capture log output for this function will fail and should be updated to initialize the logger (e.g., logger.InitFileLogger + logger.InitServerFileLogger) and assert on the generated log files / unified log content instead.

[lpcox]

@copilot address the review feedback #4191 (review)