Follow-up from #374 (Copilot review). The git handler at `src/handlers/git.js` has no automated test coverage — the recent #371 (CORS) and #373 (multi-slash) fixes were verified by hand with curl + a local boot.

Suggested coverage

• `OPTIONS` preflight returns the canonical CORS headers (`Content-Type, Authorization, Git-Protocol`)
• Single-slash `info/refs?service=git-upload-pack` → 200 with `application/x-git-upload-pack-advertisement`
• Double-slash `//info/refs` → 200 (regression for git handler: 500 on double-slash in URL (PATH_INFO not normalized) #373)
• Triple-slash `///info/refs` → 200
• Missing repo → 404 with CORS headers (regression for the git handler: collapse multi-slash in URL before forwarding to http-backend (#373) #374 follow-up)
• Path traversal attempt → 403 with CORS headers
• Push (POST `git-receive-pack`) without auth → 401 with CORS headers
• Push with auth → 200 (or 200 + receive-pack output)

Shape

Probably an integration test along the lines of `test/idp.test.js` — boot a temp `createServer({ git: true, public: true, root: tmpDir })`, init a bare repo at `tmpDir/repo.git`, hit it with `fetch`. Already a working pattern in this repo for HTTP-level tests.

Refs

• git handler: allow git-protocol header in CORS preflight responses #371 — Git-Protocol CORS header
• git handler: 500 on double-slash in URL (PATH_INFO not normalized) #373 — multi-slash 500
• git handler: collapse multi-slash in URL before forwarding to http-backend (#373) #374 — the PR that closed git handler: 500 on double-slash in URL (PATH_INFO not normalized) #373