SDK Generation pipeline shall handle the basic generation problem.

Today, we use devops pipeline to generate the SDKs.
Based on our experience, the SDK after generation usually contains some problems including:

1. Linter failure especially for SDK sample code.
2. Record test failure because of API breaking change/ api version change

As a result, service teams need to contact us to understand the root cause and how to fix the problem which takes a lot of additional effort.

Proposal:
Consider moving SDK generation pipeline into Github action and integrate with agentic workflow so SDK owner could write some guide on how to solve common SDK generation problem. Then the SDK code created by pipeline could be in a ready to release stage directly.

Start by reviewing the current devops pipeline used for SDK generation and the existing linter and record-test failures described in the issue. Compare the proposed GitHub Actions and agentic workflow approach with the current process. Done means the generated SDK code reaches a ready-to-release stage while common generation problems have documented guidance.

Written by the indexing model from the issue text.