Skip to content

v1.88.0 ·

Finished work files its idea even when the link is lost

Three things about finished work and the guardrails around it were wrong, and this release fixes all of them. The first is the one that was visibly losing work.

On 2026-10-09 two roadmap items, agent-binary-missing-crashes-loop and help-epilog-parsed-as-options, reached the in-progress stage with promoted_to set to null. The roadmap-done action finds the items to file by that field alone, so completing their instances filed nothing, and the roadmap showed shipped work as still in progress. Each instance's own copy of its roadmap item still carried the right id and promoted_to.

Filing without the link

I never found the cause. I checked every lead and ruled each out: the timeline that looked suspicious was a UTC versus EDT misreading, and the one step that could have restored the old text kept the edit when tried. So I stopped chasing it and made the outcome impossible to miss. When an item still names the instance, it is filed exactly as before and the copy is never read. Only when nothing names the instance does the copy's id come into play, and only for an item whose link is empty. An item linked to other work is never taken, so a shared id cannot move the wrong thing. The filed item gets its link back, and a line says it was matched by id because its link was missing. aidlc doctor takes the same fallback, so items already stranded this way are found and filed without anyone doing it by hand. roadmap-done lives in packages/cli/src/events/event-bus.ts, and 15 new tests cover it.

An agent can no longer approve its own gates

aidlc autopilot approve, aidlc transition --override and aidlc amend --confirm now refuse with exit code 2 when stdin is not a terminal or AIDLC_UNATTENDED=1, before reading or writing anything, and say why. At a terminal they work as before. aidlc hook install and aidlc init also write an approval guard script and a Claude Code PreToolUse entry. It blocks those commands in an agent's shell, and blocks file edits to the autopilot approval record. It fails closed: a missing script, a missing node or a crash blocks the call and says to reinstall. Each refusal is one line in refusals.ndjson under the git common directory.

This is a minor release, not a patch, because three commands now refuse where they used to run. A script or CI job that runs any of them without a terminal fails with exit 2. Nothing in this repo's scripts/ or .github/ does.

Blocking checks now block

A lifecycle action marked blocking: true did not actually stop anything. Now aidlc transition runs a phase's exit actions once every other gate has passed and before it writes anything. A failing blocking action stops the move, names the action and its error, and writes nothing. An untrusted run: command counts as a failure, and the error points at aidlc doctor. Actions on phase enter and on instance completion run after the move is recorded, so they keep it. A blocking failure there prints the error, says the move is already recorded, and exits 1. Before, only non-blocking failures printed at all.

Any repo with a blocking exit action that was failing silently will now be stopped by it. That is the fix. In this repo it is docs-drift-check on leaving implementation.