Work in progress

Author: pwelter34

.editorconfig

@@ -0,0 +1,54 @@
+# EditorConfig: https://EditorConfig.org
+
+root = true
+
+# All Files
+[*]
+charset = utf-8
+indent_style = space
+indent_size = 4
+insert_final_newline = true
+trim_trailing_whitespace = true
+vsspell_section_id = main
+vsspell_ignored_words_main = File:dictionary.dic
+
+# XML Configuration Files
+[*.{xml,config,props,targets,nuspec,resx,ruleset,vsixmanifest,vsct,refactorlog,runsettings}]
+indent_size = 2
+
+# JSON Files
+[*.{json,json5,webmanifest}]
+indent_size = 2
+
+# Project Files
+[*.{csproj,sqlproj}]
+indent_size = 2
+
+# YAML Files
+[*.{yml,yaml}]
+indent_size = 2
+
+# Markdown Files
+[*.md]
+trim_trailing_whitespace = false
+
+# Web Files
+[*.{htm,html,js,jsm,ts,tsx,css,sass,scss,less,pcss,svg,vue}]
+indent_size = 2
+
+# Batch Files
+[*.{cmd,bat}]
+end_of_line = crlf
+
+# Bash Files
+[*.sh]
+end_of_line = lf
+
+[*.{cs,vb}]
+dotnet_sort_system_directives_first = true
+dotnet_separate_import_directive_groups = true
+dotnet_style_namespace_match_folder = true
+
+[*.cs]
+csharp_using_directive_placement = outside_namespace
+csharp_style_namespace_declarations = file_scoped:warning

.gitattributes

@@ -0,0 +1,63 @@
+###############################################################################
+# Set default behavior to automatically normalize line endings.
+###############################################################################
+* text=auto
+
+###############################################################################
+# Set default behavior for command prompt diff.
+#
+# This is need for earlier builds of msysgit that does not have it on by
+# default for csharp files.
+# Note: This is only used by command line
+###############################################################################
+#*.cs     diff=csharp
+
+###############################################################################
+# Set the merge driver for project and solution files
+#
+# Merging from the command prompt will add diff markers to the files if there
+# are conflicts (Merging from VS is not affected by the settings below, in VS
+# the diff markers are never inserted). Diff markers may cause the following 
+# file extensions to fail to load in VS. An alternative would be to treat
+# these files as binary and thus will always conflict and require user
+# intervention with every merge. To do so, just uncomment the entries below
+###############################################################################
+#*.sln       merge=binary
+#*.csproj    merge=binary
+#*.vbproj    merge=binary
+#*.vcxproj   merge=binary
+#*.vcproj    merge=binary
+#*.dbproj    merge=binary
+#*.fsproj    merge=binary
+#*.lsproj    merge=binary
+#*.wixproj   merge=binary
+#*.modelproj merge=binary
+#*.sqlproj   merge=binary
+#*.wwaproj   merge=binary
+
+###############################################################################
+# behavior for image files
+#
+# image files are treated as binary by default.
+###############################################################################
+#*.jpg   binary
+#*.png   binary
+#*.gif   binary
+
+###############################################################################
+# diff behavior for common document formats
+# 
+# Convert binary document formats to text before diffing them. This feature
+# is only available from the command line. Turn it on by uncommenting the 
+# entries below.
+###############################################################################
+#*.doc   diff=astextplain
+#*.DOC   diff=astextplain
+#*.docx  diff=astextplain
+#*.DOCX  diff=astextplain
+#*.dot   diff=astextplain
+#*.DOT   diff=astextplain
+#*.pdf   diff=astextplain
+#*.PDF   diff=astextplain
+#*.rtf   diff=astextplain
+#*.RTF   diff=astextplain

.github/copilot-instructions.md

@@ -0,0 +1,21 @@
+# Foundatio.Mediator – AI agent guide
+
+Use this when coding in this repo. Keep advice specific; reference files/paths.
+
+## Key Principles
+
+All contributions must respect existing formatting and conventions specified in the `.editorconfig` file. You are a distinguished engineer and are expected to deliver high-quality code that adheres to the guidelines in the instruction files.
+
+Let's keep pushing for clarity, usability, and excellence—both in code and user experience.
+
+**See also:**
+
+- [General Coding Guidelines](instructions/general.instructions.md)
+- [Testing Guidelines](instructions/testing.instructions.md)
+
+## Commenting style
+- Keep comments to a minimum.
+- Only add comments when intent is not obvious or when explaining complex logic, tricky edge cases, or non-trivial performance/interop considerations.
+- Prefer clear naming and small, self-explanatory functions over explanatory comments.
+- Avoid boilerplate and restating what the code already says.
+

.github/dependabot.yml

@@ -0,0 +1,57 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: daily
+      time: "01:00"
+      timezone: "America/Chicago"
+    open-pull-requests-limit: 10
+
+  - package-ecosystem: nuget
+    directory: "/"
+    schedule:
+      interval: daily
+      time: "02:00"
+      timezone: "America/Chicago"
+    open-pull-requests-limit: 10
+    groups:
+      Azure:
+        patterns:
+          - "Azure.*"
+          - "Microsoft.Azure.*"
+          - "Microsoft.Extensions.Azure"
+      AspNetCoreHealthChecks:
+        patterns:
+          - "AspNetCore.HealthChecks.*"
+      AspNetCore:
+        patterns:
+          - "Microsoft.AspNetCore.*"
+          - "Microsoft.Extensions.Features"
+      MicrosoftExtensions:
+        patterns:
+          - "Microsoft.Extensions.*"
+      EntityFrameworkCore:
+        patterns:
+          - "Microsoft.EntityFrameworkCore.*"
+      OpenTelemetry:
+        patterns:
+          - "OpenTelemetry.*"
+      Serilog:
+        patterns:
+          - "Serilog"
+          - "Serilog.*"
+      Hangfire:
+        patterns:
+          - "Hangfire"
+          - "Hangfire.*"
+      Testcontainers:
+        patterns:
+          - "Testcontainers.*"
+      xUnit:
+        patterns:
+          - "xunit"
+          - "xunit.assert"
+          - "xunit.core"
+          - "xunit.extensibility.*"
+          - "xunit.runner.*"

.github/instructions/general.instructions.md

@@ -0,0 +1,73 @@
+---
+description: "General coding guidelines"
+applyTo: "**"
+---
+
+# General Coding Guidelines
+
+You are a distinguished engineer and are expected to deliver high-quality code that adheres to the guidelines below.
+All contributions must respect existing formatting and conventions specified in the `.editorconfig` file and
+Microsoft's [coding conventions](https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions).
+
+Code can be formatted with `dotnet format` and checked for errors with `dotnet build`.
+
+Use context7 for documentation
+
+## Code Style & Minimal Diffs
+
+- Match the file's existing style; use `.editorconfig` when unsure.
+- Preserve extra spaces, comments, and minimize diffs.
+- Always ask before creating new files, directories, or changing existing structures.
+- Always look at existing usages before refactoring or changing code to prevent new code from breaking existing code.
+- Assume any existing uncommitted code is correct and ask before changing it.
+- Don't add code comments unless necessary. Code should be self-explanatory.
+- Don't use deprecated or insecure libraries, algorithms or features.
+
+## Modern Code Practices
+
+- Write complete, runnable code—no placeholders or TODOs.
+- Use modern language features, clear naming conventions, and defensive coding when necessary.
+- Follow SOLID, DRY, and clean code principles. Remove unused code.
+
+## Behavior Management
+
+- Flag any user-visible changes for review.
+- Deliver exactly what's requested—avoid adding unnecessary features unless explicitly instructed.
+
+## Security Guidelines
+
+- Sanitize all user inputs and rigorously validate data.
+- Follow OWASP guidelines and implement a robust Content Security Policy.
+- Adopt Shift-Left security practices to identify vulnerabilities early.
+
+## Developer Planning & Reflection
+
+### Pre-Coding Reflection
+
+1. Identify the problem or feature you're solving.
+2. Consider three possible approaches.
+3. Choose the simplest approach that satisfies all requirements.
+4. Clarify:
+    - Can the solution be modularized into smaller functions?
+    - Are there unnecessary abstractions?
+    - Will the implementation be clear to a junior developer?
+
+### Post-Coding Reflection
+
+1. Review for refactor opportunities—can clarity or maintainability be improved?
+2. Identify potential edge cases or areas prone to bugs.
+3. Verify robust error handling and validation mechanisms.
+
+## Code Reviews
+
+- Ensure adherence to complexity, consistency, and clean code standards.
+- Validate robust error handling and defensive coding practices.
+- Check for duplication and maintainable solutions.
+
+## Debugging Guidelines
+
+1. **Reproduce** the issue with minimal steps and code.
+2. **Understand** the underlying problem thoroughly.
+3. **Form Hypotheses** about the cause.
+4. **Test & Verify** potential solutions.
+5. **Document** fixes and adjustments clearly for future reference.

.github/instructions/testing.instructions.md

@@ -0,0 +1,37 @@
+---
+description: "C# testing guidelines"
+applyTo: "tests/**/*.cs"
+---
+
+# Testing Guidelines (C#)
+
+## Framework & Best Practices
+
+- Follow Microsoft's [unit testing best practices](https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-best-practices).
+- Use xUnit as the primary testing framework.
+- Use AwesomeAssertions for fluent assertions.
+
+## Test Principles
+
+- **Fast & Isolated**: Tests should execute quickly and not depend on external factors or the order of execution.
+- **Repeatable & Self-Checking**: Tests must be consistent and validate their own outcomes without manual checks.
+- **Timely**: Write tests alongside your code to ensure relevance and improve design.
+
+## Test Structure & Naming
+
+- Write complete, runnable tests—no placeholders or TODOs.
+- Use clear, descriptive naming conventions for test methods:
+    - `MethodName_StateUnderTest_ExpectedBehavior`
+- Follow AAA pattern (Arrange, Act, Assert).
+
+## Test Organization
+
+- Use `[Theory]` and `[InlineData]` for parameterized tests.
+- Implement proper setup and teardown using constructors and `IDisposable`.
+- Tests are organized to mirror the main code structure (e.g., `Storage/` in both `src` and `tests`).
+
+## Integration Testing
+
+- Inject `ITestOutputHelper` into the test class constructor to get access to the test output.
+- Isolate dependencies using test containers, in-memory providers, or stubs to ensure reliable test execution.
+- Verify data persistence and side effects.