V2.9.0

.agent/README.md

@@ -36,6 +36,7 @@ This directory contains the project's technical constitution, specialized skills
 | [`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. |
+| [`local-dev-sync.md`](./workflows/local-dev-sync.md) | Synchronize developer changes, run unit tests, and update changelog and release notes. |
 | [`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 |
@@ -48,4 +49,4 @@ This directory contains the project's technical constitution, specialized skills
 
 
 ---
-*Generated automatically by `/doc-sync` on 2026-06-12 20:03:20*
+*Generated automatically by `/doc-sync`*

.agent/rules/03_execution_rules.md

@@ -76,11 +76,10 @@ To ensure quality and clarity in every development cycle, all non-trivial featur
 - **Commit Validation:** Commits are automatically linted via `commitlint`. Non-compliant messages will be rejected by the pre-commit hook.
 - **History Documentation:** Use `npm run commit` to generate structured history.
 
-1. **Changelog:** All changes MUST be traced and documented inside `@Changelog`.
-    - _Exception_: Documentation-only updates (`docs:`) following Conventional Commits may skip the manual `@Changelog` entry if they are primarily intended for README synchronization.
-    - _Requirement_: Adding a new test MUST have a `test:` entry in the `@Changelog`.
-    - _Requirement_: Changing test scripts or updating infrastructure MUST have a `ci:` entry in the `@Changelog`.
-    - _Requirement_: Changing `Makefile` or files under `build/` MUST be traced in the `@Changelog` (usually via `ci:` or `chore:`).
+1. **Changelog:** All changes, without exception (including documentation `docs:` and unit tests `test:`), MUST be traced and documented inside the `Changelog` file to ensure granular change tracking.
+    - _Requirement_: Adding a new test MUST have a `test:` entry in the `Changelog`.
+    - _Requirement_: Changing test scripts or updating infrastructure MUST have a `ci:` entry in the `Changelog`.
+    - _Requirement_: Changing `Makefile` or files under `build/` MUST be traced in the `Changelog` (usually via `ci:` or `chore:`).
     - _Requirement_: All feature completions MUST be synchronized with `ROADMAP.md` before final PR/Commit.
     - _Ordering_: Changelog entries MUST be ordered by category: `chore`, `feat`, `fix`, `test`, `ci`, then others.
     - _Release Notes_: All release notes generated in `releases/` MUST follow the same category ordering in their "Executive Summary" section.

.agent/workflows/doc-sync.md

@@ -10,7 +10,7 @@ category: Documentation
 // turbo
 
 ```bash
-python3 build/doc_sync.py
+perl build/doc_sync.pl
 ```
 
 1. **Full Documentation Review Checklist**:

.agent/workflows/local-dev-sync.md

@@ -0,0 +1,32 @@
+---
+trigger: explicit_call
+description: Synchronize developer changes, run unit tests, and update changelog and release notes.
+category: tool
+---
+
+# Local Developer Sync Workflow
+
+This workflow provides local synchronization automation for the developer, ensuring version consistency, automatic changelog sorting, release notes updating, unit testing, and git delivery.
+
+## 🧠 Rationale
+
+Ensuring a clean and synchronized branch history, accurate release documentation, and fully passing unit tests before any push to the remote repository.
+
+## 🛠️ Implementation
+
+Run the local dev-sync orchestrator script:
+
+// turbo
+
+```bash
+perl build/dev_sync.pl
+```
+
+## ✅ Verification
+
+- The script returns exit code 0.
+- All version files are confirmed to be consistent.
+- `Changelog` is updated and sorted according to the Conventional Commit categories.
+- `releases/v[VERSION].md` matches the latest entries.
+- All local unit tests passed successfully.
+- Modified release files are committed and pushed to `origin`.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,43 @@
+---
+name: Bug report
+about: Create a report to help us improve MySQLTuner
+title: '[BUG] '
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**Execution Command**
+Please provide the exact command used to run MySQLTuner:
+```bash
+perl mysqltuner.pl [your arguments here]
+```
+
+**Environment info:**
+- MySQLTuner version: (e.g. 2.9.0)
+- Database Server: (e.g. MySQL, MariaDB, Percona Server)
+- Database Version: (e.g. 8.0.35, 10.6.15)
+- Operating System & Version: (e.g. Rocky Linux 9, Ubuntu 22.04)
+- Perl version: (e.g. v5.32.1)
+
+**MySQLTuner Debug Output**
+Please run MySQLTuner with the `--debug` option and paste the output here.
+> ⚠️ **IMPORTANT:** Obfuscate/remove any sensitive database credentials, IP addresses, hostnames, or passwords before pasting.
+
+```markdown
+<Paste output of "perl mysqltuner.pl --debug [arguments]" here>
+```
+
+**To Reproduce**
+Steps to reproduce the behavior if not fully captured by the debug output:
+1. Run command '...'
+2. See error '...'
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Additional context**
+Add any other context about the problem here (e.g. custom configuration files, /etc/my.cnf).

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Stack Overflow
+    url: http://stackoverflow.com/questions/tagged/mysqltuner
+    about: Please post usage questions or support issues on Stack Overflow using the 'mysqltuner' tag.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for MySQLTuner
+title: '[ENHANCEMENT] '
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. (e.g., I'm always frustrated when [...])
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.husky/commit-msg

@@ -1 +1,16 @@
-npx --no-install commitlint --edit "$1"
+#!/bin/sh
+
+# Run commitlint first to validate the commit message format
+npx --no-install commitlint --edit "$1" || exit 1
+
+# Check if Changelog is staged when commit type is feat or fix
+COMMIT_MSG_FILE="$1"
+FIRST_LINE=$(head -n 1 "$COMMIT_MSG_FILE")
+
+if echo "$FIRST_LINE" | grep -qE "^(feat|fix)(\([^)]+\))?!?:\s" ; then
+  if ! git diff --cached --name-only | grep -q "^Changelog$"; then
+    echo "ERROR: Commit type 'feat' or 'fix' detected, but 'Changelog' is not staged."
+    echo "Please update and stage 'Changelog' before committing."
+    exit 1
+  fi
+fi

.husky/pre-commit

@@ -1 +1,8 @@
-npm test
+#!/bin/sh
+
+# Only run tests if code, tests, build scripts, Makefile, or package configuration has changed
+if git diff --cached --name-only | grep -qE '\.(pl|pm)$|^tests/|^build/|^Makefile$|^package(-lock)?\.json$'; then
+  npm test
+else
+  echo "Husky [pre-commit]: No code or test files modified. Skipping unit tests."
+fi

CURRENT_VERSION.txt

@@ -1 +1 @@
-2.8.45
+2.9.0