[log] proxy/handler: add debug logging to forwardAndReadBody and writeEmptyResponse

[github-actions]

Adds 5 logHandler calls to two previously-unlogged helper functions in the DIFC proxy pipeline.

Changes

forwardAndReadBody (4 new log calls):

• Entry: logs method and path so every upstream request is traceable
• Upstream error: logs method, path, and error when forwardToGitHub fails (previously only a 502 was emitted with no diagnostics)
• Body-read error: logs method, path, status, and error if io.ReadAll fails mid-stream
• Success: logs method, path, response status, and body length

writeEmptyResponse (1 new log call):

• Logs which empty JSON shape ([], {"data":null}, or {}) was selected and the upstream status code — useful when DIFC policy filters items and callers receive an empty response

Why these functions?

forwardAndReadBody is called from every code path in handleWithDIFC. Before this change, a GitHub API failure appeared in logs only as a generic 502 with no indication of which method/path was involved or whether the failure was during the HTTP call or while reading the body. writeEmptyResponse is similarly opaque: there was no log entry explaining why a DIFC-filtered response took a particular empty shape.

Validation

• go build -o awmg . ✅
• go vet ./... ✅
• go test ./... ✅ (all packages pass)
• Reuses existing logHandler = logger.New("proxy:handler") — no new logger declaration needed
• No side effects in log arguments

Warning

Firewall blocked 1 domain

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

• index.crates.io

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

network:
  allowed:
    - defaults
    - "index.crates.io"

See Network Configuration for more information.

Generated by Go Logger Enhancement · sonnet46 14M · ◷

[Copilot]

Pull request overview

Adds debug-level trace logging to previously opaque helper functions in the DIFC proxy handler, improving diagnosability of upstream request failures and empty-response shaping without changing proxy behavior.

Changes:

• Add debug logs to forwardAndReadBody for entry, upstream-call failure, body-read failure, and success summary.
• Add debug log to writeEmptyResponse to record the selected empty JSON shape and upstream status.

Show a summary per file

File	Description
internal/proxy/handler.go	Adds debug logging in forwardAndReadBody and writeEmptyResponse to improve request/response traceability in the proxy pipeline.

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