fix: ensure v2ApiClient uses shared axios instance for MCP headers

[jonathannorris]

Problem

The v2ApiClient was not using the shared axiosClient instance, causing all /v2/features API calls from the MCP server to miss the MCP identification headers (dvc-referrer and dvc-referrer-metadata).

Solution

• Updated v2ApiClient creation in src/api/apiClient.ts to use the shared axiosClient instance with validate: 'request' option
• This ensures all v2 API calls properly identify themselves as originating from the MCP server

[Copilot]

Pull Request Overview

This PR fixes an issue where the v2ApiClient was not using the shared axios instance, causing MCP server API calls to miss required MCP identification headers.

• Updated v2ApiClient creation to use the shared axiosClient instance with proper validation options
• Added test coverage to verify v2ApiClient inherits MCP headers correctly

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/api/apiClient.ts	Modified v2ApiClient creation to use shared axiosClient instance for MCP header inheritance
src/mcp/utils/api.test.ts	Added test case to verify v2ApiClient uses shared axios instance with MCP headers
src/commands/features/snapshots/update.test.ts.snap	Updated test snapshots due to JSON property ordering changes

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	devcycle-mcp-server	e5ce2e2	Oct 01 2025, 03:54 PM