Closed bug report

Restore cleared escape terminals after rip-up; retry state currently loses them

John Lauer · 22d ago ·closed by John Lauer

reserve_escapes removes a terminal when existing foreign route copper blocks it, but when the blocker later clears it stamps the stub and removes the released flag without putting the terminal back. The route search therefore cannot use a now-clear escape. This state also survives reset between passes, which resets connected flags but does not rebuild terminals.

In the fresh ESC run the binary closed 21, then 8 after placement improvement, then 6 short after nine passes. Fresh-state orchestration did not itself solve closure; this issue does not claim the candidate patch alone completes the board.

The attached regression constructs a Router from the newly placed board, selects U5.15, models an escape removed while blocked by removing it from terminals and putting it in released, and invokes reserve_escapes with no foreign route copper. The original implementation fails the assertion that the terminal is restored; the candidate passes.

Candidate patch: after a released escape passes the blocker test and is stamped, add its Term back to terminals if missing. Do not restore blocked escapes or weaken any clearance/DRC gate.

Run evidence: https://wiki.adom.inc/adom/adom-aiflow/files/docs/runs/source-unplaced-codex-astra-20260914-0314/README.md

restore-escape.patch

restore_escape.rs.txt

restore-escape-baseline.txt

restore-escape-test.txt

1 Reply

John Lauer · 18d ago

Published and installed from insiders: adom-aiflow0.1.27 (and adom-fields0.3.1 for input identities). Source and registry publication both completed; installed hashes match the tested builds.

A released escape stub that becomes clear is restored to the cluster terminal search exactly once. Regression covers release, restoration and duplicate prevention.

Release notes: https://wiki.adom.inc/adom/adom-aiflow/files/docs/release-0.1.27.md Validation records: /home/adom/project/adom-aiflow-release-audit/ .

Log in to reply.