research(optixtrans): the public document graph is exhausted, and no client-board chapter is in it (#807) #1843

Merged
jaylouisw merged 1 commit from catalogue/1117-1225 into main 2026-11-17 12:37:42 +00:00
Owner

Refs #807, #808, #810

Does not close: the missing field is still a client-port board's own Front Panel / Port Specifications.

What was tested this pass

  • Crawled the e.huawei.com/en/documents/others/<32-hex> material-page graph breadth-first from the fourteen hashes already on the thread. It drains in 52 documents; the frontier is empty, so the listing in §5.1 is the whole public set. The only board chapters in it are TNG2DAP, TNG2SRAPXF, TNG3SRAPXF - all OA (amplifier) boards. TNG1N*, TNG1T*, TNG1M*, TNV*: zero.
  • Fetched TNG3SRAPXF in full (200, application/pdf, 1,228,914 B, 50 pp) and read §1.3 Mappings and Substitution: it pairs only OA/CXP parts. Text hits for TNG1N/TNG1T/TNG1M/TNV: 0/0/0/0.
  • Closed two routes so no later pass repeats them: e.huawei.com site search (/en/search, /en/search-result, /en/searchcenter/search, /en/documents) returns one 336 KB client-rendered shell with 0 occurrences of the query; info.support.huawei.com hedex paths all return the same 91,294 B Vue shell, and Info-Finder Hardware Center is a 5,804 B shell whose bundle uses baseURL:"/info-finder" plus an X-Csrf-Token cookie (browser UA: 403).
  • Checked ENISA EUCC-3089-2026-004 (544,246 B, 25 pp, text layer): names the E9600 series and its doc packages, but 0 x TNG, 0 x board - it certifies software, not boards.

Consequence: this note's own closing claim - one search hit per board would convert #807/#808/#810 - is falsified. The remaining routes are a stated board configuration from the requester, or a support/partner login for EDOC1100163901.

Gates: scripts/syntax-check.js 385 files OK; scripts/audit-port-types.js no contradiction; test/hardware-invariants.test.js 26 passed, 0 failed. Docs-only, no generated file touched.

Refs #807, #808, #810 Does not close: the missing field is still a client-port board's own Front Panel / Port Specifications. **What was tested this pass** - Crawled the `e.huawei.com/en/documents/others/<32-hex>` material-page graph breadth-first from the fourteen hashes already on the thread. It drains in **52 documents**; the frontier is empty, so the listing in §5.1 is the whole public set. The only board chapters in it are **TNG2DAP, TNG2SRAPXF, TNG3SRAPXF** - all OA (amplifier) boards. `TNG1N*`, `TNG1T*`, `TNG1M*`, `TNV*`: zero. - Fetched `TNG3SRAPXF` in full (200, application/pdf, 1,228,914 B, 50 pp) and read §1.3 Mappings and Substitution: it pairs only OA/CXP parts. Text hits for `TNG1N`/`TNG1T`/`TNG1M`/`TNV`: 0/0/0/0. - Closed two routes so no later pass repeats them: `e.huawei.com` site search (`/en/search`, `/en/search-result`, `/en/searchcenter/search`, `/en/documents`) returns one 336 KB client-rendered shell with 0 occurrences of the query; `info.support.huawei.com` hedex paths all return the same 91,294 B Vue shell, and Info-Finder Hardware Center is a 5,804 B shell whose bundle uses `baseURL:"/info-finder"` plus an `X-Csrf-Token` cookie (browser UA: 403). - Checked ENISA EUCC-3089-2026-004 (544,246 B, 25 pp, text layer): names the E9600 series and its doc packages, but **0 x `TNG`, 0 x `board`** - it certifies software, not boards. **Consequence:** this note's own closing claim - one search hit per board would convert #807/#808/#810 - is falsified. The remaining routes are a stated board configuration from the requester, or a support/partner login for `EDOC1100163901`. Gates: `scripts/syntax-check.js` 385 files OK; `scripts/audit-port-types.js` no contradiction; `test/hardware-invariants.test.js` 26 passed, 0 failed. Docs-only, no generated file touched.
research(optixtrans): the public document graph is exhausted, and no client-board chapter is in it (#807)
All checks were successful
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
CI / Server smoke test (pull_request) Successful in 11s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 50s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Arm auto-merge (pull_request) Successful in 5s
5d4179582b
Crawled the e.huawei.com material-page graph breadth-first from the hashes already
on the thread: 52 documents, frontier empty. Three board chapters exist (TNG2DAP,
TNG2SRAPXF, TNG3SRAPXF), all OA boards; zero TNG1N/TNG1T/TNG1M/TNV chapters.

Also fetched TNG3SRAPXF in full (1,228,914 B, 50 pp) and confirmed its substitution
table names only OA/CXP parts, closed the site-search and Info-Finder/hedex routes
for the next pass, and checked the ENISA EUCC-3089 report as a second source (0 x TNG).

Corrects this note's own closing claim that one search hit per board would close the
three issues.
jaylouisw force-pushed catalogue/1117-1225 from 5d4179582b
All checks were successful
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
CI / Server smoke test (pull_request) Successful in 11s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 50s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Arm auto-merge (pull_request) Successful in 5s
to 49b37a752a
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 11s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 18) (pull_request) Successful in 1m2s
CI / Test (Node 20) (pull_request) Successful in 58s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Arm auto-merge (pull_request) Successful in 8s
2026-11-17 12:33:33 +00:00
Compare
jaylouisw force-pushed catalogue/1117-1225 from 49b37a752a
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 11s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 18) (pull_request) Successful in 1m2s
CI / Test (Node 20) (pull_request) Successful in 58s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Arm auto-merge (pull_request) Successful in 8s
to ae85e70155
All checks were successful
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 49s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Arm auto-merge (pull_request) Successful in 15s
2026-11-17 12:34:44 +00:00
Compare
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1843
No description provided.