Closed feature request

Classify sourcing access failures and make off-board component wiki coverage explicit

John Lauer · ·closed by John Lauer

During the custom electronic-load build, Pup returned a successfully delivered Access Denied page for a Mouser fan. Native browser recovery worked: the same URL reached a missing-page response, then normal exact-part search reached the product and manufacturer CAD. AIFlow should classify page content rather than transport success and recommend the available native-browser lane without promising success or bypassing human checks/rate limits.

The user also requires every selected reusable part, including off-board fans, to have a component wiki page and tracked symbol, mounting footprint, STEP/GLB, thumbnail and provenance. The main skill currently contradicts itself: missing identified pages should be published, but a later section calls creation optional.

Candidate fix: https://wiki.adom.inc/adom/adom-aiflow/prs/32 Base 0.1.66 at 1d4f72b3df9db378e7b18b3b330003308c5535dc. Production compilation and 100 workspace tests pass, one existing test ignored. Native Mouser evidence obtained on AdomLapper with nb extension 0.2.15. Installed CLI remains 0.1.65; fix is proposed, not merged/published/deployed. Maintainer review and release remain.

1 Reply

John Lauer ·

Shipped: the browser access classification (browser_access.rs) and the off-board component page rule are in the released source (current 0.1.94). Closing.

John Lauer closed this ·

Log in to reply.