docs: standardize TCGC operation naming rule promotions

[Yuchao Yan (msyyc)]

Purpose

Make the TCGC operation-naming promotion pattern explicit for similar rules such as DeleteInOperationName, ListInOperationName, and PatchInOperationName, as requested. This independent, skill-only PR targets the current branch, feature/lintdiff-migration-new; it does not modify the rule promotion PRs or package code.

Evidence and change

PUT promotion #5457 established common SDK naming in TCGC. PATCH promotion #5665 initially used authored operation names in ARM and was corrected to the same TCGC pattern at the user's request. Its independently verified Balanced review reported zero findings on commit 5d131d487ec0e1dd8f1bd0b6ff1050fe4df2f747.

The promotion skill now gives this naming family an explicit, bounded adaptation contract: prefer TCGC, use non-mutating context creation and getLibraryName(..., AllScopes), honor common client/exact/friendly names, and ignore emitter-scoped names and OpenAPI operation IDs. Preserve rule-specific endpoint, verb, paging, prefix, severity, and diagnostic-target behavior; a list-only policy must not be replaced mechanically by a generic GET naming rule.

The instructions also require both-direction override regressions, appropriate opt-in audience handling, disabled client-sdk registration, native documentation and release metadata, and an explicit distinction between immutable authored-source evidence and adapted SDK-name behavior.

The review skill consumes that same authorized contract rather than incorrectly classifying the documented name-domain adaptation as an unfixed source defect. Other semantic changes retain the existing source-repair stop policy. No source changes, new diagnostics, auto-merge, or new retry permissions are authorized by this update.

Validation

Inspected the complete two-file skill diff, checked the new cross-skill anchor and existing references, and ran scoped Prettier write/check and git diff --check.

The initial formatter invocation attempted to load a plugin from the uninitialized skill-only worktree. It failed before formatting; using the existing coordinator's identical formatter configuration and installed plugins passed without installing dependencies or initializing/building core.

No package tests, builds, documentation regeneration, corpus runs, or release entries are needed for this Markdown-only change.