Use and preserve server.json wherever it is found

[AArnott]

No description provided.

[AArnott]

@timheuer can you download the build artifacts and give this a try before I merge it?

[timheuer]

Something definitely not working still...here's what I'm seeing (reflected in this run: https://github.com/timheuer/SampleDotnetMcpServer/actions/runs/17834480394)

pack is successful, but the resulting nuget package does NOT include the stamped JSON correctly (the artifact is in the run). I added a debug step and don't even see the nb.gv\server.json file in the obj directory at all. HOWEVER on local windows runs I do see that being output. Linux thing?

UPDATE: using either a linux/windows runner on GHA I don't see the obj resource there at all. When running locally I do...no idea.

Okay, a .NET SDK target was preventing the logic from working correctly and it is required that .NET 10 SDK is used for the new PackageType. After resolving that, the flow works, I can confirm this change works as expected now!

[AArnott]

Okay, a .NET SDK target was preventing the logic from working correctly and it is required that .NET 10 SDK is used for the new PackageType. After resolving that, the flow works

@timheuer Which target was it? Is it something NB.GV needs to accommodate or was it unique to your situation?

[timheuer]

Which target was it?

I think I deleted that binlog -- it was basically seeing the McpServer package type as invalid and re-classifying it only as DotnetTool and thus the target didn't run. It makes sense to require NET10 here though as the underlying package support in the runtime to execute the MCP server from dnx requires NET10 anyway. I'm fine with that requirement...was just a miss on my part and locally I had net10 which is why 'everything working fine' was confusing me.

[AArnott]

Great. Thank you for testing.