Historical Candle Fixes - Balance Fixes - Documentation Specification - Etc

.github/FUNDING.yml

@@ -1,7 +1,7 @@
-# These are supported funding model platforms
+# Supported funding model platforms
 
 # GitHub Sponsors
-# github: [ChipaDevTeam]
+github: [ChipaDevTeam]
 
 # Custom funding links
 custom: ["https://discord.gg/p7YyFqSmAz"]

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,45 +1,56 @@
 ---
 name: Bug Report
-about: Report a technical issue
+about: Report a technical issue or unexpected behavior in the library
 title: "[BUG] "
 labels: bug
 ---
 
 ## Description
 
-Provide a concise description of the bug.
+Provide a clear and concise description of the bug.
 
-## Reproduction
+## Reproduction Steps
+
+Please describe the steps to reproduce the behavior:
 
 1. Step one
 2. Step two
-3. Observed behavior
+3. Observed behavior (e.g. error, hang, crash)
 
 ## Expected Behavior
 
-What should have happened.
+A clear and concise description of what you expected to happen.
 
-## Context
+## Environment Details
 
-- **OS**:
-- **Python Version**:
-- **Library Version**:
-- **Installation**: (e.g., pip, source)
+- **OS**: [e.g. Windows 11, Ubuntu 24.04, macOS Sequoia]
+- **Python Version**: [e.g. 3.11.2, 3.13.0]
+- **Library Version**: [e.g. 0.2.12]
+- **Installation Method**: [e.g. pip, maturin develop, source build]
 
 ## Evidence
 
 ### Code Sample
 
+Provide a minimal, self-contained, reproducible example code snippet that triggers the bug:
+
 ```python
-# Minimal reproducible example
+# Paste python code here
 ```
 
-### Error Logs
+### Traceback / Error Logs
+
+Provide the full error logs or console outputs:
 
 ```text
 # Paste error output here
 ```
 
-## Additional Information
+## Additional Context
+
+Add any other context about the problem here (e.g. SSID validity, network conditions, platform region).
+
+## AI Usage Disclosure
 
-Any other relevant technical details.
+- [ ] I used AI assistance to write or understand this issue.
+      If yes, please specify which tool(s) and what parts were AI-assisted:

.github/ISSUE_TEMPLATE/config.yml

@@ -1,14 +1,14 @@
 blank_issues_enabled: false
 contact_links:
-  - name: 💬 Discord Community
+  - name: Discord Community
     url: https://discord.gg/p7YyFqSmAz
     about: Join our Discord server for questions, discussions, and support
-  - name: 📚 Documentation
+  - name: Documentation
     url: https://chipadevteam.github.io/BinaryOptionsTools-v2/
     about: Read our comprehensive documentation
-  - name: 💡 Discussions
+  - name: Discussions
     url: https://github.com/ChipaDevTeam/BinaryOptionsTools-v2/discussions
     about: Community discussions for ideas and general topics
-  - name: 🔒 Security Issue
+  - name: Security Issue
     url: https://github.com/ChipaDevTeam/BinaryOptionsTools-v2/security/advisories/new
     about: Report security vulnerabilities privately

.github/ISSUE_TEMPLATE/documentation.md

@@ -1,22 +1,27 @@
 ---
 name: Documentation Issue
-about: Report missing or incorrect documentation
+about: Report missing, incorrect, or outdated documentation
 title: "[DOCS] "
 labels: documentation
 ---
 
 ## Description
 
-Identify the documentation issue.
+Identify the documentation issue, typo, or missing guide.
 
 ## Location
 
-Provide the file path or URL.
+Provide the file path, URL, or API method name where the documentation is located.
 
 ## Proposed Correction
 
-What should the documentation say instead?
+What should the documentation say instead? If you have a specific phrasing in mind, please include it.
 
 ## Additional Context
 
 Any other information relevant to this issue.
+
+## AI Usage Disclosure
+
+- [ ] I used AI assistance to write or understand this issue.
+      If yes, please specify which tool(s) and what parts were AI-assisted:

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,28 +1,35 @@
 ---
 name: Feature Request
-about: Propose a new feature or enhancement
+about: Propose a new feature, enhancement, or architectural improvement
 title: "[FEATURE] "
 labels: enhancement
 ---
 
-## Proposal
+## Description
 
-Clearly describe the proposed feature.
+Clearly and concisely describe the proposed feature or enhancement.
 
 ## Problem Statement
 
-What problem does this feature solve?
+What problem does this feature solve? Describe the pain point or limitation you are experiencing.
 
 ## Suggested Implementation
 
-Provide a high-level overview of how this could be implemented.
+Provide a high-level overview of how you think this feature could be implemented. If you have code design ideas, detail them here.
 
-## Use Case
+## Proposed API / Usage Example
+
+Provide a code snippet illustrating how this feature would be used by a developer:
 
 ```python
-# Example of how this feature would be used
+# Proposed usage snippet
 ```
 
 ## Benefits
 
-Why is this feature important for the project?
+Why is this feature important or beneficial for the project and its users?
+
+## AI Usage Disclosure
+
+- [ ] I used AI assistance to write or understand this issue.
+      If yes, please specify which tool(s) and what parts were AI-assisted:

.github/ISSUE_TEMPLATE/question.md

@@ -1,26 +1,25 @@
 ---
-name: Question
-about: Ask for technical assistance
+name: Question / Support
+about: Ask for assistance, usage guidance, or general technical support
 title: "[QUESTION] "
 labels: question
 ---
 
 ## Inquiry
 
-What is your technical question?
+State your technical question clearly and concisely.
 
-## Context
+## Attempted Solutions
 
-Provide details on what you are trying to achieve and what you have attempted.
+Describe what you are trying to achieve and what you have attempted so far. Include code samples if possible.
 
-## Environment
+## Environment Details
 
 - **OS**:
 - **Python Version**:
 - **Library Version**:
 
-## Resources Checked
+## AI Usage Disclosure
 
-- [ ] Documentation
-- [ ] Existing Examples
-- [ ] Previous Issues
+- [ ] I used AI assistance to write or understand this issue.
+      If yes, please specify which tool(s) and what parts were AI-assisted:

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,44 +1,46 @@
 # Pull Request
 
-## Overview
+## Description
 
-Summarize the changes and the motivation behind them. Link any related issues using keywords (e.g., Fixes #123).
+Provide a clear and concise description of the changes introduced by this PR. Detail the motivation, context, and any architectural or behavioral impacts of the change.
 
-## Changes
+## Related Issues
 
-- List key changes here.
-- Keep descriptions concise and technical.
+Fixes # (issue number)
+Closes # (issue number)
 
 ## Type of Change
 
-- [ ] Bug fix
-- [ ] New feature
-- [ ] Breaking change
-- [ ] Documentation / Examples
-- [ ] Performance / Refactoring
-- [ ] CI/CD / Build System
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation / Examples update
+- [ ] Performance improvement / Code refactoring
+- [ ] CI/CD / Build system configuration
 
-## Validation
+## Validation and Testing
 
-Describe how the changes were tested.
+Describe the tests performed to verify your changes. Provide instructions so others can reproduce. Please also list any relevant details for your testing configuration.
 
-- [ ] Unit tests
-- [ ] Integration tests
-- [ ] Manual verification
+- **Test Suite**: Run `cargo test` and `pytest` locally to verify changes.
+- **Evidence**: Paste test run outputs, benchmark results, or code snippets verifying the fix/feature here.
 
-### Environment
-
-- OS:
-- Python Version:
-- Rust Version:
+```bash
+# Example verification command used
+pytest tests/python/pocketoption/
+```
 
 ## Checklist
 
-- [ ] Code follows project conventions and style guidelines.
-- [ ] Documentation and examples updated if necessary.
-- [ ] All tests pass locally.
-- [ ] No new warnings introduced.
+- [ ] My code follows the project's coding style guidelines (Ruff for Python, `cargo fmt` for Rust).
+- [ ] I have performed a self-review of my own code.
+- [ ] I have commented my code, particularly in hard-to-understand areas.
+- [ ] I have made corresponding changes to the documentation.
+- [ ] My changes generate no new compiler or linter warnings.
+- [ ] I have added tests that prove my fix is effective or that my feature works.
+- [ ] New and existing unit/integration tests pass locally.
 
-## Screenshots (Optional)
+## AI Usage Disclosure
 
-Add relevant visuals if applicable.
+- [ ] I used AI assistance to write or understand this PR/issue.
+      If yes, please specify which tool(s) and what parts were AI-assisted:

.github/dependabot.yml

@@ -1,11 +1,30 @@
-# To get started with Dependabot version updates, you'll need to specify which
-# package ecosystems to update and where the package manifests are located.
-# Please see the documentation for all configuration options:
-# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
-
+# Dependabot configuration for automatically updating dependencies
 version: 2
 updates:
+  # Maintain Cargo dependencies for all Rust crates
   - package-ecosystem: "cargo"
     directory: "/"
     schedule:
       interval: "weekly"
+    groups:
+      rust-dependencies:
+        patterns:
+          - "*"
+
+  # Maintain GitHub Actions dependencies
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+  # Maintain Python dependencies in the bindings crate
+  - package-ecosystem: "pip"
+    directory: "/python"
+    schedule:
+      interval: "weekly"
+
+  # Maintain JavaScript dependencies in the workspace root (e.g. Husky, Prettier)
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"