Reclassify ms.topic values batch 1 (entries 1 to 40).

[Copilot]

Changes

Reclassified 40 files from legacy/generic ms.topic values to specific topic types based on content analysis. Each file maintains exactly one ms.topic line.

28 files → concept-article: Explains features, capabilities, or system behavior (API removal policy, compatibility types, observability overview, grain concepts, placement strategies, lifecycle, request scheduling)

9 files → how-to: Contains numbered procedural steps (observability setup examples, event sourcing configuration, grain extensions implementation, versioning setup, GrainService creation)

3 files → article: Navigation hubs with minimal explanatory content (how-to index, additional APIs index, grains overview)

Classification Rationale

File	New Topic	Rationale
docs/core/compatibility/api-removal.md	concept-article	Explains .NET's policy for API obsolescence and removal without procedural steps
docs/core/compatibility/breaking-changes.md	concept-article	Reference document explaining how to navigate breaking changes, with links to resources
docs/core/compatibility/categories.md	concept-article	Conceptual explanation of compatibility types (behavioral, binary, source, etc.)
docs/core/compatibility/library-change-rules.md	concept-article	Explains rules and categories for library changes with allowed/disallowed examples
docs/core/diagnostics/observability-otlp-example.md	how-to	Step-by-step walkthrough with 8 numbered sections to create and configure a project
docs/core/diagnostics/observability-prgrja-example.md	how-to	Step-by-step walkthrough with 9 numbered sections to set up Prometheus, Grafana, and Jaeger
docs/core/diagnostics/observability-with-otel.md	concept-article	Conceptual overview of observability, OpenTelemetry, and .NET implementation
docs/core/resources/manifest-file-names.md	concept-article	Explains how MSBuild generates manifest file names with examples
docs/core/runtime-config/index.md	concept-article	Explains runtime configuration mechanisms and options without step-by-step setup
docs/csharp/how-to/index.md	article	Navigation hub with categorized links to how-to articles
docs/framework/additional-apis/index.md	article	Navigation hub listing OOB projects, platform-specific libraries, and private APIs
docs/machine-learning/resources/ml-net-cli-telemetry.md	how-to	Instructions for opting out of telemetry with specific environment variable steps
docs/orleans/dashboard/index.md	concept-article	Explains dashboard features, capabilities, and configuration options
docs/orleans/deployment/handling-failures.md	concept-article	Explains failure types and recovery strategies without prescriptive steps
docs/orleans/grains/code-generation.md	concept-article	Explains code generation concepts and when it occurs
docs/orleans/grains/event-sourcing/event-sourcing-configuration.md	how-to	Configuration instructions with XML and code examples for setting up event sourcing
docs/orleans/grains/event-sourcing/immediate-vs-delayed-confirmation.md	concept-article	Explains the differences and tradeoffs between confirmation approaches
docs/orleans/grains/event-sourcing/journaledgrain-basics.md	concept-article	Explains JournaledGrain API concepts (state, events, versioning)
docs/orleans/grains/event-sourcing/journaledgrain-diagnostics.md	concept-article	Explains diagnostics features like connection error monitoring
docs/orleans/grains/event-sourcing/log-consistency-providers.md	concept-article	Explains different log-consistency provider types and their characteristics
docs/orleans/grains/event-sourcing/notifications.md	concept-article	Explains notification concepts for state changes
docs/orleans/grains/event-sourcing/replicated-instances.md	concept-article	Explains replication concepts and conditional events
docs/orleans/grains/external-tasks-and-grains.md	concept-article	Explains task scheduling model and async behavior with examples
docs/orleans/grains/grain-extensions.md	how-to	Step-by-step instructions for creating and using grain extensions with two examples
docs/orleans/grains/grain-identity.md	concept-article	Explains grain identity concepts (type names, keys, schemes)
docs/orleans/grains/grain-lifecycle.md	concept-article	Explains lifecycle stages and participation patterns
docs/orleans/grains/grain-placement.md	concept-article	Explains placement strategies and how Orleans selects silos
docs/orleans/grains/grain-references.md	concept-article	Explains grain reference concepts and disambiguation methods
docs/orleans/grains/grain-versioning/backward-compatibility-guidelines.md	how-to	Prescriptive guidelines on what to do/not do for backward compatibility
docs/orleans/grains/grain-versioning/compatible-grains.md	concept-article	Explains compatibility concepts (backward compatible, fully compatible)
docs/orleans/grains/grain-versioning/grain-versioning.md	how-to	Instructions for enabling and configuring versioning with code examples
docs/orleans/grains/grain-versioning/version-selector-strategy.md	how-to	Instructions for choosing and configuring version selection strategies
docs/orleans/grains/grainservices.md	how-to	Step-by-step instructions (6 numbered steps) for creating a GrainService
docs/orleans/grains/index.md	article	Navigation hub for grain development topics with links to other articles
docs/orleans/grains/interceptors.md	concept-article	Explains grain call filter concepts and how they work
docs/orleans/grains/observers.md	concept-article	Explains observer pattern concepts with code examples
docs/orleans/grains/oneway.md	concept-article	Explains one-way request concepts and when to use them
docs/orleans/grains/request-context.md	concept-article	Explains RequestContext API and how metadata flows with requests
docs/orleans/grains/request-scheduling.md	concept-article	Explains request scheduling model and reentrancy concepts
docs/orleans/grains/stateless-worker-grains.md	concept-article	Explains stateless worker grain concepts and scaling behavior

Each file has exactly one ms.topic line (replaced, not added). No files remain as legacy topic types.

Original prompt

For the pull request title, you MUST use: "Reclassify ms.topic values batch 1 (entries 1 to 40)."

Get the entire contents of each markdown file up to a maximum of 300 lines, not just a portion. Ignore lines for title and description and classify the content into one of the following topics, based on the associated descriptions of each topic.

Here's a markdown table defining each topic type:

Slug	Definition
best-practice	Offers best practices recommendations for working with a service or feature.
concept-article	Provides an in-depth explanation of functionality, features, or components related to a service(s) that is fundamental to understanding and use. It describes what something is, what it does, and how it works at a conceptual level. The article may include code examples, commands, SQL statements, Kusto queries, PowerShell scripts, or configuration syntax to illustrate concepts, but these are presented as REFERENCE EXAMPLES showing "this is the syntax" or "this is what it looks like," NOT as a task-based sequence the user must follow. CRITICAL CODE EXAMPLE TEST: If an article shows code/queries under headings like "Examples," "Sample queries," or "Code samples" WITHOUT surrounding numbered procedural steps ("Step 1: Open... Step 2: Paste... Step 3: Run..."), that is concept-article, NOT how-to. The mere presence of code blocks does NOT make an article how-to. It shouldn't contain step-by-step procedural instructions for the user to follow, but might explain a high-level process flow and provide examples. It also shouldn't be task-oriented with explicit action items. May include bulleted lists describing what a feature or service does/can do without instructing the user how to do it. The system/feature is the subject being explained, not the user performing tasks. CRITICAL: If an article contains 2+ numbered steps, a Requirements or Prerequisites section, or imperatives directing user actions ("Ensure...", "Make sure to...", "Give permission...") that represent the PRIMARY purpose of the article, classify it as how-to even if other sections provide navigation or overview content.
end-user-help	Aimed at end users that provides a resolution on a specific issue.
error-reference	Reference content that documents error codes.
faq	Question-and-answer formatted content. (Has a .yml template.)
get-started	Helps users get started using a particular product or service. It's a basic high-level task to use as a proof-of-concept in a short timeframe.
glossary	Lists relevant terms for understanding and using a product, service, or scenario.
how-to	Contains numbered or bulleted PROCEDURAL STEPS that guide the customer through completing a specific task in sequence. The article's PRIMARY PURPOSE must be task completion with the user as the actor. The article must present steps in a clear sequential format (1, 2, 3... or Step 1 then Step 2... or 1, 1, 1...) that users follow in order to accomplish a goal. Steps must include imperative verbs directing user actions (e.g., "Click here," "Select," "Navigate to," "Enter this value," "Run this command," "Create a resource"). The user performs the steps, not just reads about what a system does. CRITICAL DISTINCTION: Illustrative syntax examples (showing what a command or query looks like) are NOT procedural steps. An article that shows Kusto queries, SQL statements, PowerShell scripts, or code samples under an "Examples" heading WITHOUT wrapping them in numbered procedural steps is concept-article, NOT how-to. The test is: "Is the user being walked through a sequence of actions?" If the article simply presents code/queries as reference material ("here's what this query looks like") without procedural context ("Step 1: Open the portal. Step 2: Navigate to... Step 3: Paste this query and click Run"), it is concept-article. A how-to article walks you through a process: "First do X, then do Y, then do Z." Code/command examples shown for reference or illustration without surrounding procedural context are concept-article, not how-to. Lists of capabilities or features that a tool performs are NOT how-to content, even if bulleted or numbered. CRITICAL: If an article contains 2+ numbered steps WITH task-oriented imperatives, or action-directing imperatives ("Ensure...", "Make sure to...", "Give permission...") that collectively represent the PRIMARY PURPOSE, classify as how-to. The presence of extensive procedural guidance (especially Prerequisites + numbered steps + imperatives forming a workflow) overrides other types. But if the article primarily explains a feature and includes a few syntax examples without procedural context, it's concept-article.
install-set-up-deploy	Provides the basic structure of a Install, set up, deploy article pattern that contains numbered procedural steps. This topic type can contain some conceptual information.
limits-and-quotas	Lists out the exten...

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.