Refactor TinyLlama inference tests and update LLM configuration

- Updated EmbeddedLLM configuration in test_llm_tinyllama_inference.cpp to use new parameters (n_ctx, n_batch).
- Changed skipIfNoModel() to void return type and adjusted its usage in multiple tests.
- Improved test readability by removing unnecessary return statements.
- Updated test cases to ensure proper handling of model availability.
- Renamed getSolution to getRecoveryHint in test_utils_llm_path_focused.cpp for clarity.
- Introduced a Workflow Filename Rename Matrix to standardize workflow file naming conventions.
- Added a canonical milestone registry to manage project milestones effectively.
- Created maintenance workflows for issue closure recommendations and milestone synchronization.

Author: makr-code

.github/GOVERNANCE.md

@@ -130,6 +130,8 @@ Use version milestones when a fix or feature must ship in a specific release, in
 - Every milestone **MUST** have a due date.
 - Milestone names use the exact formats above — no variations.
 - When an issue slips, move it to the next milestone; do not leave it unassigned.
+- Milestones are managed canonically via `.github/milestones.yml` and synchronized by `.github/workflows/maintenance-milestones.yml`.
+- Hotfix and strategic lanes are supported via dedicated milestones (`HOTPATCH`, `LONG-TERM`) and label-driven auto-assignment rules.
 
 ---
 

.github/PR_LABELING_GOVERNANCE.md

@@ -5,7 +5,7 @@
 This document defines the governance for automatic PR labeling and milestone assignment in ThemisDB. The system uses three complementary labeling mechanisms to ensure comprehensive PR classification:
 
 1. **Path-based labeling** (`.github/labeler.yml`) — automatic label application based on changed files
-2. **Milestone assignment** (`automation-community.yml`) — automatic milestone mapping based on ROADMAP Waves
+2. **Milestone assignment** (`maintenance-milestones.yml`) — automatic milestone sync + assignment based on labels and Target Version
 3. **AI semantic labeling** (optional, `automation-community.yml`) — semantic analysis of PR title/body
 
 ## Label Taxonomy
@@ -84,36 +84,30 @@ Labels indicating release or quality status.
 
 ### Automatic Milestone Logic
 
-The `assign-milestone` job in `automation-community.yml` automatically assigns milestones based on changed files:
-
-1. **Wave A modules** → `Q4-2026`
-   - Includes: access_model, search, sharding, replication, utils, updates, process, audit
-   
-2. **Wave B modules** → `Q4-2026`
-   - Includes: llm, retrieval, tensor, gpu, acceleration
-   
-3. **Wave C modules** → `Q4-2026`
-   - Includes: security, auth, governance
-   
-4. **Wave D modules** → `Q1-2027`
-   - Includes: observability, maintenance, docs/operability
-   
-5. **Documentation-only changes** → `Documentation`
-   - Detected by PR title or `.github`, `docs` patterns
-   
-6. **Other changes** → `Backlog`
-   - Changes not matching any Wave or documentation pattern
+The `assign-milestone` job in `maintenance-milestones.yml` automatically assigns milestones based on label rules and optional Target Version override:
+
+1. **Hot patch labels** (`hot-patch`, `priority:critical`, `severity:critical`, etc.) → `HOTPATCH`
+2. **Long-term labels** (`long-term`, `roadmap/long-term`, etc.) → `LONG-TERM`
+3. **Wave D labels** (`wave:D`) → `Q1 2027`
+4. **Wave A/B/C labels** (`wave:A`, `wave:B`, `wave:C`) → `Q4 2026`
+5. **Documentation labels** (`type:documentation`, `docs`) → `Documentation`
+6. **Explicit backlog label** (`backlog`) → `Backlog`
+7. **Fallback** → default milestone from `.github/milestones.yml`
+
+If a PR includes `Target Version` in the body, that value can override label mapping (`allow_target_version_override`).
 
 ### Valid Milestones
 
-The following milestones should exist in the repository:
+The following milestones are maintained canonically in `.github/milestones.yml` and synchronized automatically:
 
-- **Q4-2026** — Q4 2026 delivery cycle (Wave A, B, C exit criteria)
-- **Q1-2027** — Q1 2027 delivery cycle (Wave D)
+- **Q4 2026** — Q4 2026 delivery cycle (Wave A, B, C exit criteria)
+- **Q1 2027** — Q1 2027 delivery cycle (Wave D)
 - **Documentation** — Documentation and governance updates
+- **HOTPATCH** — Urgent production fixes/security incidents
+- **LONG-TERM** — Long-term roadmap items
 - **Backlog** — Future work or unscoped items
 
-> **Note:** If a milestone does not exist in the repository, the milestone assignment job will skip assignment and log a message. Milestones must be created manually via repository settings.
+When `auto_create_missing_milestones` is enabled, missing milestones are auto-created during assignment.
 
 ## AI Semantic Labeling
 
@@ -149,10 +143,10 @@ Detected classifications are converted to labels and merged with existing labels
 
 ### Milestone Assignment
 
-- Triggered on PR `opened`, `synchronize` (not draft PRs)
-- Configuration: `assign-milestone` job in `automation-community.yml`
-- Permissions: `pull-requests:write`, `contents:read`
-- **Skips** if the repository lacks required milestones (logs warning)
+- Triggered on `issues` and `pull_request_target` events (`opened`, `labeled`, `unlabeled`, `edited`, etc.)
+- Configuration: `.github/workflows/maintenance-milestones.yml` + `.github/milestones.yml`
+- Permissions: `issues:write`, `pull-requests:write`, `contents:read`
+- Supports hot-patch and long-term lanes out of the box
 
 ### AI Semantic Labeling
 
@@ -166,24 +160,24 @@ Detected classifications are converted to labels and merged with existing labels
 
 ### When to Update Labels
 
-- **New modules added to Wave A/B/C/D** → Update `labeler.yml` and `assign-milestone` job
+- **New modules added to Wave A/B/C/D** → Update `labeler.yml` and `.github/milestones.yml` assignment rules
 - **ROADMAP Wave structure changes** → Update milestone mapping and wave labels
 - **Build/CI infrastructure changes** → Update type:ci label patterns
 
-### When to Create Milestones
+### When to Update Milestones
 
-Create milestones in repository settings when:
-- New quarterly cycle begins (e.g., Q2-2027)
+Update `.github/milestones.yml` when:
+- New quarterly cycle begins (e.g., Q2 2027)
 - New Wave is introduced to ROADMAP
-- New governance phase is needed
+- New governance lane is needed (e.g., emergency hotfix stream)
 
 ## Governance
 
 **Maintainer Responsibilities:**
 - Keep `.github/labeler.yml` synchronized with module structure
-- Ensure `automation-community.yml` milestone logic matches `ROADMAP.md` Waves
+- Ensure `.github/milestones.yml` assignment rules match `ROADMAP.md` waves and label taxonomy
 - Monitor AI labeling accuracy and disable if producing false positives
-- Create/retire milestones as needed
+- Create/retire milestones via config changes (synchronized by workflow)
 
 **Documentation Synchronization:**
 - Changes to labeling rules must update this file
@@ -202,7 +196,7 @@ Expected labels:
 - type:test (path-based)
 - release_critical (path-based)
 
-Expected milestone: Q4-2026
+Expected milestone: Q4 2026
 ```
 
 ### Documentation-Only PR
@@ -230,23 +224,23 @@ AI detected labels:
 
 Combined with path-based labels: area:access-model, wave:A
 Final labels: area:access-model, wave:A, breaking-change, severity:high, impact:api
-Expected milestone: Q4-2026
+Expected milestone: Q4 2026
 ```
 
 ## Troubleshooting
 
 ### PR not assigned expected milestone
 
 **Possible causes:**
-1. Repository lacks required milestone — create it in Settings > Milestones
+1. Assignment rule in `.github/milestones.yml` does not match current labels
 2. Changed files don't match any Wave pattern — assign manually or verify labeler.yml
 3. PR is draft — milestones only assigned to open PRs
 4. PR is targeting a non-develop branch (conditional logic may exclude it)
 
 **Resolution:**
-- Check `automation-community.yml` job logs for "Milestone not found" messages
-- Verify changed files against Wave patterns in `labeler.yml`
-- Create missing milestones manually if needed
+- Check `.github/workflows/maintenance-milestones.yml` run logs for rule resolution and API results
+- Verify labels on the issue/PR and the configured `assignment_rules` in `.github/milestones.yml`
+- Verify `allow_target_version_override` and `auto_create_missing_milestones` settings
 
 ### AI semantic labels not applied
 

.github/TODO_KI_WORKFLOW_IMPROVEMENTS.md

@@ -127,7 +127,7 @@ Zieldatei: `.vscode/launch.json` (repo-versioniert via `.vscode.example/launch.j
 - [x] Ziel: dynamische Prüfung auf Laufzeitfehler in KI-generiertem C++-Code
 
 ### 4.3 CodeQL-Workflow auf `paths:` eingrenzen
-- [x] `codeql.yml` aktuell triggert auf alle PRs nach `develop` ohne `paths:`
+- [x] `security-codeql.yml` aktuell triggert auf alle PRs nach `develop` ohne `paths:`
   — prüfen ob dies WORKFLOW_GUIDELINES-konform ist
 - [x] `paths:` auf `src/**`, `include/**` begrenzen (Docs/Meta-Änderungen
   lösen keinen CodeQL-Scan aus)