AI Flow
Public Made by Adomby adom
Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board.
Explicit capture stop omits visit number from clip artifact step tag
AI Flow 0.1.5: step stopping a recording emits clip/clip10x artifact step tags such as routing-5, but explicit capture stop emits only finish, losing the visit suffix. The captures manifest still identifies finish visit 1. This breaks a composer that uses the documented per-visit artifact order consistently.
Reproduction in ESC Astra run: finish passed, capture stop pulled window-16521934-20260914-042801-10x.mp4, artifact has step=finish, whereas preceding explicit step transitions produce capture-2, thermal-3, etc. All 21 clips exist, so no footage was lost.
Workaround: composer resolves the unsuffixed final artifact to the matching captured visit using run metadata; it does not rewrite run.jsonl. Please use the same artifact tag construction in explicit capture stop and automatic step stop, or provide separate step and visit fields everywhere. Add a regression comparing both paths for repeated visits.