Last version 2.8.38

.agent/README.md

@@ -0,0 +1,58 @@
+---
+trigger: always_on
+description: Overview of project governance, skills, and workflows
+category: governance
+---
+# .agent - Project Governance & Artificial Intelligence Intelligence
+
+This directory contains the project's technical constitution, specialized skills, and operational workflows used by AI agents.
+
+## Governance & Execution Constraints
+
+| File | Description |
+| :--- | :--- |
+| [`00_constitution.md`](./rules/00_constitution.md) | Core mission and unique source of truth for the project. |
+| [`01_objective.md`](./rules/01_objective.md) | Current project roadmap and success criteria. |
+| [`02_architecture.md`](./rules/02_architecture.md) | Immutable project architecture and technology stack. |
+| [`03_execution_rules.md`](./rules/03_execution_rules.md) | Core project constitution and hard execution constraints. |
+| [`04_best_practices.md`](./rules/04_best_practices.md) | Technical best practices and recommended internal patterns. |
+| [`05_memory_protocol.md`](./rules/05_memory_protocol.md) | Protocols for maintaining contextual consistency and history. |
+| [`remembers.md`](./rules/remembers.md) | "Persistent memory for emerging patterns and session-specific dynamic rules" |
+
+
+## Specialized Capabilities & Knowledge
+
+| File | Description |
+| :--- | :--- |
+| [`cli-execution-mastery/`](./skills/cli-execution-mastery/SKILL.md) | Mastery of MySQLTuner CLI options for connection and authentication. |
+| [`db-version-rift/`](./skills/db-version-rift/SKILL.md) | Mapping of critical differences between MySQL and MariaDB versions for cross-compatible diagnostics. |
+| [`legacy-perl-patterns/`](./skills/legacy-perl-patterns/SKILL.md) | Guidelines and patterns for maintaining backward compatibility with older Perl versions (5.8+). |
+| [`testing-orchestration/`](./skills/testing-orchestration/SKILL.md) | Knowledge on how to run, orchestrate, and validate tests in the MySQLTuner project. |
+
+
+## Automation & Operational Workflows
+
+| File | Description |
+| :--- | :--- |
+| [`compliance-sentinel.md`](./workflows/compliance-sentinel.md) | Automated audit to enforce project constitution rules |
+| [`doc-sync.md`](./workflows/doc-sync.md) | Synchronize .agent/README.md with current Rules, Skills, and Workflows |
+| [`docker-clean.md`](./workflows/docker-clean.md) | Reclaim disk space by removing unused containers and images |
+| [`examples-cleanup.md`](./workflows/examples-cleanup.md) | Maintain only the 10 most recent results in the examples directory |
+| [`git-flow.md`](./workflows/git-flow.md) | Automate git-flow release process |
+| [`git-rollback.md`](./workflows/git-rollback.md) | Rollback a failed release (delete tags and revert commits) |
+| [`hey-agent.md`](./workflows/hey-agent.md) | Unified management for Rules, Skills, and Workflows. |
+| [`lab-down.md`](./workflows/lab-down.md) | Stops and cleans up the database laboratory. |
+| [`lab-up.md`](./workflows/lab-up.md) | Starts a persistent database laboratory and injects data. |
+| [`markdown-lint.md`](./workflows/markdown-lint.md) | Check markdown content for cleanliness and project standard compliance (AFF, keywords, links) |
+| [`plan.md`](./workflows/plan.md) | Create or update an implementation plan (implementation_plan.md) |
+| [`release-manager.md`](./workflows/release-manager.md) | High-level release orchestrator for the Release Manager role |
+| [`release-notes-gen.md`](./workflows/release-notes-gen.md) | Generate detailed technical release notes for the current version |
+| [`release-preflight.md`](./workflows/release-preflight.md) | Pre-flight checks before triggering a git-flow release |
+| [`run-tests.md`](./workflows/run-tests.md) | Comprehensive test suite execution (Unit, Regression, and Multi-DB) |
+| [`snapshot-to-test.md`](./workflows/snapshot-to-test.md) | Transform a running production issue into a reproducible test case |
+| [`specify.md`](./workflows/specify.md) | Create or update a feature specification (specification.md) |
+| [`tasks.md`](./workflows/tasks.md) | Break down an approved plan into actionable tasks (task.md) |
+
+
+---
+*Generated automatically by `/doc-sync` on Sat Feb 14 11:35:52 CET 2026*

.agent/rules/00_constitution.md

@@ -1,14 +1,46 @@
 ---
 trigger: always_on
+description: Core mission and unique source of truth for the project.
+category: governance
 ---
 
 # **AI CONTEXT SPECIFICATIONS & PROJECT CONSTITUTION**
 
+## 🧠 Rationale
+
+Establishing an absolute source of truth is critical for maintaining consistency and quality in an agentic coding environment. This constitution ensures all interventions align with the project's high-level goals.
+
+## 🛠️ Implementation
+
 $$SYSTEM\_CRITICAL$$  
 Notice to the Agent: This document constitutes the unique and absolute source of truth for the project. Its prior consultation is imperative before any technical intervention.
 
-Make mysqltuner.pl the best performance tuning advisor
+**Core Mission:**
+Make `mysqltuner.pl` the most stable, portable, and reliable performance tuning advisor for MySQL, MariaDB, and Percona Server.
+
+**Key Pillars:**
+
+- **Production Stability**: Every recommendation must be safe for production environments. Zero tolerance for destructive or experimental "hacks" without explicit user opt-in.
+- **Single-File Architecture**: Strict enforcement of a single-file structure. Modules or splitting are prohibited to ensure maximum portability.
+- **Zero-Dependency Portability**: The script must remain self-contained and executable on any server with a base Perl installation (Core modules only).
+- **Universal Compatibility**: Support the widest possible range of MySQL-compatible versions (Legacy 5.5 to Modern 11.x).
+- **Regression Limit**: Proactively identify and prevent regressions through exhaustive automated testing.
+- **Actionable Insights**: Provide clear, verified, and well-documented tuning advice.
+- **Release Integrity**: Guarantee artifact consistency and multi-version validation through a formal Release Management protocol.
+
+## 🏗️ Governance Hierarchy (7-Tier AFF)
+
+This project follows a standardized governance structure:
+
+- **Tier 00**: [00_constitution.md](file:///.agent/rules/00_constitution.md) (Absolute Truth)
+- **Tier 01**: [01_objective.md](file:///.agent/rules/01_objective.md) (Identity & Mission)
+- **Tier 02**: [02_architecture.md](file:///.agent/rules/02_architecture.md) (Environment)
+- **Tier 03**: [03_execution_rules.md](file:///.agent/rules/03_execution_rules.md) (Constraints)
+- **Tier 04**: [04_best_practices.md](file:///.agent/rules/04_best_practices.md) (Implementation)
+- **Tier 05**: [05_memory_protocol.md](file:///.agent/rules/05_memory_protocol.md) (History)
+- **Dynamic**: [remembers.md](file:///.agent/rules/remembers.md) (Session Buffer)
+
+## ✅ Verification
 
-Large insights
-Good advices
-Well documented solution
+- All technical decisions must be cross-referenced with this document.
+- Use `/compliance-sentinel` to audit deviations.

.agent/rules/01_objective.md

@@ -1,23 +1,38 @@
-## **2\. 🎯 OPERATIONAL OBJECTIVE**
+---
+trigger: always_on
+description: Current project roadmap and success criteria.
+category: governance
+---
+
+# **2\. 🎯 OPERATIONAL OBJECTIVE**
+
+## 🧠 Rationale
+
+Dynamic context tracking allows the agent to maintain focus on current priorities and measure success against defined criteria.
+
+## 🛠️ Implementation
 
 $$DYNAMIC\_CONTEXT$$
 
 * **Status:** \[IN PROGRESS\]  
-* **Priority Task:** Maintain and enhance `mysqltuner.pl`, a Perl script for MySQL/MariaDB database performance tuning. Ensure single-file architecture and high reliability through automated testing.
+* **Priority Task:** Maintain and enhance `mysqltuner.pl` as a production-grade tuning advisor. Focus on regression testing and broad version compatibility for MySQL, MariaDB, and Percona Server.
 
 **Success Criteria:**
 
-1. **Architecture:** No splitting of the main file; all logic resides in `mysqltuner.pl`.
-2. **Quality:** 100% of new features validated through TDD.
-3. **Docs:** Keep `README.md` and translations updated with new features and requirements.
-4. **Automation:** All tests runnable via `make test-*` or specific test scripts.
-5. **Goal:** Provide the most accurate and up-to-date performance tuning recommendations for MySQL-compatible databases.
+1. **Architecture:** Strict single-file architecture. No external non-core Perl dependencies.
+2. **Quality (Zero Regression):** 100% of new features and fixes validated through TDD and regression suits (Legacy 8.0 to Modern 11.x).
+3. **Stability:** All recommendations must be traceable to official documentation and verified safe for production use.
+4. **Docs:** Maintain automated synchronization between `mysqltuner.pl` capabilities and `README.md` / translations.
+5. **Efficiency:** Optimized execution for large databases (minimal memory footprint and execution time).
 
 **Roadmap / Evolution Paths:**
 
-1. **Schema Validation for Rules**: Créer un script de linting pour valider que les fichiers `.agent/rules/*.md` respectent un format standard.
-2. **Source Code Annotation**: Automatiser l'ajout des tags de version directement dans les commentaires des fonctions modifiées.
-3. **Automated Doc-Link Check**: Ajouter un test qui vérifie que les liens de documentation insérés dans les commentaires du code (`# See: http://...`) sont toujours valides.
-4. **Pre-commit Hook**: Implementer un hook Git local qui lance le pre-flight check de `/git-flow`.
-5. **Automated Roadmap Tracking**: Créer un script qui extrait les points de la roadmap pour générer un rapport de progression.
-6. **Perl Tidy Integration**: Ajouter une règle exigeant l'utilisation de `perltidy` avec une configuration spécifique pour garantir la lisibilité du fichier unique.
+1. **CI/CD Regression Suite**: Automate testing across 10+ major DB versions (MySQL 5.6-8.4, MariaDB 10.3-11.8).
+2. **Automated Documentation Sync**: Ensure `INTERNALS.md` and `README.md` are always in sync with internal indicator count.
+3. **Advanced Container Support**: Refine detection and tuning recommendations for Docker/K8s/Cloud environments.
+4. **Enhanced Security Auditing**: Improve detection of common security misconfigurations and weak credentials.
+
+## ✅ Verification
+
+* Review [task.md](file:///brain/2fa184f4-13e1-4c64-bf13-57b4addd2797/task.md) for current status.
+* Periodic roadmap reviews during `/release-preflight`.

.agent/rules/02_architecture.md

@@ -1,12 +1,18 @@
 ---
 trigger: always_on
+description: Immutable project architecture and technology stack.
+category: governance
 ---
+# **3\. 🏗️ TECHNICAL ENVIRONMENT & ARCHITECTURE**
 
-## **3\. 🏗️ TECHNICAL ENVIRONMENT & ARCHITECTURE**
+## 🧠 Rationale
+
+Preserving the single-file architecture of `mysqltuner.pl` is a core technical constraint that ensures maximum portability and ease of deployment.
+
+## 🛠️ Implementation
 
 $$IMMUTABLE$$  
 Component Map:  
-Modification prohibited without explicit request.  
 
 | File/Folder | Functionality | Criticality |
 | :--- | :--- | :--- |
@@ -19,7 +25,12 @@ Modification prohibited without explicit request.
 
 **Technology Stack:**
 
-* **Language:** Perl (Core script)
-* **Testing:** Perl (prove, Test::More)
-* **Automation:** Makefile, Bash, Docker, Python, Per
-* **DBMS Compatibility:** MySQL, MariaDB, Percona, AWS, AWS Aurora, Docker, GCP, Azure
+- **Language:** Perl (Core script)
+- **Testing:** Perl (prove, Test::More)
+- **Automation:** Makefile, Bash, Docker, Python
+- **DBMS Compatibility:** MySQL, MariaDB, Percona, AWS, AWS Aurora, GCP, Azure
+
+## ✅ Verification
+
+- `/compliance-sentinel` must fail if `mysqltuner.pl` is split or if non-core dependencies are added.
+- All builds must pass via `make docker_build`.