feat: release 2.8.41 final polish

- fix: include tmp_table_size in per-thread memory calculation (major#864)
- fix: add retry for initial connection check (major#782)
- fix: improve check_removed_innodb_variables accuracy (#32)
- fix: correctly handle --defaults-file without dropping options (major#605)
- fix: restore Debian maintenance account automatic login (major#896)
- chore: automated project maintenance and cleanup
- ci: migrate maintenance script to GitHub Actions
- test: update unit tests for all fixes (267 tests passed)

Author: jmrenouard

.agent/rules/05_memory_protocol.md

@@ -0,0 +1,41 @@
+name: Project Maintenance
+
+on:
+  push:
+    branches: [ master, main ]
+  workflow_dispatch:
+
+jobs:
+  update-metadata:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Install Dependencies
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y libpod-markdown-perl libtemplate-perl perltidy dos2unix
+
+      - name: Generate USAGE.md
+        run: pod2markdown mysqltuner.pl > USAGE.md
+
+      - name: Tidy mysqltuner.pl
+        run: perltidy -b mysqltuner.pl
+
+      - name: Update CVE List
+        run: perl build/updateCVElist.pl
+
+      - name: Normalize line endings
+        run: dos2unix mysqltuner.pl
+
+      - name: Generate FEATURES.md
+        run: bash build/genFeatures.sh
+
+      - name: Commit and Push changes
+        run: |
+          git config --local user.email "action@github.com"
+          git config --local user.name "GitHub Action"
+          git add vulnerabilities.csv mysqltuner.pl USAGE.md FEATURES.md
+          git diff --staged --quiet || (git commit -m "chore: automated project metadata update" && git push)

.agent/rules/remembers.md

@@ -13,6 +13,13 @@
 - refactor: replace "master"/"slave" terminology with "source"/"replica" for cultural sensitivity (#888).
 - fix: improve join_buffer_size recommendation formatting in Variables to Adjust (#881).
 - fix: suppress MySQL client warning regarding 'DISABLED' boolean value for SSL (#887).
+- fix: correctly handle `--defaults-file` and `--defaults-extra-file` without dropping options (#605).
+- fix: restore Debian maintenance account automatic login by using idiomatic boolean checks (#896).
+- fix: include `tmp_table_size` in per-thread memory calculation for better accuracy (#864).
+- fix: add retry mechanism for initial `SELECT VERSION()` query to improve connection resilience (#782).
+- fix: prevent `AUTO_INCREMENT` capacity false positives for empty tables (#37).
+- chore: automated project maintenance and cleanup (extracted `RULES.md`, `MEMORY_DB.md`, `TESTS.md`).
+- ci: migrate maintenance script to GitHub Actions.
 - chore(deps): update docker/setup-buildx-action action to v4.
 - chore(deps): update docker/build-push-action action to v7.
 - chore(deps): update docker/login-action action to v4.

.github/workflows/project-update.yml

@@ -0,0 +1,70 @@
+For project-specific context, please refer to:
+- [RULES.md](file:///home/jmren/GIT_REPOS/MySQLTuner-perl/RULES.md): Core constitution, execution rules, and best practices.
+- [MEMORY_DB.md](file:///home/jmren/GIT_REPOS/MySQLTuner-perl/MEMORY_DB.md): Project evolution, version history, and systemic findings.
+- [TESTS.md](file:///home/jmren/GIT_REPOS/MySQLTuner-perl/TESTS.md): Comprehensive guide on unit and laboratory testing.
+
+---
+
+Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.
+
+**Tradeoff:** These guidelines bias toward caution over speed. For trivial tasks, use judgment.
+
+## 1. Think Before Coding
+
+**Don't assume. Don't hide confusion. Surface tradeoffs.**
+
+Before implementing:
+- State your assumptions explicitly. If uncertain, ask.
+- If multiple interpretations exist, present them - don't pick silently.
+- If a simpler approach exists, say so. Push back when warranted.
+- If something is unclear, stop. Name what's confusing. Ask.
+
+## 2. Simplicity First
+
+**Minimum code that solves the problem. Nothing speculative.**
+
+- No features beyond what was asked.
+- No abstractions for single-use code.
+- No "flexibility" or "configurability" that wasn't requested.
+- No error handling for impossible scenarios.
+- If you write 200 lines and it could be 50, rewrite it.
+
+Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
+
+## 3. Surgical Changes
+
+**Touch only what you must. Clean up only your own mess.**
+
+When editing existing code:
+- Don't "improve" adjacent code, comments, or formatting.
+- Don't refactor things that aren't broken.
+- Match existing style, even if you'd do it differently.
+- If you notice unrelated dead code, mention it - don't delete it.
+
+When your changes create orphans:
+- Remove imports/variables/functions that YOUR changes made unused.
+- Don't remove pre-existing dead code unless asked.
+
+The test: Every changed line should trace directly to the user's request.
+
+## 4. Goal-Driven Execution
+
+**Define success criteria. Loop until verified.**
+
+Transform tasks into verifiable goals:
+- "Add validation" → "Write tests for invalid inputs, then make them pass"
+- "Fix the bug" → "Write a test that reproduces it, then make it pass"
+- "Refactor X" → "Ensure tests pass before and after"
+
+For multi-step tasks, state a brief plan:
+```
+1. [Step] → verify: [check]
+2. [Step] → verify: [check]
+3. [Step] → verify: [check]
+```
+
+Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.
+
+---
+
+**These guidelines are working if:** fewer unnecessary changes in diffs, fewer rewrites due to overcomplication, and clarifying questions come before implementation rather than after mistakes.

Changelog

@@ -0,0 +1,31 @@
+# MySQLTuner-perl Version Memory
+
+## Current Version: 2.8.41
+
+## Project Evolution & Systemic Findings
+
+### System Call & Core Perl Optimization (v2.8.35+)
+Migrated several external commands to native Core Perl to reduce fork overhead and improve portability:
+- `whoami` -> `(getpwuid($<))[0]`
+- `env` / `printenv` -> `%ENV` hash access
+- `hostname` -> `Sys::Hostname::hostname()`
+- `grep ... /proc/meminfo` -> Native file parsing
+- `grep -c ^processor /proc/cpuinfo` -> Native file parsing
+- `which` -> Native PATH iteration
+- `getconf PAGESIZE` -> `POSIX::sysconf(POSIX::_SC_PAGESIZE)`
+- `uname` -> `POSIX::uname()` or `$^O`
+- `stty` -> `POSIX::Termios`
+- `uptime` -> `/proc/uptime` parsing or `$^T` calculation
+
+### Recent Audits
+- **v2.8.41**: 
+  - Completed project-wide refactoring to use standard Perl Boolean practices.
+  - Restored Debian maintenance account automatic login functionality (#896).
+  - Improved memory calculation accuracy by including `tmp_table_size` in per-thread buffers (#864).
+  - Added retry mechanism for initial server connection checks to improve resilience (#782).
+  - Resolved `AUTO_INCREMENT` capacity false positives for empty tables (#37).
+  - Corrected `check_removed_innodb_variables` false positives for injected variables (#32).
+  - Fixed `--defaults-file` usage to prevent dropping other connection options (#605).
+- **v2.8.40**: Enhanced SSL/TLS security checks and cloud discovery (AWS RDS/Aurora, GCP, Azure).
+- **v2.8.38**: Fixed container startup failures in lab environments.
+- **v2.8.31**: Improved SQL check syntax for redundant index detection.

GEMINI.md

@@ -59,9 +59,10 @@ To ensure consistency and high-density development, the following roles are defi
   * [x] Unified KPI (0-100) aggregating findings from Security, Performance, and Resilience.
   * [ ] Comparative scoring against previous runs or established industry baselines.
 * [/] **Predictive Capacity Planning**:
-  * [ ] Data growth forecasting based on binlog throughput and table statistics.
+  * [x] Data growth forecasting based on binlog throughput and table statistics.
   * [x] Memory headroom analysis for traffic peak forecasting.
-* [/] **Cluster & Replication Intelligence**:
+  * [x] AUTO_INCREMENT capacity near max value detection.
+* [x] **Cluster & Replication Intelligence**:
   * [x] Root cause analysis for replication lag (IO/SQL thread contention).
   * [ ] GTID consistency checks and multi-source replication tuning.
 * [/] **Security Hardening 2.0**:

MEMORY_DB.md

@@ -0,0 +1,29 @@
+# MySQLTuner-perl Project Rules
+
+## Core Constitution
+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.
+- **Single-File Architecture**: Strict enforcement of a single-file structure. Modules or splitting are prohibited.
+- **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.
+
+## Execution Rules & Constraints
+1. **SINGLE FILE**: Spliting `mysqltuner.pl` into modules is **strictly prohibited**.
+2. **NON-REGRESSION**: Deleting existing code is **prohibited** without relocation or commenting out.
+3. **TDD MANDATORY**: Use a TDD approach. Validate solutions by creating test cases before final submission.
+4. **SAFE COMMANDS**: Always use absolute paths. Monitor every command for `exit code 0`.
+5. **CREDENTIAL HYGIENE**: NEVER hardcode credentials.
+6. **VERSION CONSISTENCY**: Version numbers MUST be synchronized across `CURRENT_VERSION.txt`, `Changelog`, and all occurrences within `mysqltuner.pl`.
+7. **CONVENTIONAL COMMITS**: All commit messages MUST follow the [Conventional Commits](https://www.conventionalcommits.org/) specification.
+8. **NO DIRECT COMMIT**: All changes SHOULD be committed via `npm run commit` or `git cz`.
+
+## Best Practices
+1. **Multi-Version Validation**: Test diagnostic logic changes against at least one "Legacy" version (e.g. MySQL 8.0) and one "Modern" version (e.g. MariaDB 11.4).
+2. **System Call Resilience**: Every external command MUST check for binary existence and handle non-zero exit codes. Use `execute_system_command`.
+3. **"Zero-Dependency" CPAN Policy**: Use ONLY Perl "Core" modules.
+4. **Audit Trail**: Every recommendation MUST be documented in code with a comment pointing to official documentation.
+5. **Memory-Efficient Parsing**: Process logs line-by-line; NEVER load large files into memory.
+6. **SQL Modeling**: Use the `Modeling` array to collect schema design findings (naming, constraints, data types).

ROADMAP.md

@@ -0,0 +1,43 @@
+# MySQLTuner-perl Testing Guide
+
+## Unit and Regression Tests
+The project uses `Test::More` for unit testing. All tests are located in the `tests/` directory.
+
+### Running Unit Tests
+```bash
+make unit-tests
+# OR
+prove -r tests/
+```
+
+## Laboratory Tests (Docker)
+The laboratory environment allows testing `mysqltuner.pl` against multiple database versions.
+
+### Setup Vendor Repositories
+```bash
+make vendor_setup
+```
+
+### Running Lab Tests
+```bash
+# Run tests against default environments (mysql84, mariadb1011, percona80)
+make test
+
+# Run all database lab tests
+make test-all
+
+# Run tests against a specific container
+make test-container CONTAINER=my_db_name
+```
+
+### Lab Audit
+After running tests, you can audit the generated logs:
+```bash
+make audit-logs
+```
+
+## Test Scenarios
+Every diagnostic change should ideally be validated in three scenarios:
+1. **Standard**: `./mysqltuner.pl --verbose`
+2. **Container**: `./mysqltuner.pl --verbose --container [ID]`
+3. **Dumpdir**: `./mysqltuner.pl --verbose --dumpdir=dumps`