Context

The TypeSpec team has a plan for converting existing Azure services to TypeSpec. The process involves manual refinement of TypeSpec files (TSPs), validation through human reviews, and various work items assigned to different teams for approval and automation. The primary goal is to ensure that the converted TypeSpec generates an OpenAPI specification functionally equivalent to the original, maintaining round-trip correctness.

Description

ARM, the API Stewardship Committee, and the TypeSpec team need to collaborate to design linters that prevent teams from copying and modifying common TypeSpec libraries, which can lead to code divergence. These linters will help maintain consistency and reduce the risk of errors introduced by unnecessary code cloning. The goal is to ensure that teams use shared TypeSpec libraries correctly and avoid creating divergent versions.