awslabs/aidlc-workflows v2.11.4-preview.20261106.1

AI-DLC Workflow 2.11.4-preview.20261106.1

on GitHub

Merged commits since preview source bcbf4ca:

• fix(engine): a second chat leaves a side-by-side build another chat started to that chat, until you ask it to take over (#3651)
• fix(sensors): at the end of Code Generation a team's blocking check asks plainly, takes the person's own words and is not asked again (#3671)
• fix(kiro): on a 200k model the chat-full line says by Kiro's count why a new chat will not help much (#3674)
• fix(units): a Unit's redo after Unit-by-Unit work finished at Code Generation runs for that Unit (#3672)
• fix(units): a share right after choosing teams carries the lead's no to a thin slice first, so the teams can take every Unit (#3661)
• fix(checks): switching the checks off to answer a check's question records the answer and goes on (#3664)
• fix(native): in a project with more than one tool set up, each tool's chat gets its own steps (#3670)
• fix(kiro): an older copied tool's --harness kiro asks before switching a Kiro project to Kiro CLI (V2) (#3627)
• fix(kiro): a dropped plugin's registration is recognised only when it is a plain file (#3582)
• docs: the glossary and reference say the learnings step asks only about corrections, never offers the diary (#3669)
• fix(rules): a stage run on its own hands its helpers that stage's rules, the team's own included (#3665)
• fix(kiro): the aidlc agent is told from the chat's start to read your files with its file tools and run AI-DLC commands alone (#3653)
• fix(status): status says where each Unit stands in work built one Unit at a time, and what comes next (#3648)
• fix(guards): what the person asks for after work finished at Code Generation goes through (#3657)
• fix(kiro): on a 200k model the chat-full offer says a new chat on the same model will not help, instead of recommending one (#3650)
• test(e2e): t56 checks a forward jump's line on the step the agent speaks from, said once (#3656)
• fix(checkpoint): a Unit's checkpoint question says what an advisory check still finds on its files (#3624)
• fix(units): a lead's no to a thin slice first holds for teams before Construction, so no Unit waits on a walking skeleton (#3647)
• fix(plan-approval): the plan question's answer counts when the question box also asks another question (#3649)
• fix(repos): in a project with code of its own, a git submodule is no longer recorded as the work's repo (#3641)
• fix(kiro): a switched-off hook's line names its file and setting, so Kiro CLI has a way back (#3625)
• fix(engine): a stage finished in another chat is shown at its gate, not written again (#3638)
• fix(swarm): a side-by-side Unit's merge says it kept your change only once the Unit has landed (#3645)
• fix(units): on Windows, a team's publish of many new files goes through instead of failing at git add (#3643)
• fix(new-work): the clean-chat offer names the person's own tool's step and comes before the first stage (#3635)
• fix(units): a Unit command's --help prints its usage and never commits or pushes (#3620)
• fix(checkpoint): a team's blocking check is met at the Unit it fails on, not after the last Unit (#3623)
• fix(requests): a request typed again in a new chat while the plan question waits is the one the work records (#3622)
• fix(units): a teammate's claimed Unit starts beside the lead's Unit in progress, and the lead's own Unit stays theirs (#3626)
• fix(hooks): the status sync leaves Current Stage on the step the engine issued, so the Units after a walking skeleton go through their design stages (#3618)
• fix(plan-approval): a lead's plan approval is recorded after their own checkout claims the Unit (#3613)
• fix(units): a team's publish question fits its step in any checkout, and the publish commits only the Unit's own work (#3615)
• fix(kiro): a reply that was not recorded says it may be asked for again (#3614)
• fix(codekb): Reverse Engineering's snapshot says a path is outside the project, or in another repo, instead of blaming a socket or pipe (#3599)
• fix(units): a Unit's source list in multi-repo work never approves a file that is not there (#3602)
• fix(lifecycle): a system command's --help prints its usage and changes nothing (#3598)
• fix(sensors): a team check whose glob has **/ before the file name runs at the gate instead of could not run (#3597)
• fix(config): config --help names --harness and the tools it sets up (#3593)
• fix(refusals): the sync-folder hint is said only for a project in a synced folder, with its step (#3577)
• fix(plugin): a plugin's added output is still skipped, not rolled back, when the engine words its stage check differently (#3576)
• fix(scopes): infra writes its IaC in Code Generation (#3568)
• fix(hooks): the status sync leaves a claimed Unit's cursor on its own stage, so a team-scoped checkout can take a step on Kiro IDE (#3379)
• fix(units): a team name with an apostrophe is recorded whole when a teammate takes a Unit on Windows (#3573)
• fix(kiro): --harness kiro sets up Kiro and --harness kiro-v2 Kiro CLI (V2) (#2924)
• fix(unit): pin and land say what to do about a record outside the Unit's tree (#3507)
• fix(doctor): name a registered repo that is not a checkout on disk (#3536)
• fix(traceability): a ui Unit's Functional Design traces to its design files, not to business rules it does not write (#3510)
• fix(plugin): the missing-plugin row says a folder-composed plugin still works (#3553)
• fix(plugin): a plugin can add an output to functional-design or infrastructure-design without failing the graph compile (#3567)
• fix(doctor): Codex's AGENTS.override.md stays yours; doctor says what Codex reads there and offers AI-DLC's block (#3571)
• fix(units): a team Unit's stage diary, written after the review, leaves the review standing at pin (#3512)
• fix(refusals): name the files a stale fingerprint covers and say a sync client can cause it (#3566)
• fix(engine): a subcommand's --help prints its usage instead of running it (#3519)
• fix(guard): a written script is refused only for the trail it writes (#3565)
• feat(units): taking a Unit says what waits on it, who holds the others and the label your team gets (#3570)
• fix(claude): AI-DLC's own commands run without a permission prompt when a helper spells the project's path in full (#3467)

Source commit: 11daa8f