Pass 126
2026-11-05 17:09 PST (2026-11-06T01:09:05Z UTC) · commit 9a9a517 (9a9a5178144c2813f05a84d2e2e09b4cc94b6a6e)
ADOPTED
COURTYARD CAMPAIGN item 1 (U6 cluster): C49 (89,-9)->(97.5,-12), R15 (89,1)->(97.5,-15.5), R16 (89.5,-2)->(97.5,-18), C19 (95,1)->(97.5,-9.5), C18 (94,-4)->(95.5,-4), U5 (68,-18.5)->(66,-20.5). Pairs closed (7): U6xC49, U6xR15, U6xR16, U6xC19, MH2xC19, U6xC18, U6xU5. New instrument hw/move_part.py: courtyard-clear offset + straight re-lay on the anchor’s own layer + via-relay fallback, group-count guard per pad net. R15 (both pads) and C19 (NRST) reconnected by relay, counts unchanged; prune_dead run after the moves. VICTIMS NAMED AS OWED: +3V3A C49 leg (pad detached, relay refused at both tried sites; net was 1 group, now 2), BOOT0 R16 leg (1->2), and the U5 nudge split +3V3D, CDR_CLKN, CAP_CLK, CAP_DATA (each 1->2 in the repair model; DATP/DATN/CLKP held by relay) – all repay in the resumed routing queue. VCAP2 unchanged (2 groups before and after; already a residue net). GND repair-model groups 52->56 (audit is zone-inclusive; its count governs). U6xMH2 still open: neither part may move (U6 load-bearing, MH2 a mounting hole) – escalated to parent with the polygon data.
| Nets fully routed | not recorded |
| Pins failed | not recorded |
| Clearance violations | 112 |
| Unconnected nets | 30 |
| Audit verdict | FAIL |
Routes — all copper layers and each layer
F.Cu In1.Cu In2.Cu B.Cu
Top
Bottom
← Pass 125 · all passes · Pass 127 →