Add project files.

doc/bounty/bounty-announcement-template.md

@@ -0,0 +1,17 @@
+## Bounty Candidacy Announcement
+
+I am announcing my intention to tackle this bounty issue. Below is my acknowledgment of the key eligibility requirements and rules of the Elsa Workflows Bounty Hunting Program:
+
+- [ ] I have a GitHub account set up for receiving payments via GitHub Sponsors.
+- [ ] I understand this issue is assigned on a "First Come, First Served" basis.
+- [ ] I am aware of the specific time limit for this issue and commit to submitting my solution within this timeframe.
+- [ ] I understand that I must first describe my proposed solution in a comment on this issue or via a discussion linked to this bounty, before starting my work.
+- [ ] I have reviewed the [Bounty Hunting Program Guidelines](#5211) in detail.
+
+**GitHub Username**: `YourGitHubUsernameHere`
+
+**Estimated Start Date**: `YYYY-MM-DD`
+
+**Notes/Comments**: `Any additional comments or notes you wish to add`
+
+By checking the boxes above, I signify my understanding and acceptance of the program rules and confirm my intent to proceed with resolving this issue as per the guidelines of the Elsa Workflows Bounty Hunting Program.

doc/bounty/bounty-footer.md

@@ -0,0 +1,35 @@
+⭐ **This Issue is Part of the Elsa Workflows Bounty Hunting Program** ⭐
+
+Are you ready to contribute and earn rewards for your efforts?
+This issue offers a bounty for the first eligible contributor who successfully resolves it within the designated time limit, according to our comprehensive program rules.
+
+**Before You Start**:
+- Ensure you have a GitHub account set up to receive payments via GitHub Sponsors.
+- Publicly announce your intention to tackle this issue by commenting below. This follows our "First Come, First Served" rule.
+- Be aware of the specific time limit for this issue, as failing to submit a solution within this timeframe may open the opportunity for others.
+
+📜 **For a detailed overview of participation, submission guidelines, and the process for claiming rewards, please visit our [Bounty Hunting Program Guidelines](https://github.com/elsa-workflows/elsa-core/issues/5211).**
+
+To announce your intention to claim this bounty, please comment below. You can use this template:
+
+\`\`\`markdown
+## Bounty Candidacy Announcement
+
+I am announcing my intention to tackle this bounty issue. Below is my acknowledgment of the key eligibility requirements and rules of the Elsa Workflows Bounty Hunting Program:
+
+- [ ] I have a GitHub account set up for receiving payments via GitHub Sponsors.
+- [ ] I understand this issue is assigned on a "First Come, First Served" basis.
+- [ ] I am aware of the specific time limit for this issue and commit to submitting my solution within this timeframe.
+- [ ] I understand that I must first describe my proposed solution in a comment on this issue or via a discussion linked to this bounty, before starting my work.
+- [ ] I have reviewed the [Bounty Hunting Program Guidelines](#5211) in detail.
+
+**GitHub Username**: \`YourGitHubUsernameHere\`
+
+**Estimated Start Date**: \`YYYY-MM-DD\`
+
+**Notes/Comments**: \`Any additional comments or notes you wish to add\`
+
+By checking the boxes above, I signify my understanding and acceptance of the program rules and confirm my intent to proceed with resolving this issue as per the guidelines of the Elsa Workflows Bounty Hunting Program.
+\`\`\`
+
+We value your contributions to Elsa Workflows and are excited to see the innovative solutions you bring. Let's enhance Elsa Workflows together!

doc/bounty/bounty-quality-standards.md

@@ -0,0 +1,40 @@
+# Pull Request Quality Standard Checklist
+
+## Coding Standards
+- [ ] Follows [Microsoft's coding guidelines](https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions), with the following exceptions:
+  - **Use of `var`**: Use `var` for variable declarations consistently. See rationale below.
+
+## Documentation
+- [ ] XML comments provided for all public members.
+- [ ] Inline comments explain complex logic.
+
+## Testing
+- [ ] Unit tests cover critical functions.
+- [ ] Integration tests for major workflows.
+- [ ] High code coverage.
+
+## Code Review
+- [ ] Peer review completed.
+- [ ] Passes automated code analysis.
+
+## Continuous Integration
+- [ ] CI checks pass (builds, tests, style checks).
+
+## Performance and Security
+- [ ] Performance is optimized where necessary.
+- [ ] Security best practices followed.
+
+## Dependencies and Compatibility
+- [ ] Dependencies are managed and up to date.
+- [ ] No breaking changes without documentation.
+
+### Rationale for Using `var`
+
+We have chosen to use `var` consistently in our codebase for the following reasons:
+
+1. **Cleaner Code**: Using `var` reduces visual clutter and makes the code cleaner and more readable. It helps avoid redundant type information, especially when the type is already apparent from the right-hand side of the declaration.
+2. **Modern IDEs**: Tools like Visual Studio and other modern IDEs provide features such as hover or tool tips that easily display variable types, alleviating concerns about readability. This makes it unnecessary to explicitly specify the type, as it can be easily inferred by the developer.
+3. **Consistency and Maintenance**: Consistent use of `var` across the codebase promotes uniformity and reduces the mental load on developers. It simplifies refactoring because changes to the type do not require updating the variable declaration.
+4. **Focus on Logic**: By using `var`, developers can focus on the logic and functionality of the code rather than getting bogged down by type details. This is particularly beneficial in complex expressions and LINQ queries where the type is often verbose and less important than the expression itself.
+
+These points align with the insights from Chris Schaller's blog post "To var or not to var," which emphasizes that using `var` can lead to more maintainable and readable code in the context of modern development environments.