conformance

Background This repository contains conformance tests for MCP clients and MCP servers. However, there are currently no conformance tests for authorization servers. It may be because conformance tests for authorization servers may have low priority, but they are necessary. First Step Implementing conformance tests for authorization servers involves multiple steps. Therefore, as a first step, this issue focuses on implementing a test for OAuth 2.0 Authorization Server Metadata RFC8414.

Motivation and Context Two issues prevented client conformance tests from running on Windows: 1. Single-quote quoting in execSync: The --command argument was wrapped in single quotes, which cmd.exe treats as literal characters rather than string delimiters. This caused the CLI to receive only the first word of the command. Switched to execFileSync with an args array to bypass shell quoting entirely. 2. Backslash path separators in parseOutputDir: dirname() on Windows returns auth\scenario-name but reconcileWithExpected compares against auth/scenario-name, causing auth scenarios to be double-counted. Normalize backslashes to forward slashes in parsed scenario names. How Has This Been Tested? Re-running the assessment with these changes staged locally. Breaking Changes No Types of changes [x] Bug fix (non-breaking change which fixes an issue) [ ] New feature (non-breaking change which adds functionality) [ ] Breaking change (fix or feature that would cause existing functionality to change) [ ] Documentation update Checklist [x] I have read the MCP Documentation [x] My code follows the repository's style guidelines [x] New and existing tests pass locally [x] I have added appropriate error handling [x] I have added or updated documentation as needed Additional context Encountered when running the assessment for the C# SDK.