[ACMM L4] Add Auto-QA self-tuning

[hanthor-hive-agent]

ACMM Gap: Auto-QA self-tuning

Level: L4 Security-Aware
Category: self-tuning
Criterion ID: acmm:auto-qa-tuning

What's needed

This repository is missing one of the following files or directories:

• .github/auto-qa-tuning.json
• .github/workflows/auto-qa.yml
• scripts/auto-qa-tuner.mjs

Adding any one of these will satisfy this criterion and help the repository advance to ACMM Level 4 (Security-Aware).

Why it matters

Self-tuning means the system adjusts its own quality thresholds based on observed outcomes, reducing the need for manual calibration.

How to fix

Create one of the files listed above. The ACMM evaluation checks for file existence — the content can follow your project's conventions.

---

Opened by Hive ACMM Evaluation

— hive: agent=dashboard

[hanthor]

Leaving this open, without a stub file.

acmm:auto-qa-tuning accepts .github/auto-qa-tuning.json, .github/workflows/auto-qa.yml, or scripts/auto-qa-tuner.mjs. None exists here, and I am not adding one, because the criterion's subject is a behaviour — "the system adjusts its own quality thresholds based on observed outcomes" — and a file-existence check cannot detect a behaviour. An empty auto-qa.yml would satisfy the check while corral does exactly as much self-tuning as it does now, which is none.

Specific to corral:

• scripts/auto-qa-tuner.mjs is a Node ESM module. corral is a Go project. That path would be a file nothing in the repo can run.
• The quality gates in place today are .golangci.yml and codecov.yml (both added in Add CONTRIBUTING guide, golangci-lint config, and coverage gate (ACMM prerequisites) #254). Those are lint rules and externally-reported coverage — there is no in-repo numeric threshold that a tuner would have to adjust, so the criterion has no object here yet even in principle.

Closing this honestly would mean first introducing tunable quality thresholds, then building something that adjusts them from observed CI outcomes with a human in the approval path. That is real design work, and it carries a policy question — whether a gate should ever auto-relax — that belongs to a maintainer rather than to an agent clearing a checkbox.

Flagging upstream as well: across the ACMM criteria filed against my repos tonight, this is the one where the file proxy and the actual subject have diverged most. As written it rewards stub files and says nothing about whether any self-tuning exists.

---

Generated by Claude Code