fix(macos): Preserve DerivedData in app path next step

Propagate an explicit derivedDataPath from build_macos into the generated get_mac_app_path next-step params. This keeps the follow-up lookup aligned with the DerivedData location used by the build, matching the existing device and simulator behavior.

Co-Authored-By: OpenAI Codex <noreply@openai.com>

Author: cameroncooke

src/mcp/tools/macos/__tests__/build_macos.test.ts

@@ -142,6 +142,12 @@ describe('build_macos plugin', () => {
 
       expect(result.isError()).toBeFalsy();
       expectPendingBuildResponse(result, 'get_mac_app_path');
+      expect(result.nextStepParams).toEqual({
+        get_mac_app_path: {
+          scheme: 'MyScheme',
+          derivedDataPath: '/path/to/derived-data',
+        },
+      });
     });
 
     it('should return exact exception handling response', async () => {

src/mcp/tools/macos/build_macos.ts

@@ -153,6 +153,9 @@ export async function buildMacOSLogic(
     ctx.nextStepParams = {
       get_mac_app_path: {
         scheme: params.scheme,
+        ...(params.derivedDataPath !== undefined
+          ? { derivedDataPath: params.derivedDataPath }
+          : {}),
       },
     };
   }