A datasheet-to-footprint builder ran on 40 held-out parts: adding new datasheet PDFs raised correct parts from 21 to 23 but also produced 7 footprints that were built wrong. This PR gets that to 0 wrong and 27 right, mostly by falling back to KiCad's checked land when a datasheet prints none and holding the part with a page number when the read missed one. Second time in two days this repo shows more source documents making the output less trustworthy before it gets better.

Wrong design output reported against PCBLIVINGLIBRARY (oliBrowne)

PCBLIVINGLIBRARY (oliBrowne)Electronics & PCBWrong design outputMedium confidence

What engineers report

A wrong design output reported against PCBLIVINGLIBRARY (oliBrowne): produces incorrect geometry, routing, values or parts.

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 PCBLIVINGLIBRARY (oliBrowne).

Evidence

  1. 1oliBrowne/PCBLIVINGLIBRARY PR #247: Held-out new PDFs: built wrong 7 -> 0 (standard_land auto, TO-263-4, maker outlines, pull-back hold, op-amp names)github.com

More recurring errors in PCBLIVINGLIBRARY (oliBrowne)

See all 17 PCBLIVINGLIBRARY (oliBrowne) 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.