feat: implement Spector integration tests for 22 scenario groups

[Copilot]

Adds Azure Modular integration test coverage for 22 previously untested Spector scenario groups across new and existing spec files.

Updated existing spec files

• encodeDuration.spec.ts — un-skip floatSecondsLargerUnit / floatMillisecondsLargerUnit for both header and query groups
• payloadXml.spec.ts — add ModelWithEnum, ModelWithDatetime, and XmlErrorValue scenarios
• azureCorePage.spec.ts — add withRelativeNextLink (full 2-page iteration)
• azureArmResources.spec.ts — un-skip topLevel.update (PATCH + LRO poller)
• azureArmOperationTemplates.spec.ts — add exportArray LRO scenario (returns ExportResult[])
• resiliencySrvDrivenOld.spec.ts — add breakTheGlass via raw fetch (v1 client calling v2-only endpoint)

New spec files + generated clients

Spec file	Scenarios
azureClientGeneratorCoreClientDefaultValue.spec.ts	getOperationParameter, getPathParameter, putModelProperty ✅; getHeaderParameter ❌ (see below)
azureArmMultiService.spec.ts	Compute_VirtualMachines + ComputeDisk_Disks createOrUpdate/get
azureArmMultiServiceOlderVersions.spec.ts	same structure, older-version resource types with size/diskSizeGB props
azureArmMultiServiceSharedModels.spec.ts	Compute_VirtualMachines + Storage_StorageAccounts sharing SharedMetadata
serviceMultiService.spec.ts	ServiceA_Foo.test + ServiceB_Bar.test via combined client
authNoauthUnion.spec.ts	validNoAuth + validToken
parametersQuery.spec.ts	Parameters_Query_Constant_post
responseStatusCodeRange.spec.ts	errorResponseStatusCode404 + errorResponseStatusCodeInRange

New entries added to azureModularTsps in cadl-ranch-list.js; tspconfig.yaml + .gitignore + src/index.d.ts committed for each.

Known skips / emitter limitations

• Azure_ClientGenerator_Core_Override_GroupParameters_group — remains it.skip per open issue #3540
• Azure_ClientGenerator_Core_ClientDefaultValue_getHeaderParameter — emitter serializes Accept: application/json instead of application/json;odata.metadata=none; test skipped with comment

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Copilot] Implement spector tests for 22 scenario groups</issue_title>
<issue_description>## Task: Implement Spector Integration Tests
Use the spector-test-implementer skill to implement test files for the following not-implemented scenario groups.
Not-implemented scenario groups:

• Azure_ClientGenerator_Core_ClientDefaultValue (4 scenarios: getHeaderParameter, getOperationParameter, getPathParameter, putModelProperty)
• Azure_ClientGenerator_Core_Override_GroupParameters (1 scenarios: group)
• Azure_Core_Page (2 scenarios: withParameterizedNextLink, withRelativeNextLink)
• Azure_ResourceManager_MultiServiceOlderVersions_ComputeDisk_Disks (2 scenarios: createOrUpdate, get)
• Azure_ResourceManager_MultiServiceOlderVersions_Compute_VirtualMachines (2 scenarios: createOrUpdate, get)
• Azure_ResourceManager_MultiServiceSharedModels_Compute_VirtualMachines (2 scenarios: createOrUpdate, get)
• Azure_ResourceManager_MultiServiceSharedModels_Storage_StorageAccounts (2 scenarios: createOrUpdate, get)
• Azure_ResourceManager_MultiService_ComputeDisk_Disks (2 scenarios: createOrUpdate, get)
• Azure_ResourceManager_MultiService_Compute_VirtualMachines (2 scenarios: createOrUpdate, get)
• Azure_ResourceManager_OperationTemplates_Lro (1 scenarios: exportArray)
• Azure_ResourceManager_Resources_TopLevel (1 scenarios: update)
• Resiliency_ServiceDriven (1 scenarios: breakTheGlass)
• Service_MultiService_ServiceA_Foo (1 scenarios: test)
• Service_MultiService_ServiceB_Bar (1 scenarios: test)
• Authentication_Noauth_Union (2 scenarios: validNoAuth, validToken)
• Encode_Duration_Header (2 scenarios: floatMillisecondsLargerUnit, floatSecondsLargerUnit)
• Encode_Duration_Query (2 scenarios: floatMillisecondsLargerUnit, floatSecondsLargerUnit)
• Parameters_Query_Constant (1 scenarios: post)
• Payload_Xml_ModelWithDatetimeValue (2 scenarios: get, put)
• Payload_Xml_ModelWithEnumValue (2 scenarios: get, put)
• Payload_Xml_XmlErrorValue (1 scenarios: get)
• Response_StatusCodeRange (2 scenarios: errorResponseStatusCode404, errorResponseStatusCodeInRange)
  Instructions:

1. For each scenario group above, check if a .spec.ts file already exists in packages/typespec-ts/test/azureModularIntegration/ — skip if it does
2. For remaining groups, follow the spector-test-implementer workflow to implement the tests
3. Report which tests passed and which failed
   PR description format:
   The PR description must use this format for each section:

New spec files

For each newly created .spec.ts file, use this structure:

• Scenario_Group_Name — scenarioGroupName.spec.ts
  • ✅ scenarioName1
  • ✅ scenarioName2
  • ❌ scenarioName3 (reason for failure)

Updated existing spec files

Same structure as above, but for spec files that already existed and were updated with new scenarios.

Known skips / emitter limitations

List any scenarios that were skipped due to emitter bugs or limitations, with the reason.

Results should be commented on issue #17.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Copilot] Implement spector tests for 22 scenario groups #32

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.