Update .gitignore and project configuration; exclude .venv and esp32 directories

Author: DefinetlyNotAI

.gitignore

@@ -152,7 +152,4 @@ dmypy.json
 
 # Cython debug symbols
 cython_debug/
-/esp32/
-esp32
-esp32/
-esp32/*
+esp32/

.idea/.gitignore

@@ -0,0 +1,10 @@
+# To-Do List
+
+> [!TIP]
+> Here is a key for the table above:
+> - ❌ ➡️ Might be done, Not sure yet
+> - ✅ ➡️ Will be done, 100% sure
+
+| Task                     | Expected Version | Might or Will be done? |
+|--------------------------|------------------|------------------------|
+| Add esp8266 capabilities | v2.0.0           | ❌                      |

.idea/.name

@@ -0,0 +1,56 @@
+# Security Policy
+
+## Supported Versions
+
+This section outlines the versions of our project that are currently supported with security updates.
+
+| Version | Supported | Release Date |
+|---------|-----------|--------------|
+| 1.0.x   | ✅         | Apr 7, 2025  |
+
+
+### Key:
+
+| Key | Desc                                                |
+|-----|-----------------------------------------------------|
+| ✅   | Supported for all security updates                  |
+| ⚠️  | Supported, but will leave support next major update |
+| ✖️  | Only for major security issues (CVSS 8.0+)          |
+| ❌   | No longer supported for any security updates        |
+
+## Reporting a Vulnerability
+
+If you believe you have found a security vulnerability in our project, we encourage you to report it to us. Your report
+will help us improve the security of our project and ensure the trust of our users.
+
+### How to Report a Vulnerability
+
+1. **Identify the Vulnerability**: Clearly describe the vulnerability, including how it can be exploited and any
+   potential impact.
+2. **Provide Detailed Information**: Include as much detail as possible, such as the version of the project affected,
+   steps to reproduce the vulnerability, and any relevant code snippets or screenshots.
+3. **Contact Us**: Send your report to my [email](mailto:[email protected]). Please include "Security Vulnerability
+   Report" in the subject line.
+
+### What to Expect
+
+- **Acknowledgment**: Upon receiving your report, we will acknowledge receipt within 2�5 business days.
+- **Investigation**: Our security team will investigate the vulnerability and determine its validity.
+- **Update**: If the vulnerability is accepted, we will work on a fix and provide an update on the timeline for a
+  security update.
+- **Communication**: We will communicate with you regarding the status of the vulnerability and any necessary actions.
+
+### Vulnerability Acceptance Criteria
+
+- The vulnerability must be reproducible.
+- The vulnerability must be exploitable.
+- The vulnerability must not be a false positive.
+
+### Vulnerability Decline Criteria
+
+- The vulnerability is outside the scope of our project.
+
+Thank you for helping us maintain the security of our project. Your contribution is invaluable in keeping our users
+safe.
+
+---