aptitude-gatelisted

# aptitude-gate — release-readiness verdict Turns evidence into a single decision — **PASS / CONCERNS / FAIL / WAIVED** — and writes it to the `gate` block of the standardized run manifest (shared output contract, [`docs/OUTPUT-CONTRACT.md`](https://github.com/QAIA-Project/QAIA/blob/main/docs/OUTPUT-CONTRACT.md)) — that path is in the QAIA source repository, **not in the installed plugin**, so rely on the field names restated below when you do not have the repo.. It combines the quality score (`testbook-score`), the hard coverage gates, the pending human arbitrations, and — when present — the execution results. It **scores only**: it decides readiness and names what blocks it; it never edits a scenario (guardrails in `../README.md`). ## Prerequisite `.qaia/reports/<US-ID>/manifest.json` must **exist**. If the manifest itself is absent — no `report`/`run-report` has run yet — say so and offer to run `qaia-core:report` first instead of gating on nothing; do not invent a manifest or a verdict. If the manifest exists but `gate.score` is empty, that is a lesser gap: ideally `testbook-score` has already filled it; if not, run that first (or score inline using its rubric) — a verdict without a quality score is only a hard-gate check, and the skill says so. ## Verdict rules (deterministic — apply in order) Evaluate top to bottom; the **first** matching band is the verdict. 1. **FAIL** — any hard gate is broken (release-blocking): - `structural.forcedStop` is true, or `struct