diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml new file mode 100644 index 0000000..81e3347 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -0,0 +1,68 @@ +name: Bug report +description: Report a bug to help us improve vromvrom-engine +title: "[Bug]: " +labels: ["bug"] +body: + - type: markdown + attributes: + value: | + Thanks for taking the time to fill out this bug report! Please check that the issue is not already reported before submitting. + - type: input + id: version + attributes: + label: Version / commit + description: Which version or commit are you running? (e.g. `git describe --tags`, or the commit hash from `git log -1`) + placeholder: "e.g. v0.4.2 / 1a2b3c4" + validations: + required: true + - type: dropdown + id: platform + attributes: + label: Platform + description: Where are you running the engine? + options: + - Windows + - Linux + - macOS + - Docker + - Other + validations: + required: true + - type: textarea + id: steps + attributes: + label: Steps to reproduce + description: Minimal, step-by-step instructions to trigger the bug. + placeholder: | + 1. Start the engine with '...' + 2. Send the request '...' + 3. Observe the error + validations: + required: true + - type: textarea + id: logs + attributes: + label: Log output + description: Paste the relevant log extract (redact any API keys, tokens and passwords). + placeholder: "Full error traceback, including the exception message." + render: shell + validations: + required: true + - type: textarea + id: expected + attributes: + label: Expected behavior + description: What did you expect to happen instead? + validations: + required: true + - type: textarea + id: config + attributes: + label: Configuration + description: Relevant part of `config.json` / `.env` — **without any API keys or tokens** (see CONTRIBUTING.md). + render: shell + - type: textarea + id: additional + attributes: + label: Additional context + description: Anything else that might help — screenshots, related issues, hardware details... diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml new file mode 100644 index 0000000..dfedfad --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -0,0 +1,34 @@ +name: Feature request +description: Suggest an idea for vromvrom-engine +title: "[Feature]: " +labels: ["enhancement"] +body: + - type: markdown + attributes: + value: | + Thanks for suggesting a feature! Please check that a similar request does not already exist before submitting. + - type: textarea + id: problem + attributes: + label: Problem / motivation + description: What problem does this feature solve? What is the use case? + placeholder: "e.g. I would like to route tasks to provider X, but ..." + validations: + required: true + - type: textarea + id: proposal + attributes: + label: Proposed solution + description: How should the feature work? Be as concrete as possible. + validations: + required: true + - type: textarea + id: alternatives + attributes: + label: Alternatives considered + description: Any workaround or alternative approach you have tried or considered. + - type: textarea + id: additional + attributes: + label: Additional context + description: Anything else that might help — links, references, mockups... diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..101426a --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,132 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in our +community a harassment-free experience for everyone, regardless of age, body +size, visible or invisible disability, ethnicity, sex characteristics, gender +identity and expression, level of experience, education, socio-economic status, +nationality, personal appearance, race, religion, or sexual identity +and orientation. + +We pledge to act and interact in ways that contribute to an open, welcoming, +diverse, inclusive, and healthy community. + +## Our Standards + +Examples of behavior that contributes to a positive environment for our +community include: + +* Demonstrating empathy and kindness toward other people +* Being respectful of differing opinions, viewpoints, and experiences +* Giving and gracefully accepting constructive feedback +* Accepting responsibility and apologizing to those affected by our mistakes, + and learning from the experience +* Focusing on what is best not just for us as individuals, but for the + overall community + +Examples of unacceptable behavior include: + +* The use of sexualized language or imagery, and sexual attention or + advances of any kind +* Trolling, insulting or derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or email + address, without their explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Enforcement Responsibilities + +Community leaders are responsible for clarifying and enforcing our standards of +acceptable behavior and will take appropriate and fair corrective action in +response to any behavior that they deem inappropriate, threatening, offensive, +or harmful. + +Community leaders 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, and will communicate reasons for moderation +decisions when appropriate. + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when +an individual is officially representing the community in public spaces. +Examples of representing our community include using an official e-mail address, +posting via an official social media account, or acting as an appointed +representative at an online or offline event. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported to the community leaders responsible for enforcement at +[INSERT EMAIL ADDRESS]. +All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the +reporter of any incident. + +## Enforcement Guidelines + +Community leaders will follow these Community Impact Guidelines in determining +consequences for any action they deem in violation of this Code of Conduct: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behavior deemed +unprofessional or unwelcome in the community. + +**Consequence**: A private, written warning from community leaders, providing +clarity around the nature of the violation and an explanation of why the +behavior was inappropriate. A public apology may be requested. + +### 2. Warning + +**Community Impact**: A violation through a single incident or series of +actions. + +**Consequence**: A warning with consequences for continued behavior. No +interaction with the people involved, including unsolicited interaction with +those enforcing the Code of Conduct, for a specified period of time. This +includes avoiding interactions in community spaces as well as external channels +like social media. Violating these terms may lead to a temporary or permanent +ban. + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including +sustained inappropriate behavior. + +**Consequence**: A temporary ban from any sort of interaction or public +communication with the community for a specified period of time. No public or +private interaction with the people involved, including unsolicited interaction +with those enforcing the Code of Conduct, is allowed during this period. +Violating these terms may lead to a permanent ban. + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community +standards, including sustained inappropriate behavior, harassment of an +individual, or aggression toward or disparagement of classes of individuals. + +**Consequence**: A permanent ban from any sort of public interaction within +the community. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 2.1, available at +[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. + +Community Impact Guidelines were inspired by +[Mozilla's code of conduct enforcement ladder][Mozilla CoC]. + +For answers to common questions about this code of conduct, see the FAQ at +[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at +[https://www.contributor-covenant.org/translations][translations]. + +[homepage]: https://www.contributor-covenant.org +[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html +[Mozilla CoC]: https://github.com/mozilla/diversity +[FAQ]: https://www.contributor-covenant.org/faq +[translations]: https://www.contributor-covenant.org/translations diff --git a/README.md b/README.md index 00309e8..9c5b430 100644 --- a/README.md +++ b/README.md @@ -9,8 +9,11 @@ [![Python](https://img.shields.io/badge/Python-3.11%2B-blue?logo=python)](https://python.org) [![FastAPI](https://img.shields.io/badge/FastAPI-0.136%2B-009688?logo=fastapi)](https://fastapi.tiangolo.com) [![asyncio](https://img.shields.io/badge/asyncio-native-green)](https://docs.python.org/3/library/asyncio.html) -[![License](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE) +[![License](https://img.shields.io/github/license/Axellum/vromvrom-engine)](LICENSE) [![Tests](https://img.shields.io/badge/Tests-60%20pytest%20files-brightgreen)](tests/) +[![CI](https://github.com/Axellum/vromvrom-engine/actions/workflows/ci.yml/badge.svg)](https://github.com/Axellum/vromvrom-engine/actions/workflows/ci.yml) +[![Python CI & Security](https://github.com/Axellum/vromvrom-engine/actions/workflows/python-tests.yml/badge.svg)](https://github.com/Axellum/vromvrom-engine/actions/workflows/python-tests.yml) +[![ToolMaker Validate](https://github.com/Axellum/vromvrom-engine/actions/workflows/toolmaker_validate.yml/badge.svg)](https://github.com/Axellum/vromvrom-engine/actions/workflows/toolmaker_validate.yml) *Built for Home Assistant · Works with any project* diff --git a/requirements.txt b/requirements.txt index a238588..74f4e91 100644 --- a/requirements.txt +++ b/requirements.txt @@ -21,7 +21,7 @@ aiohttp>=3.14.1 aiosqlite>=0.22.1 # accès SQLite async (DAG runner) # ── MCP (serveurs Tab5-Engine, Workspace) ── -mcp>=1.27.0 +mcp>=1.27.0,<2.0.0 # borne haute : mcp 2.x a retiré mcp.server.fastmcp # ── Mémoire vectorielle / RAG ── chromadb>=1.5.0