Release v1.15.0 (#55)

* feat(cli): add vix check, vix tests, and vix verify

- Add new CLI commands: check, tests, and verify
- Improve CLI help output and documentation
- Add CLI reference documentation
- Add contributing, code of conduct, and PR template
- Update security testing documentation

* chore(release): prepare v1.15.0

* chore(release): add PR-safe release Makefile and update gitignore

* chore(release): fix release Makefile parsing and PR workflow

Author: GaspardKirira

.gitignore

@@ -71,4 +71,5 @@ cmake/*
 db.sql
 revoir.md
 main.cpp
-.vix-scripts
+.vix-scripts
+Makefile

CHANGELOG.md

@@ -8,7 +8,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ---
 
 ## [Unreleased]
-## [1.14.7] - 2025-12-19
+## [1.15.0] - 2025-12-20
 
 ### Added
 - 
@@ -20,6 +20,46 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - 
 
 
+## v1.15.0 — 2025-12-20
+
+### Added
+
+- **`vix check`**: validate a project or compile a single `.cpp` file without execution.
+- **`vix tests`**: run project tests (alias of `vix check --tests`).
+- **`vix verify`**: verify packaged artifacts and signatures.
+- CLI reference documentation (`docs/vix-cli-help.md`).
+- Pull Request template to standardize contributions.
+
+### Changed
+
+- Improved global CLI help output formatting and readability.
+- Updated README with clearer CLI usage and script mode examples.
+- Updated security testing documentation with realistic, tool-based practices.
+- Improved contributing guidelines and code of conduct.
+
+### Removed
+
+- Deprecated `SECURITY.md` in favor of a more accurate security testing guide.
+
+### Notes
+
+- This release significantly improves **CLI usability**, **testing workflow**, and **project governance**.
+- Recommended upgrade for all users relying on the Vix CLI.
+
+## [1.14.7] - 2025-12-19
+
+### Added
+
+-
+
+### Changed
+
+-
+
+### Removed
+
+-
+
 ## v1.14.7 — CLI Packaging Stability Update
 
 ### Fixed

CMakeLists.txt

@@ -13,7 +13,7 @@ cmake_minimum_required(VERSION 3.20)
 #   cmake --build build -j
 # ====================================================================
 
-project(vix VERSION 1.14.0 LANGUAGES CXX)
+project(vix VERSION 1.15.0 LANGUAGES CXX)
 
 # Make find_package honor *_ROOT hints (e.g. MYSQLCPPCONN_ROOT)
 if (POLICY CMP0144)

CODE_OF_CONDUCT.md

@@ -1,107 +1,119 @@
-# 🌍 Vix.cpp Code of Conduct
+# Vix.cpp Code of Conduct
 
-## 🧭 Our Commitment
+## Our Commitment
 
-We are committed to building a welcoming, collaborative, and respectful community around **Vix.cpp** —  
-a place where developers from all backgrounds can learn, build, and innovate together.
+We are committed to fostering a welcoming, inclusive, and professional community around **Vix.cpp**.
 
-We pledge to make participation in this project and community a harassment-free experience for everyone,  
-regardless of:
+We want this project to be a place where developers from all backgrounds can collaborate, learn, and build high-quality software together, free from harassment or discrimination.
 
-- age, body size, disability, ethnicity, gender identity and expression,
-- level of experience, education, nationality, personal appearance, race,
-- religion, sexual identity and orientation.
+We pledge to make participation in this project a harassment-free experience for everyone, regardless of:
+
+- age, body size, disability, ethnicity, nationality
+- gender identity or expression
+- level of experience or education
+- personal appearance
+- race, religion, sexual identity, or orientation
 
 ---
 
-## 🤝 Our Standards
+## Our Standards
+
+### Expected Behavior
 
-### Examples of behavior that contribute to a positive environment:
+Contributors are expected to:
 
-- Being respectful and constructive in all interactions.
-- Providing helpful feedback without personal attacks.
-- Welcoming new members and supporting beginners.
-- Focusing on what is best for the community and the project.
-- Giving credit where it is due and recognizing contributions.
+- Be respectful, professional, and constructive in all interactions
+- Provide feedback focused on ideas and code, not individuals
+- Welcome newcomers and support less experienced contributors
+- Respect differing viewpoints and experiences
+- Give proper credit for others’ work and ideas
+- Act in the best interest of the project and its community
 
-### Examples of unacceptable behavior:
+### Unacceptable Behavior
 
-- Use of sexualized language or imagery, or unwelcome advances.
-- Trolling, insulting or derogatory comments.
-- Public or private harassment of any kind.
-- Publishing others’ private information (addresses, emails, etc.) without explicit permission.
-- Any behavior that would reasonably be considered inappropriate in a professional setting.
+The following behaviors are not tolerated:
+
+- Sexualized language, imagery, or unwelcome advances
+- Trolling, insulting, or derogatory comments
+- Harassment, intimidation, or threats (public or private)
+- Publishing private information about others without explicit permission
+- Any conduct that would reasonably be considered inappropriate in a professional environment
 
 ---
 
-## 🛠 Enforcement Responsibilities
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing this Code of Conduct.
 
-Project maintainers are responsible for clarifying and enforcing our standards.  
-They may remove, edit, or reject contributions that violate this Code of Conduct.
+They may remove, edit, or reject comments, commits, issues, pull requests, or other contributions that violate these standards.
 
-They have the right and responsibility to temporarily or permanently ban any contributor  
-for behavior they deem inappropriate, threatening, or harmful.
+Maintainers may also temporarily or permanently ban contributors whose behavior they deem harmful, abusive, or disruptive.
 
 ---
 
-## 🧾 Scope
+## Scope
 
-This Code of Conduct applies both within project spaces (GitHub issues, discussions, pull requests)  
-and in public spaces when an individual is representing the project or its community.
+This Code of Conduct applies within all project spaces, including but not limited to:
 
-Examples include:
+- GitHub issues, pull requests, discussions, and code reviews
+- Official communication channels related to Vix.cpp
 
-- Using the official project email or social media accounts.
-- Acting as an official representative at an event or conference.
+It also applies when an individual is representing the project in public spaces, such as:
+
+- Using official project communication channels
+- Representing Vix.cpp at events, conferences, or online discussions
 
 ---
 
-## ⚖️ Enforcement
+## Enforcement
 
-If you experience or witness unacceptable behavior, please report it as soon as possible by emailing:
+If you experience or witness behavior that violates this Code of Conduct, please report it by contacting:
 
-📧 **vixcpp.framework@gmail.com**
+**Email:** gaspardkirira@outlook.com
 
-All complaints will be reviewed and investigated promptly and fairly.  
-All maintainers are obligated to respect the privacy and safety of reporters.
+All reports will be reviewed promptly and handled with discretion.  
+Project maintainers are committed to respecting the privacy and safety of everyone involved.
 
 ---
 
-## ⚙️ Enforcement Guidelines
+## Enforcement Guidelines
 
-Project maintainers will follow these guidelines when determining consequences for any action they deem in violation of this Code of Conduct.
+When determining appropriate consequences, maintainers will consider the context, severity, and history of the behavior.
 
 ### 1. Correction
 
-**Impact:** Use of inappropriate language or other unprofessional conduct.  
-**Consequence:** Private, written warning and clarification of expected behavior.
+**Impact:** Minor unprofessional or inappropriate behavior.  
+**Consequence:** Private clarification and guidance on expected conduct.
 
 ### 2. Warning
 
-**Impact:** A single incident or series of small violations.  
-**Consequence:** Warning and temporary exclusion from some interactions.
+**Impact:** Repeated minor violations or a single significant incident.  
+**Consequence:** Formal warning and possible temporary limitations on participation.
 
 ### 3. Temporary Ban
 
-**Impact:** Repeated or severe violations.  
-**Consequence:** Temporary ban from participation in discussions, issues, or contributions.
+**Impact:** Serious or repeated violations of community standards.  
+**Consequence:** Temporary suspension from participation in project spaces.
 
 ### 4. Permanent Ban
 
-**Impact:** Long-term pattern of harmful behavior.  
-**Consequence:** Permanent removal from all community channels.
+**Impact:** Sustained pattern of abusive, hostile, or harmful behavior.  
+**Consequence:** Permanent removal from all project-related spaces.
 
 ---
 
-## ❤️ Attribution
+## Attribution
+
+This Code of Conduct is adapted from the  
+[Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).
 
-This Code of Conduct is adapted from the [Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).  
-For answers to common questions, see the FAQ at:  
-👉 https://www.contributor-covenant.org/faq
+For additional information, see:  
+https://www.contributor-covenant.org/faq
 
 ---
 
-### 💡 Summary
+## Summary
+
+All contributors are expected to act with professionalism, respect, and integrity.
 
-> **Be kind. Be professional. Be helpful.**  
-> We are all here to make **Vix.cpp** — and the C++ ecosystem — better for everyone.
+By participating in **Vix.cpp**, you help build not only high-performance software, but also a healthy and collaborative community.