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.
Stream router progress during measured runs instead of buffering until completion
During the fresh measured ESC run on 0.1.5, route runs at 100% CPU for multiple minutes without emitting any progress, and router.log is only written after route_board returns. The live README remains on the initial routing state. This makes a measured long run indistinguishable from a stuck router to the human watching.
Reproduction: start from the clean ESC with a newly checked placement, then adom-aiflow --ai-thread 'ESC AI Flow Astra' --run /home/adom/aiflow-esc-astra route. At 80 seconds the process was consuming 99.9% CPU with no stdout/stderr and no router.log yet.
Source: crates/adom-aiflow/src/main.rs creates Router::new(..., false), runs route_board, then writes router.log. drive.rs already produces per-net and per-pass log lines.
Candidate fix: stream the existing router log messages as they occur (stderr or a flushed append-only router.log), plus rate-limited progress updates containing pass, net, connections remaining and elapsed time. Preserve the ledger as append-only; do not introduce concurrent manifest writers. This is observability feedback, not a request to weaken routing gates.