[Yuchao Yan (msyyc)]

Summary

Consolidate DescriptionMustNotBeNodeName and DescriptiveDescriptionRequired into the existing @azure-tools/typespec-azure-core/documentation-required rule. This absorbs #5674 without introducing separate public rule IDs.

The October 22 review fixes simplify the implementation, tests, and published guidance:

• Keep rule-only types, messages, normalization, and name selection in require-docs.ts; remove the two helper modules.
• Use the pinned compiler's native enumMember callback, preserving existing missing-doc exemptions and explicit-documentation checks on exempt members.
• Compare ordinary properties with their authored TypeSpec names, not JSON serialization names. HTTP parameters and multipart parts retain their distinct HTTP naming policy.
• Reduce the canonical suite from 79 to 32 tests, retaining distinct semantic branches, exact authored targets, missing/blank/name/verb deduplication, and meaningful compliant controls. Reuse one file-level tester and hook.
• Use standard rule documentation with description, Impact, examples, and Suppression; keep migration history here rather than in the public rule guide.
• Classify the existing Azure Core changeset as a feature, with a short warning example. Separate sample-package release coverage is retained.

Behavior and legacy mapping

Legacy Swagger linter	Native coverage
SummaryOrDescription	Existing missing-documentation requirements, scopes, and exemptions remain unchanged.
DescriptionMustNotBeNodeName	Reject repeated names and placeholder description, ignoring surrounding whitespace, periods, and case. Operations compare both authored names and effective HTTP verbs.
DescriptiveDescriptionRequired	Reject explicitly empty/whitespace-only documentation, including compiler-exposed docs on exempt declarations.

HTTP path/query/header properties use wire names; multipart properties use authored part names with source-name fallback, including repeated parts. Enum members and named union variants use names; unnamed string variants use values. Status-code properties are exempt from name comparisons, not blank checks. Namespaces, interfaces, scalars, inline properties, and otherwise exempt declarations receive explicit-documentation checks without newly requiring absent documentation. Uninstantiated template docs unavailable from the compiler remain outside coverage.

Native-policy adaptation: ordinary properties deliberately use authored names even when @encodedName("application/json", ...) differs. This replaces the previous JSON-name comparison following review; it is not exact Swagger emitted-name parity. One renamed-property regression proves the new source-name behavior; the prior JSON-precedence matrix is removed. The immutable lintdiff sources below are unchanged.

The already-enabled data-plane and resource-manager rulesets intentionally acquire stronger documentation-quality checks. This is not a disabled-by-default opt-in migration. Compiler metadata and emitted Swagger occurrences differ; exact diagnostic population parity and the legacy truthy selector's empty-string discrepancy are not reproduced.

Consolidation and provenance

Check	Immutable reviewed lintdiff source	Incorporated promotion
DescriptionMustNotBeNodeName	#5662 at 3753a319	#5663, including 105eb1be8's sample CI fix.
DescriptiveDescriptionRequired	#5672 at 72ab2239	#5674 at 8a3c53e2c.

Merge e4e52dac5 preserves both histories. #5674 is superseded; its branch/history and review threads are retained. The existing PR title follows the combined-migration convention used in #5294 and #5423.

Current local validation (October 22, 2026)

• mise exec -- pnpm -r --filter "@azure-tools/typespec-azure-rulesets..." build: passed, including Azure Core, ARM, and their dependency closure.
• mise exec -- pnpm test --pool=threads --maxWorkers=1 --project=@azure-tools/typespec-azure-core --project=@azure-tools/typespec-azure-rulesets: 60 files passed, 522 tests passed, 2 existing skips. The canonical documentation suite has 32 cases.
• Strict focused TypeScript check of test/rules/require-docs.test.ts using tsc --noEmit --ignoreConfig --module NodeNext --moduleResolution NodeNext --target esnext --strict --skipLibCheck --verbatimModuleSyntax true --types node: passed. The earlier undefined-location errors in this suite are eliminated. Full package test-project type-check is not clean: unchanged casing-style/type-only-import tests and Vitest project boundaries still report errors.
• Root pnpm format and pnpm lint, scoped CSpell, chronus status, and git diff --check: passed.
• One-time validation of all four actual published snippets, using compiler createTester with libraries: [], no imports/usings/wrapper, and the real linter: incorrect snippets produce 2 / 2 / 1 diagnostics; correct snippet produces zero. Document SHA-256: e6405852d08b4128d365c582840dbbd3e923b31200e25539ba91969e488534d6. This is a one-time receipt, not continuous Markdown coverage; no per-rule Markdown parser was added.
• Initial ruleset test failure came from stale ARM build output and passed after rebuilding. Missing locked JavaScript dependencies were restored; the install's unrelated Python prepare hook failed fetching PyPI metadata, but the affected dependency-closure build and tests subsequently passed. No manifests, lockfile, compiler pin, or Python files changed.

These are local results, not a claim of GitHub CI success or merge approval. Final-head CI is inspected separately without waiting for completion. Historical validation counts and behavior claims below are superseded by this section.

Historical PR description and earlier validation (superseded above)

Focused test cleanup (October 21, 2026)

b5ade3c56 removes one redundant unfiltered documentation-rule case while retaining the broader mixed missing/blank/punctuation/name/verb regression. No production behavior, public documentation, or enablement changed, and existing release-note coverage is unchanged.

The canonical suite passed 79/79 cases using the existing threads/single-worker profile with unchanged timeouts. An initial run hit a 10-second setup-hook timeout; its cause is unproven. The package/dependency-closure build and root formatting/lint passed. Focused strict TypeScript checking has the same nine pre-existing undefined-location errors as the exact-head baseline, shifted only by the deleted test; no new errors were introduced. The full test project is not claimed error-free. Earlier counts below are historical.

Summary

Consolidate DescriptionMustNotBeNodeName and DescriptiveDescriptionRequired into the existing @azure-tools/typespec-azure-core/documentation-required rule. This PR absorbs #5674, including its implementation and regression coverage, rather than adding separate no-uninformative-doc or no-empty-doc public rules.

Implemented in merge commit e4e52dac5, preserving the histories of both promotion branches.

This follows the combined-migration presentation used in #5294 and #5423. Further review of both documentation-quality checks should continue here. Closing #5674 as superseded does not imply CI or review approval; its branch and review history are retained, and existing review threads are not resolved by this consolidation.

Combined behavior and legacy-rule mapping

Legacy Swagger linter	Native coverage
SummaryOrDescription	Existing missing-documentation requirements for types, operations, and members, with their existing scopes and exemptions retained.
DescriptionMustNotBeNodeName	Reject explicit descriptions that repeat effective names or the placeholder description, ignoring surrounding whitespace, periods, and case. Operations are checked against both source names and effective HTTP verbs.
DescriptiveDescriptionRequired	Reject explicitly empty or whitespace-only documentation, including compiler-exposed documentation on declarations exempt from missing-doc requirements.

• HTTP path/query/header properties use wire names; ordinary properties use JSON encoded names; multipart properties use authored part names with source-name fallback.
• Enum members and named union variants use member names; unnamed string variants use their values. HTTP status-code properties are exempt from name comparisons, not explicit blank-documentation checks.
• Blank checks also cover namespaces, interfaces, scalars, inline properties, union variants, and explicitly documented declarations exempt from missing-doc requirements. Uninstantiated template documentation unavailable from the compiler remains outside coverage.
• Absent documentation is not newly required on exempt declarations. Required targets receive one blank diagnostic, not duplicate findings from the combined validators.
• The existing data-plane and resource-manager rulesets already enable documentation-required. This intentionally strengthens documentation quality for existing users; it is not a disabled-by-default opt-in migration.

The native contract uses compiler documentation metadata, not emitted Swagger summary/description occurrences. The legacy truthy selector's empty-string discrepancy is intentionally not reproduced, and exact emitted diagnostic parity is not claimed.

Consolidation and provenance

Check	Immutable reviewed lintdiff source	Separate promotion incorporated here
DescriptionMustNotBeNodeName	#5662 at 3753a319	#5663 at 105eb1be8, including the sample CI fix.
DescriptiveDescriptionRequired	#5672 at 72ab2239	#5674 at 8a3c53e2c.

The source lintdiff implementations are unchanged. Explicit-documentation checks run directly from the existing native semantic callbacks; one quality-check helper preserves the broader authored-documentation scope and the missing-doc exemptions without listener remapping or validator factories. The combined tests now expect name-only and placeholder descriptions to produce uninformative, not empty, findings; an unfiltered regression verifies the combined rule reports blank and uninformative documentation together.

The user-facing rule documentation has one combined legacy-coverage table, and Azure Core has one consolidated fix changelog entry. Widget Manager colors and the ARM library provisioning state have meaningful descriptions, with their OpenAPI snapshots regenerated.

Validation recorded at consolidation (historical)

• Reproduced the merged test conflict before correcting the expectations.
• Combined documentation suites: 85 passed.
• Full affected-package run: 62 files passed; 576 tests passed and 2 existing skips, covering Azure Core, Azure rulesets, sample snapshots, and playground samples.
• Full monorepo build, including the website and engineering type-check: passed.
• Full repository lint and formatting: passed.
• Chronus status and diff hygiene: passed.

These are local results, not a claim that fresh GitHub CI or review has completed. The separate REST API Specs integration check has adoption failures from strengthening an already-enabled rule; no downstream specification changes or diagnostic suppressions are included here.

Historical #5663 promotion notes before consolidation (superseded where noted above)

Current implementation after review

Uninformative-documentation checks are consolidated into existing documentation-required. Operations are compared against both their source name and HTTP verb; emitted-name, multipart and member behavior is retained. Existing missing-doc exemptions remain unchanged. The separate opt-in rule is removed: this intentionally strengthens documentation quality. Compatibility with the matching #5674 consolidation was verified.

Implemented in 5e8dc5927. Review threads are left unresolved.

Historical promotion notes and earlier validation (superseded where noted above)

Summary

Promote Swagger DescriptionMustNotBeNodeName to @azure-tools/typespec-azure-core/no-uninformative-doc.

The rule warns when explicit documentation repeats the name it describes or uses the placeholder description. It is registered in Azure Core and explicitly disabled by default in both the data-plane and resource-manager rulesets, so existing specs do not acquire new warnings automatically.

This PR includes the native rule, regression tests, documentation, generated linter references, ruleset registration, and separate Chronus entries for the Core feature and internal ruleset registration.

Original Swagger linter

• Validator implementation
• Validator documentation

The legacy rule recursively examines objects containing string descriptions. It trims whitespace, removes periods, and compares case-insensitively against an explicit name or the object's path key; it also rejects the placeholder description. Its executable registration is ARM.

Source TypeSpec lintdiff rule

Item	Value
Development PR	#5662
Local rule	description-must-not-be-node-name
Immutable reviewed source	3753a319f32f3926005536029f9ff32b94f3c905
Source implementation	description-must-not-be-node-name.ts
Migration evidence	migration.md

The promoted create(context) implementation and normalization function are identical to the reviewed source. Promotion changes the public rule/export name, documentation metadata, package registration, native testing setup, and rulesets. The source was not modified during promotion.

Destination analysis

Azure Core owns this shared documentation-quality concern: the implementation uses compiler and HTTP APIs, without ARM resource metadata or SDK-name overrides. Core's existing documentation-required rule checks missing documentation, not repetitive or placeholder text. ARM would unnecessarily restrict the native rule's audience; TCGC is not appropriate because this is not an SDK-naming policy.

How the promoted TypeSpec linter works

• Reads explicit @doc text and doc comments through compiler getDoc; normalizes surrounding whitespace, periods, and case.
• Checks named models, scalars, enums, unions, enum members, properties, union variants, and operations.
• Compares path/query/header properties against HTTP wire names. Ordinary non-part properties use JSON encoded names, falling back to source names.
• Compares multipart properties against authored HttpPart names, including repeated-part arrays. Unnamed parts use the source property name; JSON encoding does not rename multipart parts.
• Compares operations against their effective HTTP verb, including inferred GET and POST. HTTP resolution diagnostics remain owned by HTTP validation.
• Compares named union variants against their names and unnamed string variants against their literal values. Other unnamed variants are checked only for placeholder text.
• Ignores missing or normalized-empty documentation and status-code properties. Key properties are not exempt. Diagnostics target authored semantic declarations.

For example, @doc("Ready") Ready: "available" warns, while @doc("available") Ready: "available" does not.

The production rule does not emit or read Swagger, predict generated schema names, project API versions, or add emitter, OpenAPI, ARM, or TCGC dependencies.

Fixture-to-native test mapping

All 15 source fixtures are represented in the 40 native test cases. Source fixtures are pinned under DescriptionMustNotBeNodeName; native tests exercise the compiler/HTTP predicates directly rather than copying snapshots or ARM template scaffolding.

Source fixture(s)	Native coverage
description-matches-name	Property-name equality and placeholder text
descriptive-docs	Meaningful documentation
literal-description	Placeholder normalization
model-description-matches-model-name	Model-name equality; whitespace, periods, and case
operation-description-matches-http-verb	Explicit HTTP verbs
operation-description-matches-typespec-name-only	Source-operation-name compliance
parameter-description-matches-emitted-name, parameter-description-matches-source-name-only	HTTP wire names and source-name-only controls
property-description-matches-property-name	Ordinary property-name equality
member-and-key-documentation	Enum/union member names versus literal values; key properties
inferred-http-verbs	Effective inferred GET/POST and explicit-verb precedence
json-encoded-property, json-encoded-source-name-only	JSON names and source-name-only compliance
multipart-authored-names, multipart-source-name-only	Direct/custom/array/repeated parts; authored names and compliant controls

Additional native coverage includes scalar/enum/union names, doc comments, query/header metadata, unnamed variants, missing/empty docs, status-code exemption, exact diagnostic locations, multipart JSON-name isolation, and both published documentation examples.

Migration evidence

The source validation passed 47 native tests, 15 strict fixtures, and five affected fixture groups. The final full corpus run attempted 468 projects, successfully compiled 462, and retained six documented compilation exclusions. The final target-rule diagnostic multiset was unchanged at 8,499; generated corpus outputs were restored and are not included in this PR.

The pinned migration note records project overlap, selected-version attribution, one-sided findings, outliers, and limitations. Swagger counts emitted occurrences; TypeSpec diagnostics describe authored semantic declarations and instances. Repeated roots/versions, inline copies, qualified schema names, compatibility or unused types, version selection, and constant route parameters explain population differences.

The native documentation-quality contract is covered. Corpus overlap and counts are not proof of arbitrary executable Swagger parity.

Validation and review

Required promotion checks passed:

• 40 focused native tests, including incorrect/correct documentation examples.
• Full Azure Core suite: 474 passed, 2 existing skips across 58 test files.
• 6 rulesets tests, including disabled-by-default registration.
• Dependency-closure/package builds, package lint, scoped formatting, and diff hygiene.
• Documentation regeneration and formatting of authored/generated guidance.
• Chronus status for the Core feature and internal ruleset-registration entries.

The two existing skips are the unrelated @example and @useRef groups in no-openapi.test.ts. Documentation regeneration retains existing missing-diagnostic-documentation warnings outside this rule. No new tests are skipped. A website build/full-repository wrapper was not part of the targeted promotion checks.

Fresh independent local reviews were clean. The final source review completed after 2 Balanced Copilot rounds at 3753a319; the final promotion review completed after 1 Balanced round at 2c5214be. Independent refetches confirmed zero review-specific comments and zero unresolved Copilot threads on both final heads. The inferred-verb, JSON-name, and multipart findings are implemented and resolved.

Promotion sync policy

Source semantics remain immutable during promotion. Any future confirmed source-semantic defect must be repaired and reviewed in lintdiff first, then promoted from that exact reviewed commit; it must not be fixed only in the official copy.

heavy

Historical #5674 promotion notes before consolidation (superseded where noted above)

Current implementation after review

Empty/whitespace explicit documentation is checked by existing documentation-required, preserving its missing-doc exemptions. The separate no-empty-doc rule/registration is removed and semantic coverage is transferred. This intentionally strengthens documentation quality. Compatibility with the matching #5663 consolidation was verified.

Implemented in 20683492f. Review threads are left unresolved.

Historical promotion notes and earlier validation (superseded where noted above)

Original Swagger linter

• linter code: DescriptiveDescriptionRequired
• linter doc: descriptive-description-required.md

The original rule:

• Selects description fields in unresolved OpenAPI 2 documents.
• Ignores null and non-string inputs in its function.
• Reports selected strings whose trim() result is empty, at their selected JSON paths.
• Accepts nonblank text without judging prose quality.

How the Swagger linter works

Spectral recursively selects objects using $..[?(@object() && @.description)].description, then applies the blank-string check. This truthy selector skips missing, empty-string, null, and numeric descriptions before the function runs; whitespace strings are selected and rejected. That executable discrepancy is not copied into the native rule. Emitted occurrences and semantic TypeSpec declarations are different diagnostic populations, so exact Swagger diagnostic parity is intentionally partial.

Source TypeSpec lintdiff rule

• Validator ID: DescriptiveDescriptionRequired.
• Local rule: descriptive-description-required.
• Canonical validator slug: descriptive-description-required.
• Source repository: Azure/typespec-azure; source draft #5672.
• Source branch: lintdiff-descriptive-description-required.
• Immutable, cleanly reviewed and pushed source commit: 72ab22394704fce1a1555c879ff7335da8debf42.
• Source worktree: C:\dev\worktrees\lintdiff-descriptive-description-required, clean at the pinned source head.
• Original lintdiff source rule.

The source rule was assumed done for this promotion invocation. It was not modified during promotion. The development review completed two rounds with no new comments at the pinned head. The earlier development publication commit was 2423e379680a19091a1b86ffd5c240daa3d4089e; the reviewed source includes subsequent test/evidence fixes without changing production rule behavior.

Destination analysis

The agent selected @azure-tools/typespec-azure-core: the rule uses compiler documentation metadata only, applies to both ARM and data-plane authoring, and needs neither ARM resource semantics nor SDK-name resolution. ARM would unnecessarily narrow a shared authoring requirement; TCGC is not appropriate because this is not a generated SDK API policy. No ARM or TCGC dependency is introduced.

Core's existing documentation-required addresses missing documentation and tests documentation truthiness. It does not reject nonempty whitespace strings and has a different declaration scope. This rule complements that policy rather than duplicating it.

How the promoted TypeSpec linter works

The official rule is @azure-tools/typespec-azure-core/no-empty-doc.

It reads getDoc(program, target) on namespaces, interfaces, operations, models, model properties, scalars, enums, enum members, unions, and union variants. Undefined documentation is compliant; defined documentation with an empty trimmed value produces a warning targeted at the offending declaration. Any non-whitespace character is sufficient.

The enum callback explicitly iterates enum.members because the compiler does not dispatch enum-member listener callbacks. Tests preserve exact property and enum-member diagnostic locations. Standard linter traversal owns library filtering; there is no custom HTTP reachability, provider, version/projection, emitted-reference, or OpenAPI-extension filter.

The native rule's create(context) implementation matches the immutable source after line-ending normalization. Promotion adapts only the official name/export, native documentation metadata, and documentation URL. The source's unprojected native authoring population remains unchanged.

The rule is explicitly disabled (false) in both data-plane and resource-manager rulesets. The Core feature change and disabled-only rulesets internal change have separate Chronus entries.

Fixture-to-native test mapping

Snapshots and validator output are evidence only; they were not copied into the official package. Reduced compiler-native snippets exercise the same rule-owned branches.

Original lintdiff fixture	Native vitest case	Coverage note
empty-description	it("rejects a whitespace-only property description")	Reduced property snippet; one blank-description diagnostic.
whitespace-param-description	it("rejects a whitespace-only parameter description")	Direct operation parameter; one diagnostic.
non-empty-description	it("accepts nonblank descriptions on models, properties, and operations")	Compliant supplied documentation, without emitted snapshots or ambient suppressions.
enum-member-description	it("targets offending enum members rather than their containing enum")	Whitespace-member branch and precise member targeting.
N/A (review regression)	it("targets offending properties rather than their containing model")	Two diagnostics with exact property file/position/end.
N/A (review regression)	it("targets offending enum members rather than their containing enum")	Source-review member-location regression retained.
N/A (native documentation examples)	it("validates the documented incorrect and correct examples")	Reads the actual authored Markdown examples; incorrect warns and correct is valid with this rule enabled.

The 24 native cases also cover registered declaration kinds, absent and nonblank documentation, empty and Unicode-whitespace content, documentation comments, and diagnostic targeting. Fresh asynchronous tester initialization follows the Core test lifecycle.

Migration evidence

See the checked-in migration.md for focused comparisons, representative and full real-service corpus evidence, one-sided project explanations, compile exclusions, and remaining uncertainty. Those counts describe the immutable source's comparison population, not a fresh official-library corpus run or universal executable equivalence.

Validation recorded at consolidation (historical)

All required targeted checks are complete:

• Core prerequisite closure and affected package builds.

• Focused native rule tests: 24 passed, including the actual authored documentation examples.

• Core package lint.

• Core documentation regeneration, inspection, and explicit formatting/checking of the README, authored rule, generated linter reference, and ignored generated rule page.

• Maintained-file formatting check and git diff --check.

• LF Chronus entries and pnpm chronus status.

• Rulesets dependency closure/build, package lint, and five tests passed.

• Full Core native suite: 58 files passed, 458 tests passed, two original skips, 460 total, using the approved package-scoped profile:

  mise exec -- pnpm --filter @azure-tools/typespec-azure-core exec vitest run --pool=threads --maxWorkers=1
  

• Independent persistent local precommit review of the exact ten-file scope: no significant issues.

Validation limitations

The original full Core run had two per-test 5,000ms timeouts (override-api-version and casing-style); the authorized single-worker diagnostic retained one casing-style timeout. Both failed receipts remain preserved. A coordinator-authorized bounded comparison ran the exact remaining casing test once against the baseline registration and once against the restored draft using threads/single-worker; both passed. The subsequent single authorized full suite passed with the identical 460-test population and the same two original skips.

The original timeout cause is unproven. This is not a claimed environmental diagnosis. Vitest 5, isolate: false, the configured 5,000ms test and 10,000ms hook limits, assertions, dependencies, and skips were unchanged. The passing profile does not grant further retries. Baseline isolation restored the exact draft registration and all 404 archived compiled outputs.

Repository-wide validate:pr and the website build were not run; the required targeted plan above is complete, and CI's dedicated Website job remains authoritative for the Astro build. The generated rule page was inspected/formatted but remains ignored and is not force-added.

Promotion sync policy

The lintdiff source remains immutable during promotion. A confirmed source-semantic defect discovered in promotion review blocks this PR and returns evidence to the owning queue; only that coordinator may authorize a bounded return-to-development repair cycle. This PR would then be refreshed incrementally only after clean source review at a new exact pinned commit, with native regressions and provenance updated. Promotion itself never edits the source rule or silently changes its semantics.

Historical review cleanup (October 19, 2026; superseded below)

Consolidated empty/effective-name behavior into require-docs.test.ts and deleted the two additional behavior files. Authored-documentation filtering stays local; combined/missing-documentation checks remain unfiltered. HTTP metadata spies are scoped to the naming-quality subgroup and restored after each case; diagnostic targets and call-count checks remain. Removed the redundant Core internal entry, retaining the fix and separate samples-package entries.

Published in 57eb47e. Fresh focused validation: 86 tests passed, package production typecheck, root pnpm format, root pnpm lint, and diff hygiene passed. The full test TypeScript project retains pre-existing diagnostics (19 before, 19 after); the exact-head baseline comparison found no new diagnostics, accounting explicitly for moved tests and any removed duplicate fixture. This is not a claim that the full test TypeScript project is error-free or that pending CI has passed. These current file-layout/coverage statements supersede earlier descriptions of the removed test files; historical validation remains historical.

Review cleanup (October 21, 2026)

Implemented selected review IDs 32–36 in 85ac77b. Removed the unreachable uninstantiated-template success case, HTTP resolver spy/call-list oracle, and test-only missing-diagnostic filters. All canonical fixtures now instantiate the shipped public rule with minimally documented scaffolding or assert the real missing-doc warning. Mixed missing/blank/name controls and exact authored targets remain.

Documentation-quality checks now run directly in native callbacks, with explicit enum-member iteration and a small effective-name resolver. Missing-doc exemptions, broader explicit-doc coverage, blank-diagnostic deduplication, public rule ID and existing enablement are unchanged. Added instantiated-model and explicit discriminator regressions. Reduced multipart checks to a normal named part and a focused repeated outer-array part; retained authored/source/JSON precedence, fallback and placeholder controls, and combined path/query/header source-name compliance with JSON-precedence cases.

Fresh local validation: 80 canonical rule tests passed; the complete Azure Core and Azure rulesets run passed 60 files, 568 tests, with 2 existing skips. Azure Core package build (including production TypeScript compilation and TypeSpec library lint), root pnpm format, root pnpm lint, Chronus status and diff hygiene passed. Reused existing production release coverage without adding internal test-history notes. An initial diagnostic-order expectation and an intermediate TypeScript narrowing error were corrected before the passing validation. No compiler timeout settings were changed.

Available final-head CI was inspected once after publication: only license/cla had reported (success); build/test CI was not yet reported. CI pending - not awaited. These local results do not claim fresh CI passed or whole-PR review/merge readiness. The earlier consolidation and promotion validation above remains historical. Existing review threads are untouched.

[github-actions]

All changed packages have been documented.

• ✅ @azure-tools/typespec-azure-core

Show changes

@azure-tools/typespec-azure-core - feature ✏️

Strengthen documentation-required to reject explicitly empty or whitespace-only documentation and descriptions that repeat a declaration's name or the placeholder description. Ordinary properties use their authored names, regardless of JSON serialization names; HTTP parameters and multipart parts retain their HTTP names. Explicit-documentation checks also cover namespaces, interfaces, scalars, inline properties, union variants, and declarations exempt from missing-doc requirements when their documentation is exposed by the compiler. Operation descriptions are compared with both the source operation name and effective HTTP verb. Missing-documentation requirements and exemptions are unchanged. The existing data-plane and resource-manager rulesets already enable this rule.,> ,> tsp,> // Warns: the description only repeats the authored name.,> /** Widget */,> model Widget {},>

@azure-tools/typespec-samples - internal ✏️

Update Widget Manager color and ARM library provisioning-state descriptions to satisfy documentation-required, and regenerate sample snapshots.

[github-actions]

📦 Package size report

2 packages changed size, +8.05 KB (+0.0%) packed overall.

Package	Packed (base → head)	Δ Packed	Unpacked (base → head)	Δ Unpacked
@azure-tools/typespec-azure-resource-manager	194.63 KB → 201.90 KB	+7.27 KB (+3.7%) 🔴	1.16 MB → 1.21 MB	+48.33 KB (+4.1%) 🔴
@azure-tools/typespec-azure-core	136.55 KB → 137.93 KB	+1.39 KB (+1.0%) 🔴	733.30 KB → 739.94 KB	+6.64 KB (+0.9%) 🔴

12 package(s) with no notable change

Package	Packed (base → head)	Δ Packed	Unpacked (base → head)	Δ Unpacked
@azure-tools/typespec-client-generator-core	250.01 KB → 249.45 KB	-577 B (-0.2%)	1.33 MB → 1.32 MB	-3.79 KB (-0.3%)
@azure-tools/typespec-azure-rulesets	6.00 KB → 5.94 KB	-64 B (-1.0%)	35.20 KB → 35.11 KB	-88 B (-0.2%)
@azure-tools/typespec-azure-portal-core	36.26 KB → 36.28 KB	+17 B (+0.0%)	242.62 KB → 242.88 KB	+260 B (+0.1%)
@azure-tools/azure-http-specs	143.53 KB → 143.53 KB	—	1.20 MB → 1.20 MB	—
@azure-tools/typespec-autorest	87.87 KB → 87.87 KB	—	424.17 KB → 424.17 KB	—
@azure-tools/typespec-autorest-canonical	7.42 KB → 7.42 KB	—	26.00 KB → 26.00 KB	—
@azure-tools/typespec-azure-examples	80.15 KB → 80.15 KB	—	383.36 KB → 383.36 KB	—
@azure-tools/typespec-go	264.28 KB → 264.28 KB	—	1.35 MB → 1.35 MB	—
@azure-tools/typespec-java	20.22 MB → 20.22 MB	—	22.52 MB → 22.52 MB	—
@azure-tools/typespec-metadata	15.88 KB → 15.88 KB	—	62.08 KB → 62.08 KB	—
@azure-tools/typespec-python	42.58 KB → 42.58 KB	—	166.02 KB → 166.02 KB	—
@azure-tools/typespec-ts	550.66 KB → 550.66 KB	—	2.75 MB → 2.75 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.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@azure-tools/typespec-azure-core@5663

npm i https://pkg.pr.new/@azure-tools/typespec-azure-rulesets@5663

commit: e00571b

[Copilot]

🟡 Changes recommended

Inferred HTTP verbs and encoded property names currently escape checks performed by the legacy validator.

2 open findings

• Validate descriptions against inferred HTTP verbs · New
• Compare the effective JSON encoded property name · New

What changed in this PR

Adds an opt-in Azure Core lint rule migrating DescriptionMustNotBeNodeName.

Changes:

• Implements and tests uninformative-documentation detection.
• Registers the rule disabled by default in both Azure rulesets.
• Adds documentation and Chronus entries.

File	Description
website/​.../​reference/​linter.md	Lists the rule.
packages/​typespec-azure-rulesets/​test/​validate-rules-defined.test.ts	Verifies opt-in status.
packages/​typespec-azure-rulesets/​src/​rulesets/​resource-manager.ts	Registers disabled rule.
packages/​typespec-azure-rulesets/​src/​rulesets/​data-plane.ts	Registers disabled rule.
packages/​typespec-azure-core/​test/​rules/​no-uninformative-doc.test.ts	Adds rule tests.
packages/​typespec-azure-core/​src/​rules/​no-uninformative-doc.ts	Implements the rule.
packages/​typespec-azure-core/​src/​rules/​no-uninformative-doc.md	Documents behavior.
packages/​typespec-azure-core/​src/​linter.ts	Exports the rule.
packages/​typespec-azure-core/​README.md	Lists the rule.
.chronus/​changes/​register-no-uninformative-doc-2026-10-10.md	Describes ruleset registration.
.chronus/​changes/​no-uninformative-doc-2026-10-10.md	Describes the Core feature.

🧠 Review effort: Balanced

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[azure-sdk-automation]

You can try these changes here

🛝 Playground	🌐 Website

[Copilot]

🟡 Changes recommended

Renamed multipart parameters bypass the intended uninformative-documentation check.

1 open finding

• Fallback misses renamed multipart part names · New

2 resolved since last review

• Compare the effective JSON encoded property name
• Validate descriptions against inferred HTTP verbs

🧠 Review effort: Balanced

[Copilot]

🟢 Approval recommended

The implementation, registration, documentation, release metadata, and regression coverage are complete and consistent.

0 open findings

1 resolved since last review

• Fallback misses renamed multipart part names

🧠 Review effort: Balanced

[Yuchao Yan (msyyc)]

Copilot resolve the merge conflicts in this pull request

[Copilot]

Copilot resolve the merge conflicts in this pull request

Resolved in 3612bc1 by merging the latest main, preserving both the documentation-rule tests and main’s ARM opt-in tests. Build, formatting, lint, and all 89 focused tests passed; read-only review found no issues. CodeQL timed out after Actions/Go completed with no alerts, so security analysis is incomplete.