AER v5 succeeds v3.1.1 directly. V4 was an unreleased experiment and is skipped.
What changed
- A compact 45-line universal contract puts complete behavior, coherent design, exact contracts, engineering judgment, and evidence-backed completion first. Diff size is neutral; both symptom patches and speculative architecture are discouraged.
- Verification investment follows the feature's risk, lifespan and stability. Permanent tests are a separate decision, valid evidence is reused, and selected UI guidance explicitly covers draft preservation and keyboard focus after rendering.
aer verify <contrast|slop|size>selects an optional diagnostic. It does not run project scripts or certify completion. Runtime modules ship once and are installed through the existing ownership checks.- Provider-free validators cover the corpus, all 110 grievance owners, frozen historical records, complete instruction loads and the actual npm package. Dormant evaluation execution machinery is removed.
Install or upgrade
Requires Node.js 24 or newer.
npm install --global @aaarslan/aer@5.0.0
# New managed project: choose the host actually used by the repository.
aer init --host codex --dry-run
aer init --host codex
# Existing managed project after upgrading the CLI.
aer update --dry-run
aer update
aer doctorUse --host claude for Claude Code or --host both when both are used. Preserve the existing ownership ledger and consumer instructions. V4 experimental hook/runtime installs are not a supported automatic migration source. Installation and migration explain collision and recovery behavior.
Validation and evidence limits
The full local release gate passed: 62 main tests, 6 research tests, 91 source files, 39 expanded load plans and an isolated installation of the 96-file package. Linux, Windows, research validation and CodeQL passed on the release PR and merged commit. PR #10 contains the reviewed change; release validation and CodeQL record the merged checks.
No general efficacy, token savings or verification-cost claim is made. In one known-task comparison, v5 and v3.1.1 tied at ten of ten exercised groups and the baseline passed eight. V3.1.1's reset check used a confirmation adapter; the native dialog remains unverified. The comparison record preserves those qualifications.
The attached package and SHA-256 checksum identify the validated release artifact. Full changelog.