🤖 Number 5 is alive!

Author: PureKrome

.editorconfig

@@ -0,0 +1,158 @@
+# EditorConfig is awesome:
+http://EditorConfig.org
+
+
+#### How to manually clean up code in an IDE?
+
+#### - Visual Studio: CTRL + K + D
+#### - VSCode: SHIFT + ALT + F
+
+
+
+####################################################################################################
+
+### VS Settings Reference: https://docs.microsoft.com/en-us/visualstudio/ide/editorconfig-code-style-settings-reference
+
+
+
+
+# top-most EditorConfig file
+root = true
+
+# Default settings:
+# A newline ending every file
+# Use 4 spaces as indentation
+[*]
+insert_final_newline = true
+indent_style = space
+indent_size = 4
+end_of_line = crlf
+charset = utf-8
+trim_trailing_whitespace = true
+
+# C# files
+[*.cs]
+# New line preferences
+csharp_new_line_before_open_brace = all
+csharp_new_line_before_else = true
+csharp_new_line_before_catch = true
+csharp_new_line_before_finally = true
+csharp_new_line_before_members_in_object_initializers = true
+csharp_new_line_before_members_in_anonymous_types = true
+csharp_new_line_between_query_expression_clauses = true
+
+# Indentation preferences
+csharp_indent_block_contents = true
+csharp_indent_braces = false
+csharp_indent_case_contents = true
+csharp_indent_switch_labels = true
+csharp_indent_labels = one_less_than_current
+
+# Namespace preferences
+csharp_style_namespace_declarations = file_scoped:error
+
+# avoid this. unless absolutely necessary
+dotnet_style_qualification_for_field = false:suggestion
+dotnet_style_qualification_for_property = false:suggestion
+dotnet_style_qualification_for_method = false:suggestion
+dotnet_style_qualification_for_event = false:suggestion
+
+# only use var when it's obvious what the variable type is
+csharp_style_var_for_built_in_types = true:suggestion
+csharp_style_var_when_type_is_apparent = true:suggestion
+csharp_style_var_elsewhere = true:suggestion
+
+# use language keywords instead of BCL types
+dotnet_style_predefined_type_for_locals_parameters_members = true:suggestion
+dotnet_style_predefined_type_for_member_access = true:suggestion
+
+# name all constant fields using PascalCase
+dotnet_naming_rule.constant_fields_should_be_pascal_case.severity = suggestion
+dotnet_naming_rule.constant_fields_should_be_pascal_case.symbols  = constant_fields
+dotnet_naming_rule.constant_fields_should_be_pascal_case.style    = pascal_case_style
+
+dotnet_naming_symbols.constant_fields.applicable_kinds   = field
+dotnet_naming_symbols.constant_fields.required_modifiers = const
+
+dotnet_naming_style.pascal_case_style.capitalization = pascal_case
+
+# internal and private fields should be _camelCase
+dotnet_naming_rule.camel_case_for_private_internal_fields.severity = suggestion
+dotnet_naming_rule.camel_case_for_private_internal_fields.symbols  = private_internal_fields
+dotnet_naming_rule.camel_case_for_private_internal_fields.style    = camel_case_underscore_style
+
+dotnet_naming_symbols.private_internal_fields.applicable_kinds = field
+dotnet_naming_symbols.private_internal_fields.applicable_accessibilities = private, internal
+
+dotnet_naming_style.camel_case_underscore_style.required_prefix = _
+dotnet_naming_style.camel_case_underscore_style.capitalization = camel_case
+
+# Code style defaults
+dotnet_sort_system_directives_first = true
+csharp_preserve_single_line_blocks = true
+csharp_preserve_single_line_statements = false
+
+# Expression-level preferences
+dotnet_style_object_initializer = true:suggestion
+dotnet_style_collection_initializer = true:suggestion
+dotnet_style_explicit_tuple_names = true:suggestion
+dotnet_style_coalesce_expression = true:suggestion
+dotnet_style_null_propagation = true:suggestion
+
+# Expression-bodied members
+csharp_style_expression_bodied_methods = false:none
+csharp_style_expression_bodied_constructors = false:none
+csharp_style_expression_bodied_operators = false:none
+csharp_style_expression_bodied_properties = true:none
+csharp_style_expression_bodied_indexers = true:none
+csharp_style_expression_bodied_accessors = true:none
+
+# Pattern matching
+csharp_style_pattern_matching_over_is_with_cast_check = true:suggestion
+csharp_style_pattern_matching_over_as_with_null_check = true:suggestion
+csharp_style_inlined_variable_declaration = true:suggestion
+
+# Null checking preferences
+csharp_style_throw_expression = true:suggestion
+csharp_style_conditional_delegate_call = true:suggestion
+
+# Space preferences
+csharp_space_after_cast = false
+csharp_space_after_colon_in_inheritance_clause = true
+csharp_space_after_comma = true
+csharp_space_after_dot = false
+csharp_space_after_keywords_in_control_flow_statements = true
+csharp_space_after_semicolon_in_for_statement = true
+csharp_space_around_binary_operators = before_and_after
+csharp_space_around_declaration_statements = do_not_ignore
+csharp_space_before_colon_in_inheritance_clause = true
+csharp_space_before_comma = false
+csharp_space_before_dot = false
+csharp_space_before_open_square_brackets = false
+csharp_space_before_semicolon_in_for_statement = false
+csharp_space_between_empty_square_brackets = false
+csharp_space_between_method_call_empty_parameter_list_parentheses = false
+csharp_space_between_method_call_name_and_opening_parenthesis = false
+csharp_space_between_method_call_parameter_list_parentheses = false
+csharp_space_between_method_declaration_empty_parameter_list_parentheses = false
+csharp_space_between_method_declaration_name_and_open_parenthesis = false
+csharp_space_between_method_declaration_parameter_list_parentheses = false
+csharp_space_between_parentheses = false
+csharp_space_between_square_brackets = false
+
+[*.{asm,inc}]
+indent_size = 8
+
+# Xml project files
+[*.{csproj,vcxproj,vcxproj.filters,proj,nativeproj,locproj}]
+indent_size = 2
+
+# Xml config files
+[*.{props,targets,config,nuspec}]
+indent_size = 2
+
+[CMakeLists.txt]
+indent_size = 2
+
+[*.cmd]
+indent_size = 2

.gitattributes

@@ -0,0 +1 @@
+* -text

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at help@world-domination.com.au. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

.github/CONTRIBUTING.md

@@ -0,0 +1,49 @@
+# How to contribute
+
+One of the easiest ways to contribute is to participate in discussions and discuss issues. You can also contribute by submitting pull requests with code changes.
+
+## Filing issues
+- Don't be afraid to ask any question about the project, including suggestions to change how things currently are. 
+- Keep the conversation polite and respectful. This way, all parties will take an interest in your question and will be more proactive into helping.
+- For bugs, the best way to get your bug fixed is to be as detailed as you can be about the problem. Providing a minimal project with steps to reproduce the problem is ideal. Even though this might be frustrating, it can speed up the resolution to the problem.
+
+Helpful tip: GitHub supports [markdown](https://help.github.com/articles/github-flavored-markdown/), so when filing bugs make sure you check the formatting before clicking submit.
+
+## Contributing code and content
+
+**Identifying the scale**
+
+If you would like to contribute to the project, first identify the "scale" of what you would like to contribute. If it is small (grammar/spelling or a bug fix) feel free to start working on a fix. If you are submitting a feature or substantial code contribution, please discuss it with the team, via an Issue. 
+
+You might also read these two blogs posts on contributing code: [Open Source Contribution Etiquette](http://tirania.org/blog/archive/2010/Dec-31.html) by Miguel de Icaza and [Don't "Push" Your Pull Requests](https://www.igvita.com/2011/12/19/dont-push-your-pull-requests/) by Ilya Grigorik. Note that all code submissions will be reviewed and tested by team members. Of course (where appropriate), tests will be required.
+
+**Obtaining the source code**
+
+If you are an outside contributer, please fork the repository to your own GitHub account. See the GitHub documentation for [forking a repo](https://help.github.com/articles/fork-a-repo/) if you have any questions about this. 
+
+**Submitting a Pull Request**
+
+If you don't know what a Pull Request is read then please read the article [Using Pull Requests](https://help.github.com/articles/using-pull-requests) to get up-to-speed. Make sure the respository can build and all tests pass. Familiarize yourself with the project workflow and our coding conventions. 
+
+Pull Requests should all be done to the `main` branch.
+
+**Commit/Pull Request Format**
+
+```
+Summary of the changes (Less than 80 chars)
+ - Detail 1
+ - Detail 2
+
+Addresses #bugnumber (in this specific format)
+```
+
+**Tests**
+
+-  Tests need to be provided for every bug/feature that is completed.
+-  Tests only need to be present for issues that need to be verified by QA (e.g. not tasks)
+-  If there is a scenario that is far _too hard*_ to test there does not need to be a test for it.
+
+
+*"_Too hard_" is determined by the team as a whole.
+
+---

.github/FUNDING.yml

@@ -0,0 +1 @@
+custom: ['https://paypal.me/purekrome']

.github/copilot-instructions.md

@@ -0,0 +1,131 @@
+# GitHub Copilot Instructions
+
+## Project Context
+
+This is a project focused on two parts
+- A .NET website to observe the health of various servers that expose a standard schema. Intended use is via a docker instance
+- A list of projects (per language) that are easy to use libraries that expose that standard observability schema
+The codebase emphasizes simplicity, developer experience, and production-ready patterns
+
+## Code Style & Standards
+
+### General .NET Guidelines
+- Use modern C# features (pattern matching, records, nullable reference types, file-scoped namespaces)
+- Follow Microsoft's C# coding conventions (enforced via `.editorconfig`)
+- Prefer `async`/`await` for I/O operations
+- Use meaningful, descriptive names (avoid abbreviations unless widely known)
+- All comments should be in English and finish with a period
+
+### Code Organization
+- Use file-scoped namespaces
+- One class per file (match filename to class name)
+- Group using statements (System namespaces first, then third-party, then local)
+- Order class members: fields, constructors, properties, methods (public before private)
+
+### Error Handling
+- Use exceptions for exceptional cases, not control flow
+- Provide meaningful exception messages with context
+- Use guard clauses for parameter validation
+- Consider custom exceptions for domain-specific errors
+- Always validate input parameters (use ArgumentNullException, ArgumentException)
+
+### Async/Await
+- Always use `ConfigureAwait(false)` in library code (not in ASP.NET Core endpoints)
+- Pass `CancellationToken` to all async methods
+- Don't use `.Result` or `.Wait()` - always await
+- Return `Task` or `Task<T>`, not `async void` (except event handlers)
+
+### Logging
+- Use structured logging with ILogger
+- Include relevant context in log messages
+- Use appropriate log levels (Trace, Debug, Information, Warning, Error, Critical)
+- Log at method entry/exit for important operations
+- Include correlation IDs where applicable
+
+### Testing
+- Write unit tests for all public APIs
+- Use xUnit as the testing framework and specifically xunit v3 using the latest Microsft Test Platform version
+- Follow AAA pattern (Arrange, Act, Assert)
+- Always comment in a test the "Arrange.", "Act.", and "Assert." sections
+- Use meaningful test names (e.g., `AddMessageAsync_WithLargeContent_StoresInBlob`)
+- Mock external dependencies (use Moq or NSubstitute)
+- Aim for high code coverage on business logic
+- Each method being tested should have it's own class to xunit can run tests in parallel
+- Each method being tested should have at least one test for success and one for failure
+
+### Documentation
+- Use XML documentation comments for public APIs
+- Include `<summary>`, `<param>`, `<returns>`, and `<exception>` tags
+- Provide code examples in remarks when helpful
+- Keep README.md updated with examples
+- Document breaking changes in release notes
+
+### Performance
+- Avoid allocations in hot paths
+- Use `Span<T>`, `Memory<T>`, and `ReadOnlySpan<T>` where appropriate
+- Consider object pooling for frequently allocated objects
+- Profile before optimizing
+- Use `ValueTask<T>` for high-performance scenarios
+
+### Dependencies
+- Minimize external dependencies
+- Use well-maintained, popular NuGet packages
+- Keep packages up-to-date
+- Prefer Microsoft packages for common functionality
+- Review package licenses for compatibility
+
+### Design Patterns
+- Favor composition over inheritance
+- Use dependency injection
+- Apply SOLID principles
+- Keep classes focused (Single Responsibility Principle)
+- Program to interfaces, not implementations
+- Use builder pattern for complex object construction
+
+### Records and Data Types
+- Use `record` for DTOs and immutable data
+- Use `readonly struct` for small, immutable value types
+- Prefer immutability where possible
+- Use nullable reference types (`?`) appropriately
+
+### API Design
+- Keep public API surface small and focused
+- Make it hard to use incorrectly (pit of success)
+- Provide async methods for I/O operations
+- Accept interfaces in constructors, return concrete types
+- Version APIs carefully to avoid breaking changes
+
+## What NOT to Do
+
+- ❌ Don't ignore CA (Code Analysis) warnings without justification
+- ❌ Don't commit commented-out code
+- ❌ Don't use magic numbers/strings (use constants)
+- ❌ Don't catch generic exceptions without rethrowing
+- ❌ Don't use `Thread.Sleep` in async code (use `Task.Delay`)
+- ❌ Don't expose internal implementation details in public APIs
+- ❌ Don't write methods longer than ~50 lines (refactor into smaller methods)
+- ❌ Don't use regions to hide code
+- ❌ Don't use dynamic types
+- ❌ Don't use static classes for stateful operations
+- ❌ Don't use Automapper or MediatR
+
+## Code Review Checklist
+
+When reviewing code suggestions, ensure:
+- [ ] Code follows project conventions
+- [ ] All public APIs have XML documentation
+- [ ] Async methods use `CancellationToken`
+- [ ] Proper exception handling is in place
+- [ ] Tests are included for new functionality
+- [ ] No hardcoded values (use configuration)
+- [ ] Logging is appropriate and structured
+- [ ] Performance implications are considered
+- [ ] Breaking changes are documented
+
+## Additional Context
+
+- This project prioritizes **simplicity** and **developer experience**
+- Code should be self-documenting where possible
+- Favor clarity over cleverness
+- Consider the library consumer's perspective
+- Maintain backward compatibility when possible