docs: Add parameter renaming guide using client.tsp approach

[Copilot]

Documentation Update: Parameter Renaming Guide

• Review current documentation and understand the issue
• Add complete section for "Renaming operation parameters" with clear examples
• Include explanation about wire names vs. client names
• Address review feedback: Remove Option 1 (direct decorator in main.tsp)
• Address review feedback: Remove version-scoped parameter renaming section
• Update documentation to only recommend client.tsp approach with @@clientName
• Address review feedback: Add both generated API code and usage examples for all languages
• Address review feedback: Make example self-contained with complete TypeSpec definition
• Address review feedback: Separate main.tsp and client.tsp examples
• Address review feedback: Add using statement for PetStoreNamespace in client.tsp
• Ensure examples follow the same pattern as model/operation renaming
• Add consistent subheadings for both operations and parameters
• Final validation complete

Summary of Changes

Updated parameter renaming documentation with properly structured and complete examples:

Latest changes:

• Added using PetStoreNamespace; statement: The client.tsp example now properly includes the using statement to reference entities from the main.tsp namespace
• This makes the TypeSpec code syntactically correct and complete

The client.tsp example now includes:

1. Import statements for main.tsp and the client generator core library
2. Using statements for both Azure.ClientGenerator.Core and PetStoreNamespace
3. The @@clientName decorators for parameter renaming

This ensures the example is a complete, working TypeSpec specification.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[DOC]: Describe how to rename a parameter of an operation in the client</issue_title>
<issue_description>There is a lack of document on how to rename a parameter in https://azure.github.io/typespec-azure/docs/howtos/generate-client-libraries/09renaming/

The document mentioned sample but I didn't find a real case:

There is also the suggestion mentioned in the teams channel, so we need the document to clarify the right behaviour.

• the name of an operation parameter is not part of the api-definition. In the case of query parameters like this, you can name the parameter on the wire using the @query decorator, and this is the value that shows up in the uri. So the recommended way to change the parameter name is just to change the name
• Changing a parameter name is not an API breaking change, but it is an SDK breaking change. You can use the @renamedFrom() decorator to scope the change to the new api-version you are hopefully doi9ong this in (unless you want the change across all API versions.</issue_description>

<agent_instructions>Refine the doc: website\src\content\docs\docs\howtos\Generate client libraries\09renaming.mdx. Make the doc correct and clear and example for renaming parameter according to other examples</agent_instructions>

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

@lirenhe @tadelesh, could you start with adding the TCGC part for this? thanks

• Fixes [DOC]: Describe how to rename a parameter of an operation in the client #3785

---

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

[tadelesh]

@copilot Resolve the comments.

[Copilot]

@copilot Resolve the comments.

All comments resolved in commit ccf1d8f:

• Updated to only recommend client.tsp approach with @@clientName
• Removed direct decorator approach (Option 1)
• Removed version-scoped parameter renaming section

[azure-sdk]

No changes needing a change description found.

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website

[tadelesh]

@copilot For each part of the example, instead of import "main.tsp";, please compose a complete example, adding:

namespace PetStoreNamespace;

/** This is the input I need */
@resource("input")
model InputModel {
  /** Id of this object */
  @key
  @visibility(Lifecycle.Read)
  name: string;
}

/** Read my resource */
op get is ResourceRead<InputModel>;

[Copilot]

@copilot For each part of the example, instead of import "main.tsp";, please compose a complete example, adding:

namespace PetStoreNamespace;...

Updated the example to be self-contained. Replaced import "./main.tsp" with the complete TypeSpec definition including namespace, model, and operation declarations. (be6dcb6)