Add linter rule arm-post-lro-response-mismatch for ARM POST LRO operations

[Copilot]

• New rule arm-post-lro-response-mismatch for ARM POST LRO operations
• Response-based checking logic driven by HTTP status codes:
  • If 200 response exists: non-void body must match finalResult; void/empty body means finalResult should be "void"
  • If 204 without 200: finalResult should be "void"
  • If both 200 (void body) and 204: finalResult should be "void"
  • If both 200 (non-void body) and 204: emit new conflictingResponses diagnostic (POST should not have both 204 NoContent and 200 OK with a non-empty body)
  • If only 202: check template instantiation of Azure.ResourceManager.ActionAsync (fully-qualified name) for Response param match with finalResult
• doesFinalResultMatch checks both namespace-qualified name equality (for named types) and isAssignableTo from typekit for type compatibility
• Void matching: "void" finalResult is compared against TypeSpec builtin void type via isVoidType
• Uses resolveArmResources for both resource-level and provider-level actions
• Codefix arm-post-lro-set-final-result using ArmLroLocationHeader<FinalResult = ResponseType> — handles:
  • Existing ArmLroLocationHeader alone → replace with FinalResult version
  • ArmLroLocationHeader in intersection → replace just that part
  • No LroHeaders parameter → append it after last template arg
• Fix in resolveArmResourceOperations: raw @armResourceAction operations (with simple HTTP paths like /generate) are now properly discovered by matching against already-resolved resources when path-based resolution fails. Previously these operations were silently dropped because getResourceInfo couldn't derive ARM resource type info from relative paths.
• Tests use ...ResourceNameParameter<Employee> throughout
• Tests refactored to use it.each for parameterized type matching/non-matching scenarios
• Low-level (non-template) tests use ArmAcceptedLroResponse for proper LRO constructs: invalid case (200 with Model body + ArmAcceptedLroResponse) and valid case (204 + ArmAcceptedLroResponse)
• Tests cover: 200 body mismatch, 204 void check, ArmResourceActionAsyncBase with 200 body check, ActionAsync 202-only template check, low-level non-template LRO operations with ArmAcceptedLroResponse, conflicting 200+204 responses, and codefix
• All tests pass, files formatted correctly
• Documentation page added for the rule
• Merged latest from main, regenerated docs — only PR-related files differ

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Mark Cowlishaw (markcowl)]

Copilot Pull the latest from main and then apply the fixes in the comments. Ensure that all tests pass and all files are correctly formatted.

[Copilot]

Copilot Pull the latest from main and then apply the fixes in the comments. Ensure that all tests pass and all files are correctly formatted.

Pulled latest from main, applied all review fixes, and verified all 286 tests pass with correct formatting. Changes in a9c28e6.

[Mark Cowlishaw (markcowl)]

Copilot Please pull the latest from main, regenrate docs for tyepspec-azure-resource-manager, validate that all files are correctly formatted.

[Copilot]

Copilot Please pull the latest from main, regenrate docs for tyepspec-azure-resource-manager, validate that all files are correctly formatted.

Pulled latest from main (already up to date at a228fc5), regenerated docs for typespec-azure-resource-manager (added the new rule to README.md and linter.md), validated formatting, and confirmed all 286 tests pass. Done in 7e87831.

[Mark Cowlishaw (markcowl)]

Please pull the latest from main, make the changes suggested, ensure all tests are passing and all files are correctly formatted.

[Copilot]

Please pull the latest from main, make the changes suggested, ensure all tests are passing and all files are correctly formatted.

Pulled latest from main (already up to date), added the fallback for non-template operations that checks the 200 response body vs final-result-schema, and verified all 288 tests pass with correct formatting. Done in fcb4809.

[Copilot]

Copilot Found some instances of what looks like a bad merge. If you think these belong in this pr, please explain why.

Otherwise, pull the latest, fix this bad merge, really look to make sure the...

Reverted resource.ts entirely — those changes (raw @armResourceAction operation discovery fallback) were out of scope. Updated the two low-level tests that depended on that code to expect .toBeValid() since those operations aren't discovered by resolveArmResources. All 377 tests pass, files formatted, only PR-related files in the diff.

[Mark Cowlishaw (markcowl)]

Copilot there is a merge issue with readme.md (generated by rebuilding docs for typespec-azure-resource-manager). Please pull the latest, rebuild and regen docs, ensure that all files are correctly formatted, any merge conflicts are fixed and only the changes associated with this pr are in the pr diff.

[Copilot]

Copilot there is a merge issue with readme.md (generated by rebuilding docs for typespec-azure-resource-manager). Please pull the latest, rebuild and regen docs, ensure that all files are correctly ...

Pulled latest from main, resolved the README.md merge conflict (took main's version then regenerated docs), all 377 tests pass, files formatted, only PR-related files in the diff.

[Mark Cowlishaw (markcowl)]

Copilot it looks like you missed change the rule source file name and the function name for the rule to match the new rule name (no-lro-response-mismatch). Please pull the latest from main, make these changes, rebuild and regenerate docs, ensure all tests pass and all changed files are properly formatted, then ensure that only the changes associated with this pr are in the pr diff.

[Copilot]

Copilot it looks like you missed change the rule source file name and the function name for the rule to match the new rule name (no-lro-response-mismatch). Please pull the latest from main, make the...

Renamed source file to lro-response-mismatch.ts, export to lroResponseMismatchRule, and test file to lro-response-mismatch.test.ts. Pulled latest from main, rebuilt, regenerated docs. All 377 tests pass, files formatted, only PR-related files in diff.

[Mark Cowlishaw (markcowl)]

suppression pr: Azure/azure-rest-api-specs#45314

Private suppression pr: https://github.com/Azure/azure-rest-api-specs-pr/pull/29906

[github-actions]

📦 Package size report

✅ No notable package size changes compared to the base branch.

13 package(s) with no notable change

Package	Packed (base → head)	Δ Packed	Unpacked (base → head)	Δ Unpacked
@azure-tools/typespec-azure-resource-manager	175.40 KB → 175.48 KB	+74 B (+0.0%)	1.06 MB → 1.06 MB	+632 B (+0.1%)
@azure-tools/typespec-java	13.51 MB → 13.51 MB	-20 B (-0.0%)	15.03 MB → 15.03 MB	—
@azure-tools/typespec-azure-rulesets	5.15 KB → 5.16 KB	+5 B (+0.1%)	31.73 KB → 31.92 KB	+192 B (+0.6%)
@azure-tools/azure-http-specs	146.21 KB → 146.21 KB	—	1.16 MB → 1.16 MB	—
@azure-tools/typespec-autorest	80.93 KB → 80.93 KB	—	395.06 KB → 395.06 KB	—
@azure-tools/typespec-autorest-canonical	7.42 KB → 7.42 KB	—	26.00 KB → 26.00 KB	—
@azure-tools/typespec-azure-core	128.11 KB → 128.11 KB	—	696.78 KB → 696.78 KB	—
@azure-tools/typespec-azure-portal-core	42.40 KB → 42.40 KB	—	192.87 KB → 192.87 KB	—
@azure-tools/typespec-client-generator-core	226.23 KB → 226.23 KB	—	1.22 MB → 1.22 MB	—
@azure-tools/typespec-go	244.79 KB → 244.79 KB	—	1.25 MB → 1.25 MB	—
@azure-tools/typespec-metadata	15.91 KB → 15.91 KB	—	62.26 KB → 62.26 KB	—
@azure-tools/typespec-python	46.21 KB → 46.21 KB	—	180.83 KB → 180.83 KB	—
@azure-tools/typespec-ts	524.66 KB → 524.66 KB	—	2.53 MB → 2.53 MB	—

_{Packed = gzipped .tgz published to npm. Unpacked = total extracted size. 🆕 added, 🗑️ removed. Packages from the core/ submodule are not included.
🔴 grew · 🟢 shrank — only changes of at least 512 B and 0.5% are marked.}

[Mark Cowlishaw (markcowl)]

Please fix these two issues