Support gh CLI /meta probe in DIFC proxy

[Copilot]

gh initializes by calling GET /meta (via GH_HOST as /api/v3/meta). The proxy treated /meta as an unknown REST route and returned 403, which broke workflows running gh commands in pre-agent steps.

• Request handling

  • Added an explicit fast-path in proxyHandler.ServeHTTP for GET /meta.
  • Requests are forwarded upstream unchanged (after existing GH_HOST prefix stripping), instead of entering REST route matching and being fail-closed.

• Behavioral coverage

  • Added a focused handler test for /api/v3/meta to assert passthrough behavior and upstream path normalization to /meta.

// gh CLI probes /meta during initialization for feature detection.
if r.Method == http.MethodGet && rawPath == "/meta" {
    h.passthrough(w, r, fullPath)
    return
}

[Copilot]

Pull request overview

Adds a /meta passthrough path in the DIFC proxy so gh CLI startup probes are forwarded to GitHub instead of being blocked as unknown REST reads.

Changes:

• Handles GET /meta after /api/v3 prefix normalization.
• Adds a handler test covering /api/v3/meta passthrough and upstream path normalization.

Show a summary per file

File	Description
internal/proxy/handler.go	Adds the /meta fast-path passthrough before DIFC REST route matching.
internal/proxy/handler_test.go	Verifies GET /api/v3/meta reaches upstream as /meta and returns the upstream response.

Copilot's findings

Tip

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

• Files reviewed: 2/2 changed files
• Comments generated: 0