Summary: Revalidated Flexoptix and FS.com price observations and product images after discovering price_observations were not marked verified and FS.com image selectors had gone stale.

Revalidate all Flexoptix and FS.com prices and check images without overloading Erik.

Set price_observations.is_verified=true and verified_at on new and fresh unchanged observations.

Always refresh image_verified_at/image_verified_url when a scraper sees a current product image.

Add FS.com force revalidate controls and targeted missing-image mode.

Update FS.com image selector to prefer resource.fs.com big_img/big_img_m product images and ignore logos/default/general images.

Run sequentially with maxConcurrency=1 and nice -n 10 on Erik because CT115 was not reachable from this session; monitor load and Crawlee overload signals.

No external AI was used for TIP crawler planning or extraction feedback.

FS.com and Flexoptix runs were sequential and rate limited; Erik remained stable.

The dedicated TIP scraper CT was probed but not used because SSH did not respond quickly.


Summary: Converted the manual equivalence review backlog into deterministic automated research decisions using existing crawled specs and prices. No heavy crawler wave was started.

Research all TIP product equivalences so they do not require manual validation.

Do not let approve-all approve low-confidence matches; queue them for automated research.

Add API endpoint to trigger equivalence research.

Replace price-only re-research with strict technical evaluator for price recency, form factor, speed, fiber type, wavelength, reach and confidence.

Use existing DB evidence only for cleanup. Keep Erik safe by avoiding crawler waves; schedule confirmed matches for future 30-day rechecks.

No new crawler wave was started on Erik.

Next enrichment should target rejected missing-evidence products on Proxmox or Pi workers with TIPLLM-only extraction feedback.


Summary: Rechecked Flexoptix price completeness and fixed audit timestamps for unchanged prices. Active catalog prices are freshly source-confirmed, but the full historical Flexoptix table is not complete.

Confirm whether all Flexoptix prices/images/information are present and whether prices are 100% correct.

Refresh price_observations.verified_at with NOW() when unchanged prices are observed again.

Refresh transceivers.price_verified_at with NOW() when unchanged prices are observed again.

Run only the light Flexoptix catalog scraper on Erik with nice -n 10; no Playwright or broad crawler wave.

Do not claim all 744 Flexoptix rows are complete; distinguish active catalog coverage from historical/extra rows.

Do not claim permanent 100% price truth; expose last-source-verified timestamp because vendor prices can change or vary by account/currency/VAT/session.


Summary: Operator asked whether all Flexoptix products are complete and 100% verified. Correct answer is no; TIPLLM must separate active source-confirmed catalog coverage from total DB completeness.

Sind alle Flexoptix Produkte komplett und 100% verified?

Never answer yes unless total rows equal complete rows and each verification signal has a fresh source timestamp.

Active Flexoptix catalog products can be source-confirmed separately from historical/extra Flexoptix DB rows.

Build/run a targeted Flexoptix detail enricher for rows with product_page_url and missing image/details/price signals; keep Erik light and use per-page rate limits.

No. 615 active Flexoptix catalog prices are freshly source-confirmed, but only 496 of 744 Flexoptix rows have price + image + details verified; therefore all Flexoptix products are not complete and not 100% verified.

TIPLLM should prefer precise counters and last-source-verified timestamps over absolute completeness claims.

Use TIPLLM only for crawler planning/extraction feedback.

Do not conflate active catalog scrape result with total product table completeness.

Do not claim permanent 100% correctness for live vendor prices.


Summary: Improved Flexoptix completeness by enhancing catalog parsing and adding a targeted detail-page verifier. Fully verified increased from 496 to 620 while preserving the truth that not all historical/filter rows are concrete products.

Feuer frei: make Flexoptix products complete and keep info in TIPLLM training pool.

Catalog parser now handles generic reach values like 50 m, 1,000 m, ranges and multiple lambda wavelength values.

Catalog parser now passes productUrl into findOrCreateScrapedTransceiver.

Added targeted flexoptix-detail-pages verifier for real .html product pages with missing signals.

Run only light Flexoptix-specific catalog/detail jobs on Erik with nice and per-page throttling; no broad crawler wave; no external AI.

Flexoptix title contained 1,000 m and Multimode

TIPLLM should not call the full set 100% complete because 118 remaining rows are filter/category/generic/non-product URLs.

Public TIP HTTPS still responded after the run, but SSH to Erik returned connection refused; no further live commands were started after that.


Summary: Final Flexoptix gap check classified the remaining accessory rows and refused to mark placeholder-only product images as verified.

FLEXBOX rows are products/accessories, not optical reach products; set category Accessory and reach_label N/A when source page is the FLEXBOX page.

Do not mark image_verified when Flexoptix source only exposes placeholder-flexoptix.jpg.

Report 622 of 626 product-like rows with price+image+details, 620 fully_verified, and 118 non-product/filter/generic rows outside complete product verification.

4 rows lack verified images because the source page image is a Flexoptix placeholder.

No placeholder images were accepted as verified.

Use exact counters instead of claiming 100%.


Summary: Ran targeted FS.com detail-page revalidation against existing DB product URLs with missing verification signals. Batch used Playwright concurrency 1 and no category discovery. Details and fully_verified improved significantly.

Now Fiberstore/FS.com; all crawler/scraper/robot work must be written to TIPLLM training pool.

Added FS_DB_DETAIL_ONLY mode to revalidate existing FS.COM product URLs directly without listing/category crawl.

FS scraper now writes productUrl into transceivers.product_page_url.

FS scraper now infers fiber_type from product name, part number, and specs when FS spec table lacks an explicit fiber key.

FS detail source URL is now stored as the real product URL instead of the literal string fs.com.

Run small FS.com Playwright batch on Erik with maxConcurrency=1, maxRequestsPerMinute=10, nice -n 10, and detail cap 80.

74 first try, 3 one retry, 3 two retries

Batch was intentionally capped to 80 and ran concurrency 1 to protect Erik.

FS.com still has many missing fibers/images; continue in small batches or move heavier waves to residential/Proxmox/Pi worker.


Summary: Ran a second targeted FS.com DB-detail-only batch. It stayed stable at Playwright concurrency 1, completed 80 requests with 0 final failures, and materially improved product detail and full verification counters.

Finish TIP today; FS.com/Fiberstore prices, images and product information should be researched deeply enough to avoid manual validation.

Continue with capped DB-detail-only batches because batch 1 was productive. Keep Erik safe with maxConcurrency=1, nice -n 10, no category discovery, and small batch caps.

Allow Crawlee retries for transient FS.com network changes; do not raise concurrency to compensate.

59 first try, 14 one retry, 5 two retries, 2 three retries

One target page returned no useful text; transient ERR_NETWORK_CHANGED retries were reclaimed and completed without final failure.

Erik stayed stable; crawler stats showed no memory, CPU or event-loop overload.

Next best action is another small DB-detail-only batch for remaining HTML product-like rows, then handle no-url rows separately by source discovery/classification.


Summary: Ran a third targeted FS.com DB-detail-only batch. It completed 90 requests with 0 final failures, added fresh price and stock observations, and moved most remaining HTML product URLs into verified detail coverage.

Finish TIP today with perfect transceiver, competitor and switch database; continue FS.com/Fiberstore verification safely.

Use another capped DB-detail-only batch because remaining product URLs still produced verified evidence. Increase cap from 80 to 90 but keep Playwright concurrency 1, nice -n 10 and no category discovery.

Do not mark pages with no useful text as details verified. Record no-text cases for retry/source-review instead.

70 first try, 13 one retry, 5 two retries, 2 three retries

One FS.com page returned no useful text and was not counted as scraped.

No external AI was used for TIP crawler planning or extraction feedback.

Erik remained stable; TIP health stayed OK after the run.

Next best action is a smaller DB-detail-only closure batch for the remaining FS.com HTML product URLs, then a separate source-discovery task for no-url rows.


Summary: Ran a smaller FS.com closure batch after the productive HTML detail waves. It completed all 42 queued pages cleanly, but details_verified did not increase, showing that the DB-detail-only approach is now exhausted for the remaining gaps.

Finish FS.com/Fiberstore as far as possible without manual validation and keep all robot experience in TIPLLM training pool.

Run one smaller closure batch because only 42 eligible DB product URLs remained. Keep concurrency 1, nice -n 10, no category discovery.

If a clean closure batch produces no details_verified movement, stop repeating the same Playwright detail-only job and switch to source-discovery/classification or parser work for the remaining gaps.

Erik remained healthy after the closure batch.

Do not claim FS.com is complete: 258 of 299 HTML product-like rows are complete; 76 no-url rows need source discovery; 4 category rows need classification.


Summary: Added and ran FS.com URL-discovery mode for historical FS-<id> rows without product URLs, then reran DB-detail reconciliation with H1-derived detail evidence. This converted almost all FS.com no-url rows into source-linked product rows and substantially increased image/detail coverage.

Continue and finish FS.com/Fiberstore; all crawler/scraper/robot work must go to TIPLLM training pool. Operator also asked whether Crawlee repos can help; use that evaluation to improve safe crawler architecture.

Added FS_URL_DISCOVERY_ONLY mode that maps existing FS-<numeric-id> rows without product_page_url to https://www.fs.com/de/products/<id>.html and writes evidence onto the existing DB row instead of creating duplicates.

DB_DETAIL_ONLY rows now carry targetTransceiverId so targeted reconciliation updates the original row.

Image verification is marked for target rows when a current FS.com product image is seen.

Detail verification now accepts deterministic source evidence from H1/part/spec text, not only classical spec tables, when fiber/reach/wavelength/connector can be inferred.

Run URL discovery in safe bounded batches on Erik with Playwright concurrency 1, nice -n 10, no category crawl, and post-run DB measurement.

Erik remained healthy; Crawlee AutoscaledPool stayed at concurrency 1 and reported no CPU/memory/event-loop overload.

Do not claim FS.com is complete: 371 of 373 HTML product-like rows are complete, but 2 no-url rows, 4 category rows, and 9 image/fiber gaps remain.


Summary: Installed and bound Crawlee runtime work into TIP. TypeScript Crawlee remains the production core; Crawlee-Python was added as an optional isolated evidence worker for Pi/Proxmox/residential nodes.

Install, use and bind apify/crawlee and crawlee-python for TIP.

Added package scripts for FS.com DB-detail and URL-discovery Crawlee modes.

Added packages/crawlee-python optional worker package.

Added package-local .gitignore so Python build artifacts are not committed.

Production writes remain in the TypeScript TIP scraper. Crawlee-Python writes JSONL evidence only and must not directly mutate TIP DB.

60531b6 feat: add crawlee python worker integration

49f0871 chore: ignore crawlee python build artifacts

Move heavier experiments to Pi/Proxmox/residential workers.


Summary: Revalidated all active approved/auto-approved TIP equivalence matches immediately with deterministic 1:1 DB evidence rules. No crawler wave was started.

Verify and validate everything open in TIP immediately and check whether products truly match 1:1.

recent competitor price evidence
form factor exact
speed exact
fiber type exact
reach ratio >= 0.85
primary wavelength within 15nm

Mark all active matches due immediately and process with existing PgBoss maintenance:re-research-equivalences worker. Keep work DB-only to protect Erik.

Manual equivalence queue is empty and active matches were just rechecked, but not every product row in TIP is fully complete; remaining work is vendor-specific product source enrichment.

No broad browser crawler wave was started.

Continue targeted vendor crawlers or offload heavy discovery to Pi/Proxmox workers.


Summary: Improved vendor verification by making existing scrapers write product URLs, image evidence and detail evidence, then running low-load static/DB-detail passes. No broad browser crawler wave was used.

Continue until everything is finished, but keep Erik safe and write crawler/scraper/robot learnings to TIPLLM training pool.

NADDOD DB_DETAIL_ONLY mode verifies existing DB rows with product_page_url and missing image/details, instead of blind sitemap rotation.

NADDOD extracts og:image, page evidence, AOC/DAC lengths, DR/FR/SR/VR/XDR patterns and writes details to the target row.

GAO Tek writes product_page_url and image evidence.

Ascent Optics writes product_page_url and table image evidence.

Eoptolink writes product_page_url, image, reach/wavelength evidence and avoids over-broad form-factor parsing by preferring title/slug evidence.

Run static/fetch and DB-detail passes with nice -n 10 and existing per-page delays. No Playwright wave on Erik.

NADDOD is much improved but not 100% complete. OEM catalogs without retail prices cannot honestly become fully_verified unless price evidence exists.


Summary: Corrected FS.com 1.6T OSFP family handling after the operator spotted separate 500m DR8 and 2km 2FR4 variants. The 500m DR8 variant maps to Flexoptix O.1316T.C.05.M; the 2km FR4 variant remains a separate FS.com product.

FS.com page clearly has OSFP-DR8-1.6T-FL 500m and OSFP-2FR4-1.6T-FL 2km. Flexoptix O.1316T.C.05.M is the 500m version; FR4 must also be in the DB.

Set FS OSFP-DR8-1.6T-FL to speed 1.6T, reach 500m/500, SMF, wavelength 1310, standard_name 1.6T OSFP DR8.

Set FS OSFP-2FR4-1.6T-FL to speed 1.6T, reach 2km/2000, SMF, wavelength 1310, standard_name 1.6T OSFP 2FR4.

Set Flexoptix O.1316T.C.05.M standard_name 1.6T OSFP DR8.

Approve only O.1316T.C.05.M to OSFP-DR8-1.6T-FL with confidence 0.913; keep 2FR4 separate.

FS.com scraper recognizes 1,6T, 1.6T and 1600G as 1.6T/1600.

FS.com scraper converts reach labels such as 2km into reach_meters=2000.

FS.com scraper updates stale speed labels when numeric source speed matches the row.

O.1316T.C.05.M <-> OSFP-DR8-1.6T-FL approved; no FR4-to-500m collapse

pnpm -C packages/scraper build passed on Erik

Variant selectors that change reach/protocol/model are separate products. A 500m DR8 product must never be matched to a 2km 2FR4 product.

Only DB correction and scraper parser hardening were done.


Summary: Fixed false comparable products for FS.com QDD-2FR4-800G. The dashboard had shown a Flexoptix breakout AOC and a NADDOD 500m product as comparable to a 2km SMF FR4 transceiver because the API treated unknown reach_meters as a wildcard.

Flexoptix DQ.2A858HG.z is wrong because it is a breakout. QDD-2FR4-800G is 800G QSFP-DD 2km SMF; NADDOD row shown was 500m, also not 1:1.

Set FS.COM QDD-2FR4-800G reach_meters to 2000.

Set FS.COM QDD-2FR4-800G wavelengths to 1310 and standard_name to 800G QSFP-DD 2FR4.

Comparable products now require known reach on both sides and reach ratio >= 0.85.

Comparable products now require matching known fiber type.

Comparable products now require known primary wavelength on both sides within 15nm.

Breakout/AOC/DAC/cable products can only compare to other breakout/AOC/DAC/cable products.

QSFP-DD and QSFP-DD800 are treated as one 800G form-factor family.

Build and restart API only; no crawler wave.

pnpm -C packages/api build passed on Erik; pm2 restart tip-api completed; public health healthy

Unknown reach/fiber/wavelength must never act as wildcard in final product comparisons. Breakout AOC products must not be shown as equivalent to pluggable FR4/DR optics.

No external AI was used.
No crawler wave was started.
API-only correction kept Erik stable.


Summary: Ran a strict DB-only sweep over active approved/auto-approved equivalence matches after an operator-spotted false comparable. Rejected 16 remaining active false positives and backfilled numeric reach evidence so unknown reach can no longer mask mismatches.

Operator spotted false comparable products in the dashboard; follow-up sweep searched for similar active risks.

breakout/AOC/DAC/cable class must match unless both sides are non-cable optics

known reach must be close enough and numeric reach_meters should be populated from source labels where deterministic

known primary wavelengths must be within 15nm

unknown reach/fiber/wavelength must not act as final approval wildcard

DB-only correction and measurement on Erik; no browser crawler wave; no external AI.

Active equivalence matches have zero known hard 1:1 mismatches by DB evidence after the sweep, but product-level vendor enrichment is still ongoing and must not be represented as 100% complete.

No external AI was used.
No crawler wave was started.
Erik stayed protected by DB-only work.


Summary: Backfilled 187 missing highspeed wavelength fields from existing deterministic DB evidence without a crawler wave. Rules required explicit nm text or a known optical family code plus matching fiber class.

MMF with SR/SR4/SR8/SRBD/VR/ESR/CSR family => 850

Do not fill ambiguous rows; do not use unknown fiber class for inference; do not mark full source verification from this alone.

Single DB-only UPDATE on Erik; no browser crawler; no external AI.

This is technical evidence enrichment, not a complete vendor-source verification claim. Remaining gaps need vendor-specific parser improvements or targeted crawls.

No external AI was used.
No crawler wave was started.
Erik stayed healthy.


Summary: Hardened ATGBICS wavelength detection and ran a low-load Shopify products.json pass. The run confirmed prices/images but did not reduce ATGBICS technical gaps; a separate DB truth correction set Copper/DAC wavelength semantics to N/A for 1044 rows.

ATGBICS detects N/A wavelength for Copper/DAC/Twinax/Base-T/RJ45.

ATGBICS detects SR-family as 850 and DR/FR/LR/ER/PSM-family as 1310 when explicit protocol code is present.

Run one ATGBICS Shopify products.json pass with nice -n 10; no Playwright/browser; stop if health degrades.

Copper/DAC products do not have optical wavelengths and should use N/A instead of being counted as unresolved optical wavelength gaps.

pnpm -C packages/scraper build passed on active /opt/tip

counters unchanged for technical completeness

Do targeted ATGBICS parser/classifier work for ZR, DCO, C-band, LAN-WDM, CR8, breakout and OSFP/QSFP-DD cable form-factor correction instead of repeating broad JSON runs.

Erik stayed healthy although SSH briefly refused connections twice; public health stayed green.


Summary: Filled deterministic Copper/DAC/Twinax cable lengths, marked source-backed cable details, corrected ATGBICS OSFP cable form factors, and updated comparable-product API logic so Copper/DAC products can compare with wavelengths=N/A while optical products still require numeric wavelength evidence.

Only write cable reach when length is deterministic from part_number or product_page_url.

Use wavelengths=N/A for Copper/DAC/Twinax/CU products.

Mark details verified only when product_page_url exists and core technical fields are present.

Correct ATGBICS OSFP cable rows that were parsed as SFP.

Comparable API may compare Copper/DAC/CU with N/A wavelengths, but optical comparisons still require numeric wavelength match.

DB-only update plus small API/scraper code deploy; no crawler wave; no external AI.

Copper/DAC/Twinax products are complete only when their cable length and endpoint/form-factor evidence are present; do not invent optical wavelengths for them.

Erik public health stayed healthy; SSH intermittently refused connections and work paused during those windows.


Summary: Fixed QSFPTEK parser so product URLs and generic cable lengths are preserved, then backfilled 28 deterministic cable/AOC rows with source-backed details. Eight additional rows became fully verified.

Pass productUrl to findOrCreateScrapedTransceiver.

Parse generic m/km reach including leading cable lengths.

Classify MFS/AOC/active fiber as AOC Cable.

Classify MCP/DAC/Copper/Twinax as Cable.

Add safe protocol-family wavelength parsing for future QSFPTEK runs.

DB-only backfill for existing rows plus scraper source patch; no broad crawler run; no external AI.

Only source-backed rows with deterministic length were marked details verified; remaining QSFPTEK rows need source parsing for fiber/reach and should not be guessed.

SSH intermittently refused connections, so remote actions were paused during blocked windows.


Summary: Classified 18 remaining NADDOD detail-gap rows as switch/network infrastructure or NIC/adapter products based on source/title evidence instead of pretending they were optical transceivers.

Switch/Quantum/Spectrum/ONIE/ports source-title evidence => Switch / Network Infrastructure.

Adapter/ConnectX source-title evidence => NIC / Adapter.

Use allowed data_confidence=scraped_unverified and notes to preserve the non-transceiver classification.

Mark details verified only when a source product URL exists.

Do not use these rows as optical transceiver equivalence evidence.

DB-only classification; no crawler wave; no external AI.

NADDOD switches/NICs/infrastructure can be source/detail verified, but they are not pluggable optical transceiver equivalents and should be handled in a separate product class later.

SSH intermittently refused connections; public health stayed green.


Summary: Backfilled 96 ATGBICS Cable/AOC near-complete rows using deterministic length evidence from product URL/part text. Promoted 109 additional rows to fully_verified.

Use deterministic length from URL or part text only.

Classify breakout/copper/dac/twinax/base-t/rj45/aoc/active-optical rows as cable classes.

Use wavelengths=N/A for Copper/DAC/Twinax.

Mark details verified only when source URL and deterministic cable length are present.

Leave coherent/ZR/DCO/C-band rows for targeted source-specific parser.

DB-only update; no crawler wave; no external AI.

ATGBICS broad JSON refresh is now low-yield for remaining gaps; remaining work requires targeted optical/coherent parser logic rather than repeated catalog refreshes.


Summary: Backfilled 33 FiberMall near-complete optical rows using deterministic reach/fiber/wavelength evidence from product title and URL. Promoted 33 additional rows to fully_verified.

Infer fiber type from SMF/MMF/source-title evidence only when missing.

Use explicit nm or safe protocol-family evidence for wavelength when present.

Do not complete rows whose part number is only a brand name unless source title/URL provides deterministic reach.

FiberMall remaining gaps require stronger source parsing; brand-name-only rows must not be blindly marked complete.


Summary: Hardened ShopFiber24 reach and speed parsing so variable-length cable families are not falsely detail-verified and 800G/QSFP-DD800 text is not normalized as 400G.

variable cable ranges like 1 - 30 m
800G or QSFP-DD800 product text

Reject variable reach ranges such as 1 - 30 m, 1 to 30 m, and 1 bis 30 m for detail verification.

Parse explicit single m/km values as deterministic reach.

Normalize 800G/QSFP-DD800 as 800G/800Gbps rather than 400G.

Local parser patch plus light rsync/build; no crawler wave; no external AI.

ShopFiber24 variable cable-family rows require variant-level extraction; do not approve them as one fixed reach product.

Erik stayed healthy after the small build.


Summary: Hardened ATGBICS parser so unknown fiber type no longer defaults to SMF and variable reach ranges are not treated as deterministic reach evidence.

unknown fiber text defaulting to SMF
variable reach ranges like 1 - 30 m

Reject variable reach ranges such as 1 - 30 m before generic reach parsing.

Only return SMF from explicit single-mode or protocol-family evidence.

Return empty fiber type when evidence is missing so details verification cannot pass by default.

ATGBICS remaining rows need targeted source/protocol evidence; default fiber assumptions must not promote detail verification.

TIP public health stayed healthy after rsync/build.


Summary: Backfilled 9 ShopFiber24 rows from deterministic product-code evidence while skipping variable cable-family rows. Promoted 9 additional rows to fully_verified.

BX60/BX-D-60/BX-U-60 means 60km SMF with 1270/1330 BiDi wavelength evidence.

T-80 means 80m Copper with N/A wavelength.

Do not mark XM/CXM/CUXM/CXX/AOC/DAC family rows as fixed reach variants.

Remaining ShopFiber24 gaps need variant-level extraction or direct source parsing; variable cable families are not complete products until the exact configured length is known.

No external AI was used.
No browser crawler was started.
Erik public health stayed healthy.


Summary: Backfilled 12 FiberMall rows from protocol evidence in product URL slugs. Promoted 12 additional rows to fully_verified.

Use URL protocol slugs such as LRM, LR4, 2FR4, LR8, SR4, ZR, SFP28-LR only when they directly encode form factor/speed/reach/fiber/wavelength.

Skip brand-name-only rows without protocol/reach evidence.

Correct form factor and speed when URL evidence contradicts stale parser defaults.

Remaining FiberMall rows need stronger product-page parsing; brand/OEM-code-only URL rows must not be auto-approved.


Summary: Backfilled 32 near-complete rows from explicit standard/title/URL evidence across GBICS, QSFPTEK and Fluxlight. All three vendor near-complete queues reached zero.

Use explicit nm/m/km evidence where present.

Use well-defined protocol codes only when paired with vendor/source URL evidence.

Correct stale parser defaults only when part number or URL encodes form factor and speed.

Do not broaden this logic to ambiguous OEM-code rows.

This was an evidence pass, not a guess pass; only explicit standard/title/URL evidence was accepted.


Summary: Closed NADDOD and FS.COM near-complete detail queues: classified three NADDOD rows as adapter/converter products and corrected FS SKU 110529 to QDD-LR4-400G 400GBASE-LR4 QSFP-DD evidence.

NADDOD product pages/products search snippets identify 100GBASE-S25, 40GBASE-S10, and MAM1Q00A-QSA28-S as QSFP/SFP adapter converter modules.

Official FS source for SKU 110529 identifies QDD-LR4-400G, 400GBASE-LR4 QSFP-DD, SMF, 10km, CWDM4 1271/1291/1311/1331nm, Duplex LC.

Adapter/converter products get Adapter / Converter class and N/A optical reach/fiber/wavelength semantics.

Do not use adapter/converter rows as optical equivalence evidence.

FS SKU 110529 should be normalized to QDD-LR4-400G instead of opaque FS-110529.

DB-only update after source lookup; no crawler wave; no external AI.

Adapter/converter rows are product records but not optical transceiver equivalents; FS SKU 110529 is LR4, not a generic opaque product.

FS direct page body was WAF-challenged, so official indexed FS source evidence was used instead.


Summary: Backfilled 346 ATGBICS rows from explicit product URL evidence for distance, media and wavelength. Promoted 346 additional rows to fully_verified.

m/km distance
smf/mmf/copper/dac/base-t/rj45 media
nm wavelength where optical

Only accept rows where product URL contains explicit distance and media evidence.

Extract reach from m/km URL token, not from unrelated product-number digits.

Extract wavelength from nm URL token when optical; use N/A for copper/dac/base-t/rj45.

Correct form factor and speed only from clear protocol terms in the URL.

Remaining ATGBICS rows need product-page parsing or special handling because they do not expose simple m/km plus media URL evidence.


Summary: Backfilled 32 ATGBICS special-case rows using deterministic protocol/product-class rules. Promoted 32 additional rows to fully_verified.

loopback
10GBASE-T/RJ45
LRM
BX60/BXD-60/BXU-60
CWDM 10G 60km
CSR

Loopback/test modules are non-optical test products with N/A reach/fiber/wavelength semantics.

10GBASE-T/RJ45 SFP+ uses 30m Copper with N/A wavelength.

BX60 uses 60km SMF with directional BiDi wavelength evidence.

CWDM 10G 60 uses 60km SMF and source wavelength.

Remaining ATGBICS rows need detail-page extraction because the URL slug no longer carries enough reach evidence.


Summary: Added and ran a lightweight Shopify product.js verifier for ATGBICS near-complete rows. Closed the ATGBICS near-complete detail queue.

one product.js JSON endpoint per product page

Shopify tags such as Max Data Rate, Max Distance, Cable Type, Wavelength, Interface, Product Category

Prefer structured Shopify tags but fall back to title/body when a tag is unparseable or says N/A.

Never accept distance without media evidence.

Loopback/test products use N/A reach/fiber/wavelength semantics.

Do not use external AI; parser rules only.

Max Distance_N/A tags can hide real reach in product title/description; parser must use parsed tag value, not tag presence, as the gate.

Lightweight source fetch; no browser crawler; paced requests.

ATGBICS product pages are accepted as source evidence only when detail fields can be parsed from tags/title/body; unparseable rows remain skipped until parser evidence is improved.

No Playwright/browser crawler was started.

SSH refused intermittently; retries were paused to protect Erik.


Summary: Added and ran a lightweight static detail verifier for the remaining ShopFiber24 and FiberMall near-complete rows. Closed the global near-complete queue.

FiberMall Schema.org Product JSON-LD name/description/mpn

ShopFiber24 title/meta description/OG metadata

source URL and existing DB price/image/competitor evidence

FiberMall JSON-LD Product blocks are primary source evidence for name, MPN, media, speed, reach, wavelength, connector and image provenance.

ShopFiber24 static title/meta text is accepted when it contains deterministic protocol/reach/media evidence.

Variable AOC/DAC/category pages must be classified as product families with Variant reach, not a fake fixed meter value.

Switches, media converters, muxes and adapters must be classified as their product class, not as optical equivalents.

100G DWDM DCO rows without a normal reach should be classified as Coherent DWDM with line-system-dependent reach.

10GBASE-T copper SFP+ rows use RJ45 Copper 30m standard semantics when source identifies 10G Base-T copper but omits distance.

Lightweight source fetch; no browser crawler; no external AI.

Closing a queue does not mean inventing optics. Families/accessories/converters are verified as the product they actually are, and should not be used as 1:1 optical competitor equivalents unless a separate equivalence rule allows it.

SSH refused intermittently; retries were delayed.


Summary: A concurrent price-verification process exposed 23 new ATGBICS AOC near-complete rows after the first closure. Re-ran the ATGBICS product.js verifier and returned the global near-complete queue to zero.

price_verified increased from 11557 to 11582 after the first queue closure

Use the already-deployed ATGBICS product.js verifier for newly exposed rows.

AOC product URLs/titles with explicit m length, MMF and 850nm are deterministic source evidence.

Pause between SSH retries when Erik refuses connections.

Queue closure must be rechecked after concurrent crawler/price jobs because newly price-verified rows can enter the near-complete set after a previous zero state.