[2.9.0] - 2026-09-15
AI-DLC 2.9.0 rolls up the user-visible changes merged since 2.8.2, including the Classic scope v1 ceremony model, commit provenance, intent archiving, on-demand Construction autonomy, review-loop corrections, and the native preview release channel. Upgrade: run aidlc update, then run aidlc config --yes in each project to refresh its harness runtime. Manual-copy users must replace the complete runtime/<harness>/ tree from aidlc-copy-runtime-2.9.0.tar.gz. Existing in-flight Classic intents keep their recorded stage graph; the new ceremony defaults apply immediately where noted below.
aidlc versionreports2.9.0on Claude Code, Codex CLI, GitHub Copilot, Cursor, Kiro CLI, Kiro IDE, and opencode.- New Classic intents use the 18-stage v1 flow through Build and Test, with one approval per stage, one advisory review pass where configured, sensors and learnings enabled, and summary confirmation disabled. Existing Classic intents keep their recorded graph; use the
workshopscope when the previous Classic graph with CI Pipeline and Operation stages is required. - Ceremony is scope-owned and can be changed per intent with
--sensors,--learnings, and--summary-confirmation.aidlc engine config setapplies depth, testing, review, change-control, and ceremony settings as one transaction. Breaking for scripts: the standaloneaidlc-utility.ts change-controlroute is removed, and unknownconfig-changeflags now fail instead of being ignored. aidlc confignow resolves provider choices per harness. Kiro CLI and Kiro IDE need no provider answer: model access comes with Kiro, so the first-run wizard andaidlc config providersstate that and ask nothing, provider flags are refused there, and a provider record left by an earlier build is ignored (aidlc config providers --reset --yesclears it). Theaws-mcpregion in.kiro/settings/mcp.jsonis kept as the project has it across refreshes. Other harnesses offer Amazon Bedrock orunchanged, which keeps the current provider. Thebalancedpreset now records medium deciding, reviewing, and writing-up effort.aidlc engine orchestrate waitprovides a bounded read-only wait for collaborators, artifacts, or reviews. Record-level engine files now live under<record>/.aidlc-engine/; existing records remain readable through legacy-path fallbacks./aidlc intent archive <name>retires an unfinished intent without deleting its record or audit trail./aidlc intent unarchive <name>restores it, andintent list --allincludes archived intents.aidlc attest resolvemaps a commit or diff range to reviewed Units and reportsverified,drifted,unattested,unverifiable,indeterminate, orexcluded.aidlc attest anchorrecords commit pointers in the audit trail. Reviews created before 2.9.0 have no committed source evidence and reportunverifiableuntil the next per-Unit review.- Construction autonomy can be granted or revoked on demand. The choice persists in older records that did not already contain the state field, while the first Construction approval, Code Generation Plan Approval, and failure stops remain human-owned.
- Advisory review retries now use the engine's current ordinal after a rejected gate, avoiding false
REVIEW_BUDGET_EXHAUSTEDdead ends. Review bookkeeping stays in review records and audit data instead of becoming artifact content or new reviewer findings. - Kiro IDE read tools remain available during Code Generation Plan Approval recovery while write, shell, MCP, and delegated mutation paths stay guarded.
- Stable and preview release packaging now separates the native
aidlc-runtime-2.9.0.tar.gzasset from the Bun-basedaidlc-copy-runtime-2.9.0.tar.gzmanual-copy asset. Versioned installers install the release that carries them, including previews, and multiple changedmaincommits can publish previews on the same UTC date. - Repository maintainers can run the adversarial AI pull-request review workflow for same-repository PRs, with prompt-injection, security, and project-aligned review passes plus deterministic publication validation.
Source commit: 891669a