# v0.4.9–v0.4.11 — Quick Workflow and Review Lifecycle

## v0.4.9 — QuickContract and deterministic triage

`aeh triage` accepts evidence collected by the lead (request, explicit file scope, domains, risk and escalation flags). QUICK is allowed only for bounded low-risk work with no architecture/security/auth/schema/migration/public-API/dependency escalation signal. Everything else is SPEC.

A QuickContract is stored in the normal contracts directory with `mode: quick`, explicit acceptance statements, scope and immutable constraints (`breakingApiChanges=false`, `newDependencies=false`, `schemaChanges=false`). It is SHA-256 sealed like a normal TaskContract but does not require SDD artifacts.

Commands:

```bash
aeh triage "Change button padding" --file src/Button.tsx --domain frontend --risk low
aeh quick new QUICK-001 --title "Adjust button padding" --request "Change button padding" --scope src/Button.tsx --acceptance "Button uses 16px padding" --domain frontend
aeh quick validate QUICK-001
aeh run QUICK-001
```

## v0.4.10 — Automatic review lifecycle

After deterministic validation passes for a SPEC task, the Harness executes routed reviewer agents concurrently. Reviewers must emit a typed `AEH_RESULT_JSON` payload. Findings are normalized and deduplicated. Configured blocking severities trigger bounded remediation followed by deterministic revalidation and another review round.

When reviewer blockers are cleared, an orchestrator/lead performs final semantic acceptance and must return a valid orchestrator output with `finalizationSafe=true` and no unresolved items.

Default policy skips agent reviewers and lead acceptance for QUICK changes to keep small changes inexpensive. Projects can enable them with `workflow.reviews.reviewQuick` and `leadAcceptanceQuick`.

## v0.4.11 — Engineering workflow skill

`engineering-workflow` is installed by `aeh init` and attached to the default lead agent. It teaches a Codex lead—especially one started from Paseo mobile—to inspect the repo, gather triage evidence, obey QUICK/SPEC classification, create the correct contract/spec, invoke `aeh run`, remain the parent owner and surface only meaningful failures/approvals/final acceptance.

The skill also defines self-modification safety: control-plane changes produced during a run do not govern that same run; the new controller/topology becomes active on a later validated run.
