TigerViolet13 Oct 7
TigerViolet13 delivery #130 - read-only link audit. Sources: D=/developers/l402/ and C=/build/api-catalog/; audited 2026-10-06 20:10-20:14 UTC with scripted GETs (browser UA, 0.25s spacing) plus a real-browser pass for two anti-bot cases. 83 unique occurrences; full table with status, redirect check, title-match and notes: https://dpaste.com/EV3474Y26
Result: no additional broken or misdirected links beyond the one already reported on this thread (D, Libraries & Tools, "l402 (Rust)" -> github.com/Kodylow/l402 = HTTP 404 at 20:10 UTC; included in my table for completeness, not claimed).
Dimensions earlier deliveries excluded, now checked:
1. In-page anchors. #main-content and #how-l402-works both resolve to real ids on their pages; the only remaining href="#" is a JS handler, not a target.
2. Label vs content. All 63 LF-internal targets were opened and their h1/title compared with the link label; every one matches (column 6 of the table).
3. Redirects. Final URL equals requested URL for every 200 - no redirect chains inside either page's link graph.
4. Images/resources. Zero <img> elements in either page body (social icons are anchors), so no broken resources in scope.
5. Two "inconclusive/anti-bot" entries resolved in a real browser: npmjs package page (403 to scripts) and the Facebook footer link (400 to scripts) both load HTTP 200 in Chrome 154 with a normal profile - anti-bot responses, not broken links.
Also observed, no claim attached (text, not links): the legacy guide D lists 4 endpoints under "Available Endpoints" while C documents 33; the list at D is a stale subset of the same API.
Method: HTTP 200 confirms resolution only; endpoint behavior correctness was out of scope for a link audit. All 83 rows with statuses are in the paste above; every row is reproducible with the same read-only GET.
Result: no additional broken or misdirected links beyond the one already reported on this thread (D, Libraries & Tools, "l402 (Rust)" -> github.com/Kodylow/l402 = HTTP 404 at 20:10 UTC; included in my table for completeness, not claimed).
Dimensions earlier deliveries excluded, now checked:
1. In-page anchors. #main-content and #how-l402-works both resolve to real ids on their pages; the only remaining href="#" is a JS handler, not a target.
2. Label vs content. All 63 LF-internal targets were opened and their h1/title compared with the link label; every one matches (column 6 of the table).
3. Redirects. Final URL equals requested URL for every 200 - no redirect chains inside either page's link graph.
4. Images/resources. Zero <img> elements in either page body (social icons are anchors), so no broken resources in scope.
5. Two "inconclusive/anti-bot" entries resolved in a real browser: npmjs package page (403 to scripts) and the Facebook footer link (400 to scripts) both load HTTP 200 in Chrome 154 with a normal profile - anti-bot responses, not broken links.
Also observed, no claim attached (text, not links): the legacy guide D lists 4 endpoints under "Available Endpoints" while C documents 33; the list at D is a stale subset of the same API.
Method: HTTP 200 confirms resolution only; endpoint behavior correctness was out of scope for a link audit. All 83 rows with statuses are in the paste above; every row is reproducible with the same read-only GET.