chore: Update project configuration and documentation for improved development experience

- Added coverage-php.txt to .gitignore to prevent tracking of coverage reports.
- Refactored .php-cs-fixer.dist.php to align with Symfony standards and removed deprecated rules.
- Updated composer.json to require PHP 8.1 and added new development dependencies for PHPStan and Rector.
- Enhanced Makefile with new targets for Rector and PHPStan, improving code quality checks.
- Updated CI configuration to support PHP 8.1-8.3 and improved caching strategy.
- Expanded README with additional documentation links and clarified package removal process.
- Adjusted PHPUnit configuration to separate unit and integration tests.
- Improved error handling in FrameworkDetector for better resilience against invalid composer.json files.

Author: HecFranco

.cursor/mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "engram": {
+      "command": "engram",
+      "args": ["mcp"]
+    }
+  }
+}

.github/CODEOWNERS

@@ -1,7 +1,5 @@
-# Code Owners for Code Review Guardian
-# These users will be automatically requested for review when someone opens a pull request
-
-# Default owner for everything in the repo
+# CODEOWNERS for CodeReviewGuardian
+# Default owner for everything in the repository
 * @HecFranco
 
 # GitHub Actions workflows

.github/ISSUE_TEMPLATE/---bug-report.md

@@ -0,0 +1,40 @@
+---
+name: "🐞 Bug report"
+about: Something is broken?
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+<!--
+- Please do not report an issue for a version of `code-review-guardian` that is no longer supported. Currently supported versions are listed here: https://github.com/nowo-tech/CodeReviewGuardian#version-information
+- Please fill in this template according to your issue.
+- Please keep the table shown below at the top of your issue.
+- You can retrieve `code-review-guardian` version by running `composer info | grep "code-review-guardian"`.
+- You can retrieve PHP version by running `php -v`.
+- Please post code as text (using proper markup). Do not post screenshots of code.
+- Please remove this comment before submitting your issue.
+-->
+
+| Q                           | A
+| ----------------------------| -----------------------
+| `CodeReviewGuardian` version | x.y.z
+| PHP version                 | x.y.z
+| Database                    | MySQL / PostgreSQL / SQLite / Other
+
+#### Summary
+
+<!-- Provide a summary describing the problem you are experiencing. -->
+
+#### Current behavior
+
+<!-- What is the current (buggy) behavior? -->
+
+#### How to reproduce
+
+<!-- Provide steps to reproduce the bug. -->
+
+#### Expected behavior
+
+<!-- What was the expected (correct) behavior? -->

.github/ISSUE_TEMPLATE/---feature-request.md

@@ -0,0 +1,10 @@
+---
+name: "🎉 Feature Request"
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+<!-- Provide a summary of the feature you would like to see implemented. -->

.github/ISSUE_TEMPLATE/--support-question.md

@@ -0,0 +1,10 @@
+---
+name: "❓ Support Question"
+about: You have a question about this bundle or need help?
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+

.github/ISSUE_TEMPLATE/bug_report.md

@@ -18,7 +18,7 @@ Fixes # (issue number)
 - [ ] I have added tests that prove my fix is effective or that my feature works
 - [ ] New and existing unit tests pass locally with my changes
 - [ ] I have updated the documentation accordingly
-- [ ] I have updated the CHANGELOG.md if applicable
+- [ ] I have updated `docs/CHANGELOG.md` if applicable
 
 ## Testing
 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -8,43 +8,28 @@
 
 ## Reporting a Vulnerability
 
-We take the security of Code Review Guardian seriously. If you believe you have found a security vulnerability, please report it to us as described below.
+We take the security of CodeReviewGuardian seriously. If you believe you have found a security vulnerability, please report it privately:
 
-### How to Report
+- **Email**: hectorfranco@nowo.tech
+- **Do not** open a public GitHub issue for security-sensitive bugs.
 
-**Please do not report security vulnerabilities through public GitHub issues.**
+Please include:
 
-Instead, please send an email to: **hectorfranco@nowo.tech**
+- Type of issue (e.g., injection, XSS, auth bypass, deserialization risk, etc.)
+- Affected file(s) and version/tag/commit
+- Steps to reproduce
+- Impact assessment
+- PoC (if available)
 
-Include the following information in your report:
+## Response Timeline
 
-- Type of issue (e.g., buffer overflow, SQL injection, cross-site scripting, etc.)
-- Full paths of source file(s) related to the issue
-- The location of the affected source code (tag/branch/commit or direct URL)
-- Any special configuration required to reproduce the issue
-- Step-by-step instructions to reproduce the issue
-- Proof-of-concept or exploit code (if possible)
-- Impact of the issue, including how an attacker might exploit it
+- Initial acknowledgment: within 48 hours
+- Follow-up status: within 7 days
+- Resolution: depends on complexity and impact
 
-### Response Timeline
-
-- **Initial Response**: Within 48 hours
-- **Status Update**: Within 7 days
-- **Resolution**: Varies depending on complexity
-
-### Disclosure Policy
-
-- We will confirm receipt of your vulnerability report
-- We will work with you to understand and validate the issue
-- We will develop and release a fix as quickly as possible
-- We will publicly acknowledge your responsible disclosure (if desired)
-
-## Preferred Languages
-
-We prefer all communications to be in English or Spanish.
-
-## Contact
-
-- **Maintainer**: [Héctor Franco Aceituno](https://github.com/HecFranco)
-- **Organization**: [nowo-tech](https://github.com/nowo-tech)
+## Disclosure Policy
 
+- We confirm receipt and validate the report.
+- We prepare and publish a fix as soon as possible.
+- We coordinate disclosure with the reporter.
+- We credit responsible disclosure (unless anonymity is requested).