pkidl routes a board a second time when pours leave pads cut off, and that second routing was never checked until now. KiCad 10.0.6 names the starved GND thermals on the next-bus clock board (D1, C5, C6, SR1 pads against the B.Cu zone), but pkidl's own model of the fill does not report a starved relief. Built without KiCad, the same board comes back with nothing left, and the PR says plainly the error is still on the board.

Wrong verdict reported against pkidl (feastorg)

pkidl (feastorg)Electronics & PCBWrong verdictMedium confidence

What engineers report

A wrong verdict reported against pkidl (feastorg): a check, review or gate reports pass or fail incorrectly.

Recorded mode: agent / failure

Analyst note

From the Grok pain-radar digests, Nov 13-14 2026 (Nov 13 10:41 AM ET through Nov 14 7:41 AM ET digests plus the Haitch editions). Verified live 2026-11-14: issue/PR read; title and state confirmed.

What it costs a team

Modeled annual cost

$30,000

For a team of 5

Prototype delay

3 days

Modeled schedule slip per occurrence

Time lost

240 min

Per engineer per month, about 1 incidents

How the cost is modeled

240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000

A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.

Engineering tools that address it

No engineering tool profile lists this error yet. Browse tools that connect to pkidl (feastorg).

Evidence

  1. 1feastorg/pkidl PR #60: feat(routing): check the board routed again without its poursgithub.com

More recurring errors in pkidl (feastorg)

See all 4 pkidl (feastorg) errors

Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.