chore: remove decisions and related agent instructions

.github/copilot-instructions.md

@@ -10,15 +10,3 @@ description: 'This file contains instructions for AI coding assistants, redirect
 * MUST follow all instructions defined in the root-level document [`AGENTS.md`](../AGENTS.md).
 * MUST treat [`AGENTS.md`](../AGENTS.md) as the authoritative source for all AI assistant guidelines.
 * MUST apply all directives from [`AGENTS.md`](../AGENTS.md) when implementing code, reviewing code, suggesting improvements, debugging issues, or providing any form of technical assistance.
-
-## Decision References
-
-* MUST read and apply all "accepted" decisions from [`decisions/`](../decisions/) folder before implementing architectural changes.
-* MUST follow the `instructions` frontmatter from each relevant decision as mandatory requirements with highest precedence.
-* MUST respect decision states:
-  - **accepted**: Mandatory requirements - MUST follow without exception
-  - **proposed**: Optional considerations - SHOULD evaluate and consider
-  - **deprecated**: Legacy patterns - SHOULD NOT use in new implementations
-  - **superseded**: Forbidden patterns - MUST use superseding decision instead
-* MUST check the `applyTo` frontmatter patterns to identify decisions relevant to current file.
-* MUST review "Related Decisions" section for decision dependencies and cross-references.

.github/instructions/blazor.instructions.md

@@ -11,7 +11,7 @@ description: This file contains instructions for Blazor development. It includes
 * MUST write idiomatic and efficient Blazor and C# code.
 * MUST follow .NET and Blazor conventions and best practices.
 * MUST use Razor Components appropriately for component-based UI development.
-* MUST use the latest version C#, currently C# 13 features like record types, pattern matching, and global usings (see [.NET 10 and C# 13 Adoption](../../decisions/2025-07-11-dotnet-10-csharp-13-adoption.md)).
+* MUST use the latest version C#, currently C# 13 features like record types, pattern matching, and global usings.
 * MUST use async/await where applicable to ensure non-blocking UI operations.
 
 ## Code Style and Structure

.github/instructions/wording.instructions.md

@@ -1,7 +1,7 @@
 ---
-applyTo: '.github/copilot-instructions.md, .github/instructions/*.instructions.md, decisions/**/*.md'
+applyTo: '.github/copilot-instructions.md, .github/instructions/*.instructions.md'
 
-description: 'This file contains instructions for wording and writing style. It includes guidelines for creating and modifying instruction files, decision documents, and Copilot instructions. Ensure to follow the practices outlined in this file to maintain consistency and clarity in documentation.'
+description: 'This file contains instructions for wording and writing style. It includes guidelines for creating and modifying instruction files and Copilot instructions. Ensure to follow the practices outlined in this file to maintain consistency and clarity in documentation.'
 ---
 
 # Wording and Writing Style Instructions
@@ -34,21 +34,13 @@ description: 'This file contains instructions for wording and writing style. It
 * MUST use code formatting (backticks) for code, file names, and technical terms.
 * MUST include both general principles and specific implementation details.
 
-## Decision Documents
-
-* MUST follow the established ADR (Architecture Decision Record) format.
-* MUST include all required frontmatter fields: authors, applyTo, created, lastModified, state.
-* MUST provide clear context and problem statements.
-* MUST explicitly state the decision and its implications.
-* MUST use consistent terminology when referring to technical concepts.
-
 ## Copilot Instructions
 
 * MUST structure guidance as imperative statements.
 * MUST group related instructions under appropriate section headings.
 * MUST explicitly state constraints and limitations.
 * MUST reference specific file paths, folders, or patterns when applicable.
-* MUST include cross-references to related decisions or instruction files when appropriate.
+* MUST include cross-references to related instruction files when appropriate.
 
 ## Examples and References
 

.github/prompts/csharp-docs.prompt.md

@@ -121,7 +121,6 @@ description: 'Ensure that C# types are documented with XML comments following Mi
 * MUST use `NotNullAttribute` and related nullable attributes in public API documentation when appropriate.
 * MUST use `nameof()` operator in examples instead of string literals when referring to member names.
 * MUST ensure that documentation examples properly demonstrate null-checking patterns using `is null` and `is not null`.
-* SHOULD reference related decisions or architectural guidelines when relevant to the API's design or usage.
 
 ## Accessibility and Localization
 

AGENTS.md

@@ -18,17 +18,6 @@ Use AI coding assistants, such as GitHub Copilot, to enhance productivity and ma
 * MUST consider the impact on existing workflows and user experience.
 * MUST evaluate the cost-benefit ratio of proposed changes or new implementations.
 
-## Decision References
-
-* MUST document all decisions in `decisions/` folder using `templates/adr.md` format.
-* MUST treat "accepted" decisions as mandatory requirements with highest precedence.
-* MUST respect decision states:
-  - **accepted**: mandatory requirements
-  - **proposed**: optional considerations
-  - **deprecated**: avoid in new implementations
-  - **superseded**: forbidden, follow superseding decision instead
-* MUST use the `instructions` frontmatter property as primary AI guidance for each decision.
-
 ## Configuration Files
 
 These files control project-wide settings and should remain unchanged unless specifically requested.