catalogue: Huawei OptiXtrans E6608T — 7x TMB1LDCD terminal shelf (28x 100GE client, 14x 200G line) #1739

Merged
jaylouisw merged 2 commits from catalogue/1116-2155 into main 2026-11-17 06:19:02 +00:00
Owner

Fixes #804

Adds devices/huawei/optixtrans-e6608t.json — OptiXtrans E6608T (7x TMB1LDCD, DC chassis): 28x 100GE QSFP28 client + 14x CFP2 200G line.

Evidence

  • Family spec table (vendor page): E6608T service slots DC 7 / AC 5, cross-connect capacity NA, 96 DWDM channels, 1-to-9-degree ROADM, max single-channel rate 400 Gbit/s — https://e.huawei.com/en/products/optical-transmission/optiXtrans-e6600
  • E6608T datasheet (viewer; PDF downloadable): 2U, 88.1 x 442 x 220 mm, "DC-powered chassis: 6 (two system control boards) or 7 (single system control board)", pluggables SFP/eSFP, XFP, SFP+, QSFP+, QSFP28, CFP, CFP2, line rate 2.5/10/100/200/400 Gbit/s, OTN-only — https://e.huawei.com/en/documents/others/a80f5e49b6d74beaa368b57673bc4c85
  • Slot arithmetic: 7 service boards + 1 system control board = the 8-slot DC backplane; 2 SCC boards give 6+2. The AC chassis (5/4) is a different box and is not modelled here.
  • Board cage map: TMB1LDCD is 4x 100GE client (QSFP28, LR4/SR4/CLR4 or OTU4) into 2x programmable 100G/200G line (CFP2, 50 GHz) — Huawei HCIP-Transmission V2.5 material, B1LDCD slide. Same board and stated-configuration convention as optixtrans-e6608.json (6x) and optixtrans-e6616.json (14x).

What the request got wrong, corrected here

The T is not an E6608 with a smaller name: it is "OTN equipment supporting only OTN services" with no cross-connect (Huawei's summary: "7 slot @ 2U, Ponder + Optical"). So capabilities is cli only, there is no OTN/PKT/SDH unified switching, and the entry carries no fabric block — the seven boards are independent transponders that cannot groom between each other.

Gates

  • node scripts/syntax-check.js — 364 files, all OK
  • node scripts/audit-port-types.js — "No port contradicts its declared type"
  • node test/hardware-invariants.test.js — 26 passed, 0 failed (2332/2332 distinct keys)
  • node scripts/check-control-bytes.js — clean
  • docs/DEVICE_REGISTRY.md regenerated (never hand-edited): 2,332 models, 28,500 sockets, 951 port shapes
Fixes #804 Adds `devices/huawei/optixtrans-e6608t.json` — **OptiXtrans E6608T (7x TMB1LDCD, DC chassis)**: 28x 100GE QSFP28 client + 14x CFP2 200G line. ### Evidence - Family spec table (vendor page): E6608T service slots **DC 7 / AC 5**, cross-connect capacity **NA**, 96 DWDM channels, 1-to-9-degree ROADM, max single-channel rate 400 Gbit/s — https://e.huawei.com/en/products/optical-transmission/optiXtrans-e6600 - E6608T datasheet (viewer; PDF downloadable): 2U, 88.1 x 442 x 220 mm, "DC-powered chassis: 6 (two system control boards) or 7 (single system control board)", pluggables SFP/eSFP, XFP, SFP+, QSFP+, **QSFP28, CFP, CFP2**, line rate 2.5/10/100/200/400 Gbit/s, OTN-only — https://e.huawei.com/en/documents/others/a80f5e49b6d74beaa368b57673bc4c85 - Slot arithmetic: 7 service boards + 1 system control board = the 8-slot DC backplane; 2 SCC boards give 6+2. The AC chassis (5/4) is a different box and is not modelled here. - Board cage map: TMB1LDCD is 4x 100GE client (QSFP28, LR4/SR4/CLR4 or OTU4) into 2x programmable 100G/200G line (CFP2, 50 GHz) — Huawei HCIP-Transmission V2.5 material, B1LDCD slide. Same board and stated-configuration convention as `optixtrans-e6608.json` (6x) and `optixtrans-e6616.json` (14x). ### What the request got wrong, corrected here The T is **not** an E6608 with a smaller name: it is "OTN equipment supporting only OTN services" with no cross-connect (Huawei's summary: "7 slot @ 2U, Ponder + Optical"). So `capabilities` is `cli` only, there is no OTN/PKT/SDH unified switching, and the entry carries **no `fabric` block** — the seven boards are independent transponders that cannot groom between each other. ### Gates - `node scripts/syntax-check.js` — 364 files, all OK - `node scripts/audit-port-types.js` — "No port contradicts its declared type" - `node test/hardware-invariants.test.js` — 26 passed, 0 failed (2332/2332 distinct keys) - `node scripts/check-control-bytes.js` — clean - `docs/DEVICE_REGISTRY.md` regenerated (never hand-edited): 2,332 models, 28,500 sockets, 951 port shapes
catalogue: Huawei OptiXtrans E6608T — 7x TMB1LDCD terminal shelf, no cross-connect (#804)
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Failing after 54s
CI / Test (Node 18) (pull_request) Failing after 58s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 22) (pull_request) Failing after 1m0s
CI / Arm auto-merge (pull_request) Successful in 4s
9dde979882
OTN-only 2U shelf, DC chassis with one system control board (7 service
slots; 6 with two SCC, AC 5/4), filled with 7x TMB1LDCD transponders:
28x 100GE QSFP28 client, 14x CFP2 200G line. The T has no cross-connect
(family table: cross-connect capacity NA), so capabilities stays cli and
there is no fabric block - unlike optixtrans-e6608.json.
Author
Owner

This branch conflicts with main, so it was not rebased:

README.md devices/huawei/optixtrans-e6608t.json docs/CONNECTORS.md docs/DEVICE_REGISTRY.md docs/wiki/Home.md scripts/build-wiki.js 

A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.

This branch conflicts with `main`, so it was not rebased: ``` README.md devices/huawei/optixtrans-e6608t.json docs/CONNECTORS.md docs/DEVICE_REGISTRY.md docs/wiki/Home.md scripts/build-wiki.js ``` A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.
Author
Owner

Surgery run 2026-11-16 22:08 — this PR is red for one reason: three hard-coded counts in test/ now see a third TMB1LDCD shelf.

Local run of the head 9dde979 (detached, node scripts/run-tests.js --concurrency=8): 293 suites, 10,395 assertions, 3 failed, audit-port-types clean, duplicate-models 21/21. The three failures are all the same cause — this PR adds OptiXtrans E6608T (7x TMB1LDCD, DC chassis) with alias TMB1LDCD, so a B1LDCD query legitimately returns 3 shelves (E6608, E6616, E6608T) where the suites assert 2. The same two suites on origin/main (4e14afe) are green (13/13, 19/19), so it is this PR's content, not main.

Which lines (all mechanical count/ranking updates, no behaviour question):

  1. test/device-aliases.test.js:95
    ok(board.length === 2, 'B1LDCD finds both shelves that take the board', String(board.length));
    → actual 3; expectation needs to be 3 (or >= 2).
  2. test/device-aliases.test.js:99
    const multi = filterDevices('b1ldcd 14x', specs, {});
    ok(multi.length >= 1 && /E6616/.test(multi[0].model), ...)
    → multi[0].model is now OptiXtrans E6608T (7x TMB1LDCD, DC chassis) (its label carries "14x 200G line"), so the ranking assertion no longer holds — the new shelf outranks E6616 for b1ldcd 14x.
  3. test/palette-search-keys.test.js:96
    ok(warm[7].length === 2, 'the B1LDCD alias still finds both shelves', String(warm[7].length));
    → actual 3; expectation needs to be 3.

Why I have not fixed it: test/ is outside the surgery loop's remit — I may only regenerate generated docs and resolve mechanical merge conflicts, never author source or test changes. This needs the owning loop (or Jay) to land the three updated expectations on this branch; after that the PR is ready and the armed auto-merge will take it. Nothing else in the diff is at fault — the catalogue data, README/docs count regeneration and scripts/build-wiki.js all regenerate cleanly, and the PR is 2 commits behind 4e14afe with no conflict.

— surgery watchdog

**Surgery run 2026-11-16 22:08 — this PR is red for one reason: three hard-coded counts in `test/` now see a third TMB1LDCD shelf.** Local run of the head `9dde979` (detached, `node scripts/run-tests.js --concurrency=8`): **293 suites, 10,395 assertions, 3 failed**, `audit-port-types` clean, `duplicate-models` 21/21. The three failures are all the same cause — this PR adds `OptiXtrans E6608T (7x TMB1LDCD, DC chassis)` with alias `TMB1LDCD`, so a `B1LDCD` query legitimately returns **3** shelves (E6608, E6616, E6608T) where the suites assert **2**. The same two suites on `origin/main` (`4e14afe`) are green (13/13, 19/19), so it is this PR's content, not main. Which lines (all mechanical count/ranking updates, no behaviour question): 1. `test/device-aliases.test.js:95` `ok(board.length === 2, 'B1LDCD finds both shelves that take the board', String(board.length));` → actual `3`; expectation needs to be 3 (or `>= 2`). 2. `test/device-aliases.test.js:99` `const multi = filterDevices('b1ldcd 14x', specs, {});` `ok(multi.length >= 1 && /E6616/.test(multi[0].model), ...)` → `multi[0].model` is now `OptiXtrans E6608T (7x TMB1LDCD, DC chassis)` (its label carries "14x 200G line"), so the ranking assertion no longer holds — the new shelf outranks E6616 for `b1ldcd 14x`. 3. `test/palette-search-keys.test.js:96` `ok(warm[7].length === 2, 'the B1LDCD alias still finds both shelves', String(warm[7].length));` → actual `3`; expectation needs to be 3. **Why I have not fixed it:** `test/` is outside the surgery loop's remit — I may only regenerate generated docs and resolve mechanical merge conflicts, never author source or test changes. This needs the owning loop (or Jay) to land the three updated expectations on this branch; after that the PR is ready and the armed auto-merge will take it. Nothing else in the diff is at fault — the catalogue data, `README`/`docs` count regeneration and `scripts/build-wiki.js` all regenerate cleanly, and the PR is 2 commits behind `4e14afe` with no conflict. — surgery watchdog
Author
Owner

Surgery run 22:23 — two new facts, still needs Jay's decision, deliberately not rebased.

  1. Main moved twice since the diagnosis (326ea7fc #1740, 473d4c96 #1741), so the branch is now 4 behind / 1 ahead. The conflict surface has widened from what pr-rebase reported at 22:03: git merge-tree origin/main 9dde9798 now conflicts in 5 files — README.md, docs/CONNECTORS.md, docs/DEVICE_REGISTRY.md, docs/wiki/Home.md, scripts/build-wiki.js. Three of those are generated (DEVICE_REGISTRY.md, wiki/Home.md come from scripts/build-wiki.js), so they are regenerable — but regenerating them cannot turn this PR green.

  2. test/device-aliases.test.js:95 and :99 and test/palette-search-keys.test.js:96 are byte-identical on origin/main to what was reported: board.length === 2, warm[7].length === 2, /E6616/. The blocker is unchanged.

Rebasing was skipped on purpose: catalogue/1116-2155 is checked out in the live pf-wt/firmware worktree, so a force-push from here would desync a running loop for zero benefit — a clean rebase still fails those 3 assertions. The one decision needed is still: who lands the 3-line count bump in test/ (293 suites / 10,395 assertions / 3 failed is the expected-total arithmetic).

**Surgery run 22:23 — two new facts, still needs Jay's decision, deliberately not rebased.** 1. Main moved twice since the diagnosis (`326ea7fc` #1740, `473d4c96` #1741), so the branch is now 4 behind / 1 ahead. The conflict surface has widened from what `pr-rebase` reported at 22:03: `git merge-tree origin/main 9dde9798` now conflicts in **5** files — `README.md`, `docs/CONNECTORS.md`, `docs/DEVICE_REGISTRY.md`, `docs/wiki/Home.md`, `scripts/build-wiki.js`. Three of those are generated (`DEVICE_REGISTRY.md`, `wiki/Home.md` come from `scripts/build-wiki.js`), so they are regenerable — but regenerating them cannot turn this PR green. 2. `test/device-aliases.test.js:95` and `:99` and `test/palette-search-keys.test.js:96` are byte-identical on `origin/main` to what was reported: `board.length === 2`, `warm[7].length === 2`, `/E6616/`. The blocker is unchanged. Rebasing was skipped on purpose: `catalogue/1116-2155` is checked out in the live `pf-wt/firmware` worktree, so a force-push from here would desync a running loop for zero benefit — a clean rebase still fails those 3 assertions. The one decision needed is still: who lands the 3-line count bump in `test/` (293 suites / 10,395 assertions / 3 failed is the expected-total arithmetic).
jaylouisw force-pushed catalogue/1116-2155 from 9dde979882
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Failing after 54s
CI / Test (Node 18) (pull_request) Failing after 58s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 22) (pull_request) Failing after 1m0s
CI / Arm auto-merge (pull_request) Successful in 4s
to 8229c866c8
Some checks failed
CI / Classify the change (pull_request) Successful in 18s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 18s
CI / Test (Node 20) (pull_request) Failing after 53s
CI / Test (Node 18) (pull_request) Failing after 58s
CI / Docker build (pull_request) Successful in 32s
CI / Test (Node 22) (pull_request) Failing after 58s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-16 22:41:37 +00:00
Compare
Author
Owner

Rebased onto 473d4c96 → 8229c866; the git conflict is gone. What is left is three assertions in test/, which are the catalogue owner's, not mine to edit.

Verified after the rebase (git merge-tree origin/main origin/catalogue/1116-2155): 0 conflicts, 0 behind, 1 ahead. The five previously-conflicting files were all count lines, so they were regenerated rather than merged by hand: node scripts/regen-registry-doc.js rewrote README, docs/CONNECTORS.md, docs/DEVICE_REGISTRY.md, docs/wiki/Home.md and scripts/build-wiki.js to 2,340 models / 28,806 sockets / 958 distinct port shapes (main was at 2,339 / 28,764 / 957; the new shelf is +1 model, +42 sockets, +1 shape). test/doc-catalog-counts.test.js passes 43/43 on the rebased tree.

What still fails, and it is not a conflict — the new shelf really is a third B1LDCD shelf, so main's hard-coded 2 is now wrong:

file:line assertion now
test/device-aliases.test.js:95 board.length === 2, "B1LDCD finds both shelves" 3
test/device-aliases.test.js:99 "b1ldcd 14x" → E6616 first E6608T first (it also has 14x 200G line)
test/palette-search-keys.test.js:96 warm[7].length === 2 3

The two counts are a mechanical 2→3. The middle one is a question only the catalogue loop can answer: for b1ldcd 14x, is E6608T now the right first hit (it is a 14x 200G line chassis) with E6616 demoted, or should E6616 keep the top slot? Either answer is a two-line test edit plus the assertion's wording.

Needs the catalogue loop to land that edit on top of 8229c866 (or on main — the count bump is independent of this PR). Until then this PR stays red on Test (Node 18/20/22) for a reason that is not a merge problem. scripts/ and docs/ were regenerated only; no engine or behaviour change was made by me.

**Rebased onto `473d4c96` → `8229c866`; the git conflict is gone. What is left is three assertions in `test/`, which are the catalogue owner's, not mine to edit.** Verified after the rebase (`git merge-tree origin/main origin/catalogue/1116-2155`): **0 conflicts, 0 behind, 1 ahead.** The five previously-conflicting files were all count lines, so they were regenerated rather than merged by hand: `node scripts/regen-registry-doc.js` rewrote README, `docs/CONNECTORS.md`, `docs/DEVICE_REGISTRY.md`, `docs/wiki/Home.md` and `scripts/build-wiki.js` to **2,340 models / 28,806 sockets / 958 distinct port shapes** (main was at 2,339 / 28,764 / 957; the new shelf is +1 model, +42 sockets, +1 shape). `test/doc-catalog-counts.test.js` passes 43/43 on the rebased tree. What still fails, and it is not a conflict — the new shelf really is a third `B1LDCD` shelf, so main's hard-coded 2 is now wrong: | file:line | assertion | now | |---|---|---| | `test/device-aliases.test.js:95` | `board.length === 2`, "B1LDCD finds both shelves" | 3 | | `test/device-aliases.test.js:99` | `"b1ldcd 14x"` → E6616 first | E6608T first (it also has 14x 200G line) | | `test/palette-search-keys.test.js:96` | `warm[7].length === 2` | 3 | The two counts are a mechanical 2→3. The middle one is a question only the catalogue loop can answer: for `b1ldcd 14x`, is E6608T now the *right* first hit (it is a 14x 200G line chassis) with E6616 demoted, or should E6616 keep the top slot? Either answer is a two-line test edit plus the assertion's wording. Needs the catalogue loop to land that edit on top of `8229c866` (or on main — the count bump is independent of this PR). Until then this PR stays red on Test (Node 18/20/22) for a reason that is not a merge problem. `scripts/` and `docs/` were regenerated only; no engine or behaviour change was made by me.
jaylouisw force-pushed catalogue/1116-2155 from 8229c866c8
Some checks failed
CI / Classify the change (pull_request) Successful in 18s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 18s
CI / Test (Node 20) (pull_request) Failing after 53s
CI / Test (Node 18) (pull_request) Failing after 58s
CI / Docker build (pull_request) Successful in 32s
CI / Test (Node 22) (pull_request) Failing after 58s
CI / Arm auto-merge (pull_request) Successful in 3s
to 855c071fd6
Some checks failed
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 15s
CI / Test (Node 20) (pull_request) Failing after 51s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 18) (pull_request) Failing after 58s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Arm auto-merge (pull_request) Successful in 2s
2026-11-16 22:47:54 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 855c071fd6
Some checks failed
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 15s
CI / Test (Node 20) (pull_request) Failing after 51s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 18) (pull_request) Failing after 58s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Arm auto-merge (pull_request) Successful in 2s
to 3fc15a0b6b
Some checks failed
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 15s
CI / Test (Node 20) (pull_request) Failing after 52s
CI / Test (Node 18) (pull_request) Failing after 57s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-16 22:55:44 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 3fc15a0b6b
Some checks failed
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 15s
CI / Test (Node 20) (pull_request) Failing after 52s
CI / Test (Node 18) (pull_request) Failing after 57s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Arm auto-merge (pull_request) Successful in 3s
to aa3586bf24
Some checks failed
CI / Arm auto-merge (pull_request) Blocked by required conditions
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 14s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 20) (pull_request) Failing after 42s
CI / Test (Node 22) (pull_request) Failing after 46s
CI / Test (Node 18) (pull_request) Failing after 10m45s
2026-11-16 23:00:47 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from aa3586bf24
Some checks failed
CI / Arm auto-merge (pull_request) Blocked by required conditions
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 14s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 20) (pull_request) Failing after 42s
CI / Test (Node 22) (pull_request) Failing after 46s
CI / Test (Node 18) (pull_request) Failing after 10m45s
to 404ff1889d
Some checks failed
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 17s
CI / Test (Node 20) (pull_request) Failing after 50s
CI / Test (Node 18) (pull_request) Failing after 57s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 22) (pull_request) Failing after 55s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-16 23:06:35 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 404ff1889d
Some checks failed
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 17s
CI / Test (Node 20) (pull_request) Failing after 50s
CI / Test (Node 18) (pull_request) Failing after 57s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 22) (pull_request) Failing after 55s
CI / Arm auto-merge (pull_request) Successful in 3s
to 91de308772
Some checks failed
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 17s
CI / Test (Node 20) (pull_request) Failing after 50s
CI / Test (Node 18) (pull_request) Failing after 58s
CI / Docker build (pull_request) Successful in 29s
CI / Test (Node 22) (pull_request) Failing after 56s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-16 23:22:46 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 91de308772
Some checks failed
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 17s
CI / Test (Node 20) (pull_request) Failing after 50s
CI / Test (Node 18) (pull_request) Failing after 58s
CI / Docker build (pull_request) Successful in 29s
CI / Test (Node 22) (pull_request) Failing after 56s
CI / Arm auto-merge (pull_request) Successful in 4s
to 83162ef88a
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 17s
CI / Test (Node 20) (pull_request) Failing after 51s
CI / Test (Node 18) (pull_request) Failing after 1m0s
CI / Docker build (pull_request) Successful in 31s
CI / Test (Node 22) (pull_request) Failing after 58s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-16 23:55:39 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 83162ef88a
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 17s
CI / Test (Node 20) (pull_request) Failing after 51s
CI / Test (Node 18) (pull_request) Failing after 1m0s
CI / Docker build (pull_request) Successful in 31s
CI / Test (Node 22) (pull_request) Failing after 58s
CI / Arm auto-merge (pull_request) Successful in 3s
to 0e790aadd8
Some checks failed
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 18s
CI / Docker build (pull_request) Successful in 32s
CI / Test (Node 18) (pull_request) Failing after 1m7s
CI / Test (Node 20) (pull_request) Failing after 1m0s
CI / Test (Node 22) (pull_request) Failing after 1m6s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-17 00:03:09 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 0e790aadd8
Some checks failed
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 18s
CI / Docker build (pull_request) Successful in 32s
CI / Test (Node 18) (pull_request) Failing after 1m7s
CI / Test (Node 20) (pull_request) Failing after 1m0s
CI / Test (Node 22) (pull_request) Failing after 1m6s
CI / Arm auto-merge (pull_request) Successful in 4s
to f614ae87b8
Some checks failed
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
CI / Server smoke test (pull_request) Successful in 15s
CI / Docker build (pull_request) Successful in 29s
CI / Test (Node 20) (pull_request) Failing after 57s
CI / Test (Node 18) (pull_request) Failing after 1m5s
CI / Test (Node 22) (pull_request) Failing after 1m1s
CI / Arm auto-merge (pull_request) Successful in 2s
2026-11-17 00:17:07 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from f614ae87b8
Some checks failed
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
CI / Server smoke test (pull_request) Successful in 15s
CI / Docker build (pull_request) Successful in 29s
CI / Test (Node 20) (pull_request) Failing after 57s
CI / Test (Node 18) (pull_request) Failing after 1m5s
CI / Test (Node 22) (pull_request) Failing after 1m1s
CI / Arm auto-merge (pull_request) Successful in 2s
to 9615f066c0
Some checks failed
CI / Classify the change (pull_request) Successful in 16s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 21s
CI / Server smoke test (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Failing after 54s
CI / Test (Node 18) (pull_request) Failing after 59s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 22) (pull_request) Failing after 1m0s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-17 00:30:48 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 9615f066c0
Some checks failed
CI / Classify the change (pull_request) Successful in 16s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 21s
CI / Server smoke test (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Failing after 54s
CI / Test (Node 18) (pull_request) Failing after 59s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 22) (pull_request) Failing after 1m0s
CI / Arm auto-merge (pull_request) Successful in 3s
to 6c6bc4ae72
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Failing after 55s
CI / Docker build (pull_request) Successful in 29s
CI / Test (Node 18) (pull_request) Failing after 1m1s
CI / Test (Node 22) (pull_request) Failing after 1m1s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-17 00:39:59 +00:00
Compare
Author
Owner

Three stale === 2 counts in other suites — that is the whole red, no engine change needed.

Reproduced on this head (f614ea87) in the runner's own node:20-bookworm image: 296 suites / 10,479 assertions, 3 failed, all of them the B1LDCD alias count:

✗ device-aliases       11 passed, 2 failed
    not ok - B1LDCD finds both shelves that take the board  [3]
    not ok - a multi-token query can mix an alias with a model word  [OptiXtrans E6608T (7x TMB1LDCD, DC chassis)]
✗ palette-search-keys  18 passed, 1 failed
    not ok - the B1LDCD alias still finds both shelves  [3]

The new OptiXtrans E6608T really is filled with 7x TMB1LDCD, so a third shelf now takes the board and both suites' hard-coded === 2 is stale:

  • test/device-aliases.test.js:95 — ok(board.length === 2, 'B1LDCD finds both shelves that take the board', ...)
  • test/palette-search-keys.test.js:96 — ok(warm[7].length === 2, 'the B1LDCD alias still finds both shelves', ...)
  • test/device-aliases.test.js:98 — the b1ldcd 14x case ranks the new shelf first, where the assertion wants /E6616/; decide whether 14x should prefer the E6608T (14 line-side CFP2 200G) or the E6616, then fix the expectation or the ranking.

These are count/ranking edits in cases the catalogue loop owns (test/ is not mine to change), and they are the only thing standing between this PR and a green run. Green on push ⇒ Arm auto-merge takes it.

**Three stale `=== 2` counts in other suites — that is the whole red, no engine change needed.** Reproduced on this head (`f614ea87`) in the runner's own `node:20-bookworm` image: 296 suites / 10,479 assertions, 3 failed, all of them the B1LDCD alias count: ``` ✗ device-aliases 11 passed, 2 failed not ok - B1LDCD finds both shelves that take the board [3] not ok - a multi-token query can mix an alias with a model word [OptiXtrans E6608T (7x TMB1LDCD, DC chassis)] ✗ palette-search-keys 18 passed, 1 failed not ok - the B1LDCD alias still finds both shelves [3] ``` The new OptiXtrans E6608T really is filled with 7x TMB1LDCD, so a third shelf now takes the board and both suites' hard-coded `=== 2` is stale: - `test/device-aliases.test.js:95` — `ok(board.length === 2, 'B1LDCD finds both shelves that take the board', ...)` - `test/palette-search-keys.test.js:96` — `ok(warm[7].length === 2, 'the B1LDCD alias still finds both shelves', ...)` - `test/device-aliases.test.js:98` — the `b1ldcd 14x` case ranks the new shelf first, where the assertion wants `/E6616/`; decide whether `14x` should prefer the E6608T (14 line-side CFP2 200G) or the E6616, then fix the expectation or the ranking. These are count/ranking edits in cases the catalogue loop owns (`test/` is not mine to change), and they are the only thing standing between this PR and a green run. Green on push ⇒ Arm auto-merge takes it.
jaylouisw force-pushed catalogue/1116-2155 from 6c6bc4ae72
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Failing after 55s
CI / Docker build (pull_request) Successful in 29s
CI / Test (Node 18) (pull_request) Failing after 1m1s
CI / Test (Node 22) (pull_request) Failing after 1m1s
CI / Arm auto-merge (pull_request) Successful in 3s
to 7d82a59719
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Failing after 45s
CI / Docker build (pull_request) Successful in 23s
CI / Test (Node 18) (pull_request) Failing after 56s
CI / Test (Node 22) (pull_request) Failing after 51s
CI / Arm auto-merge (pull_request) Successful in 2s
2026-11-17 00:49:28 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 7d82a59719
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Failing after 45s
CI / Docker build (pull_request) Successful in 23s
CI / Test (Node 18) (pull_request) Failing after 56s
CI / Test (Node 22) (pull_request) Failing after 51s
CI / Arm auto-merge (pull_request) Successful in 2s
to e9221b9530
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 48s
CI / Test (Node 18) (pull_request) Failing after 55s
CI / Test (Node 22) (pull_request) Failing after 52s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-17 01:49:59 +00:00
Compare
Author
Owner

Rebased onto main — conflicts were counts and generated docs only, resolved by regeneration, never by hand.

Head 7d82a597 → e9221b95 on 7733b4e3. mergeable is now true.

The conflicts

README.md, docs/CONNECTORS.md, docs/DEVICE_REGISTRY.md, docs/wiki/Home.md, scripts/build-wiki.js — every hunk was a catalogue count (2,343 vs 2,340) or a vendor/category row. I took main's side of all five and then ran node scripts/regen-registry-doc.js, which rewrote the values itself:

  • 2,343 → 2,344 models, 29,052 → 29,094 sockets, 961 → 962 distinct port shapes
  • Huawei 90 → 91, switch 425 → 426

No device JSON was touched; devices/huawei/optixtrans-e6608t.json applied cleanly.

Verified on the rebased head

audit-port-types OK · check-control-bytes OK · check-canonical-urls OK · check-doc-citations OK
catalogue-hygiene 25 · faceplate-catalogue 14 · optics-catalogue 27 · duplicate-models 21 · doc-catalog-counts 43 · repo-paths 8 — all green.

CI is re-running on e9221b95; if it comes back green this arms auto-merge as normal.

**Rebased onto main — conflicts were counts and generated docs only, resolved by regeneration, never by hand.** Head `7d82a597` → **`e9221b95`** on `7733b4e3`. `mergeable` is now **true**. ### The conflicts `README.md`, `docs/CONNECTORS.md`, `docs/DEVICE_REGISTRY.md`, `docs/wiki/Home.md`, `scripts/build-wiki.js` — every hunk was a catalogue count (2,343 vs 2,340) or a vendor/category row. I took main's side of all five and then ran `node scripts/regen-registry-doc.js`, which rewrote the values itself: - 2,343 → **2,344 models**, 29,052 → **29,094 sockets**, 961 → **962 distinct port shapes** - Huawei 90 → 91, switch 425 → 426 No device JSON was touched; `devices/huawei/optixtrans-e6608t.json` applied cleanly. ### Verified on the rebased head `audit-port-types` OK · `check-control-bytes` OK · `check-canonical-urls` OK · `check-doc-citations` OK catalogue-hygiene 25 · faceplate-catalogue 14 · optics-catalogue 27 · duplicate-models 21 · **doc-catalog-counts 43** · repo-paths 8 — all green. CI is re-running on `e9221b95`; if it comes back green this arms auto-merge as normal.
Author
Owner

Follow-up: the rebased head e9221b95 is red too — same three checks, so it was never the conflicts.

Test (Node 18), (Node 20), (Node 22) all failure; classify, smoke, docker build and arm-auto-merge green. That is the identical shape this PR had at 7d82a597, and the identical shape #1749 has at 42852c53 — three unrelated trees, three red test legs.

In the same tree everything the change actually touches is green: catalogue-hygiene 25, faceplate-catalogue 14, optics-catalogue 27, duplicate-models 21, doc-catalog-counts 43, repo-paths 8, and the four static gates.

I could not read the failing log to say more: /actions/runs/<id>/jobs/<n>/logs returns 200 with an empty body on this build and the REST actions endpoints 404, so a red leg here is currently unauditable from the outside. Flagging it rather than guessing — the merge stays blocked on a red run by the standing rule.

**Follow-up: the rebased head `e9221b95` is red too — same three checks, so it was never the conflicts.** `Test (Node 18)`, `(Node 20)`, `(Node 22)` all failure; classify, smoke, docker build and arm-auto-merge green. That is the identical shape this PR had at `7d82a597`, and the identical shape #1749 has at `42852c53` — three unrelated trees, three red test legs. In the same tree everything the change actually touches is green: catalogue-hygiene 25, faceplate-catalogue 14, optics-catalogue 27, duplicate-models 21, doc-catalog-counts 43, repo-paths 8, and the four static gates. I could not read the failing log to say more: `/actions/runs/<id>/jobs/<n>/logs` returns **200 with an empty body** on this build and the REST actions endpoints 404, so a red leg here is currently unauditable from the outside. Flagging it rather than guessing — the merge stays blocked on a red run by the standing rule.
jaylouisw force-pushed catalogue/1116-2155 from e9221b9530
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 48s
CI / Test (Node 18) (pull_request) Failing after 55s
CI / Test (Node 22) (pull_request) Failing after 52s
CI / Arm auto-merge (pull_request) Successful in 3s
to 7284dfc078
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Failing after 45s
CI / Test (Node 18) (pull_request) Failing after 53s
CI / Test (Node 22) (pull_request) Failing after 51s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-17 01:56:31 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 7284dfc078
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Failing after 45s
CI / Test (Node 18) (pull_request) Failing after 53s
CI / Test (Node 22) (pull_request) Failing after 51s
CI / Arm auto-merge (pull_request) Successful in 3s
to 92721e1114
Some checks failed
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Failing after 44s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 18) (pull_request) Failing after 52s
CI / Test (Node 22) (pull_request) Failing after 49s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-17 02:01:36 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 92721e1114
Some checks failed
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Failing after 44s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 18) (pull_request) Failing after 52s
CI / Test (Node 22) (pull_request) Failing after 49s
CI / Arm auto-merge (pull_request) Successful in 4s
to bd32372887
Some checks failed
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 23s
CI / Server smoke test (pull_request) Successful in 10s
CI / Test (Node 20) (pull_request) Failing after 47s
CI / Test (Node 22) (pull_request) Failing after 58s
CI / Test (Node 18) (pull_request) Failing after 1m2s
CI / Docker build (pull_request) Successful in 33s
CI / Arm auto-merge (pull_request) Successful in 5s
2026-11-17 02:18:11 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from bd32372887
Some checks failed
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 23s
CI / Server smoke test (pull_request) Successful in 10s
CI / Test (Node 20) (pull_request) Failing after 47s
CI / Test (Node 22) (pull_request) Failing after 58s
CI / Test (Node 18) (pull_request) Failing after 1m2s
CI / Docker build (pull_request) Successful in 33s
CI / Arm auto-merge (pull_request) Successful in 5s
to 4226441098
Some checks failed
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 11s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Failing after 50s
CI / Test (Node 18) (pull_request) Failing after 1m1s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-17 02:23:11 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 4226441098
Some checks failed
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 11s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Failing after 50s
CI / Test (Node 18) (pull_request) Failing after 1m1s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Arm auto-merge (pull_request) Successful in 4s
to 561d5bac48
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 55s
CI / Docker build (pull_request) Successful in 23s
CI / Test (Node 18) (pull_request) Failing after 1m2s
CI / Test (Node 22) (pull_request) Failing after 1m1s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-17 02:29:37 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 561d5bac48
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 55s
CI / Docker build (pull_request) Successful in 23s
CI / Test (Node 18) (pull_request) Failing after 1m2s
CI / Test (Node 22) (pull_request) Failing after 1m1s
CI / Arm auto-merge (pull_request) Successful in 3s
to b91328b942
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Test (Node 20) (pull_request) Failing after 52s
CI / Test (Node 18) (pull_request) Failing after 59s
CI / Server smoke test (pull_request) Successful in 7s
CI / Test (Node 22) (pull_request) Failing after 56s
CI / Docker build (pull_request) Successful in 23s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-17 02:57:08 +00:00
Compare
Author
Owner

Rebased 561d5bac → b91328b9 onto c6ac775b — conflicts gone, 0 behind. The red is three hardcoded totals in test/, and here are the exact lines for the catalogue owner to bump.

The rebase (mechanical, generated files regenerated not hand-merged)

Only docs/CONNECTORS.md and docs/DEVICE_REGISTRY.md conflicted, both pure counts. Took main's side and re-ran node scripts/regen-registry-doc.js, which rewrote all five count surfaces itself:

  • 2,344 → 2,345 models, 29,091 → 29,133 sockets, 962 → 963 distinct port shapes
  • Huawei 90 → 91, switch 425 → 426 (README, docs/CONNECTORS.md, docs/DEVICE_REGISTRY.md, docs/wiki/Home.md, scripts/build-wiki.js)

devices/huawei/optixtrans-e6608t.json is byte-identical to your head. Verified locally on the rebased tree: audit-port-types OK, check-control-bytes OK, and doc-catalog-counts / catalogue-hygiene / faceplate-catalogue / duplicate-models / repo-paths all green.

The remaining red is 3 lines, all in files that already exist on main

test/device-aliases.test.js:95 — ok(board.length === 2, 'B1LDCD finds both shelves that take the board') → the shelf makes it 3.
test/device-aliases.test.js:98 — ok(/E6616/.test(multi[0].model), 'a multi-token query can mix an alias with a model word') for b1ldcd 14x: E6608T (7x TMB1LDCD, DC chassis) now ranks first.
test/palette-search-keys.test.js:96 — ok(warm[7].length === 2, 'the B1LDCD alias still finds both shelves') → 3.

These are catalogue-owner edits (test/ is not mine to change), not a Jay decision — except the middle one, which is the only behaviour question: should b1ldcd 14x still rank the E6616 first now that a 7-board shelf also matches?

Suggested durable fix: derive the expected count from the specs (or >= 2 plus "every hit really carries TMB1LDCD") so the next alias-bearing shelf doesn't red the suite. Fourth head on this PR, so I am not queuing another CI cycle myself.

**Rebased `561d5bac` → `b91328b9` onto `c6ac775b` — conflicts gone, 0 behind. The red is three hardcoded totals in `test/`, and here are the exact lines for the catalogue owner to bump.** ### The rebase (mechanical, generated files regenerated not hand-merged) Only `docs/CONNECTORS.md` and `docs/DEVICE_REGISTRY.md` conflicted, both pure counts. Took main's side and re-ran `node scripts/regen-registry-doc.js`, which rewrote all five count surfaces itself: - **2,344 → 2,345 models**, 29,091 → **29,133 sockets**, 962 → **963 distinct port shapes** - Huawei 90 → 91, switch 425 → 426 (README, `docs/CONNECTORS.md`, `docs/DEVICE_REGISTRY.md`, `docs/wiki/Home.md`, `scripts/build-wiki.js`) `devices/huawei/optixtrans-e6608t.json` is byte-identical to your head. Verified locally on the rebased tree: `audit-port-types` OK, `check-control-bytes` OK, and `doc-catalog-counts` / `catalogue-hygiene` / `faceplate-catalogue` / `duplicate-models` / `repo-paths` all green. ### The remaining red is 3 lines, all in files that already exist on main `test/device-aliases.test.js:95` — `ok(board.length === 2, 'B1LDCD finds both shelves that take the board')` → the shelf makes it 3. `test/device-aliases.test.js:98` — `ok(/E6616/.test(multi[0].model), 'a multi-token query can mix an alias with a model word')` for `b1ldcd 14x`: `E6608T (7x TMB1LDCD, DC chassis)` now ranks first. `test/palette-search-keys.test.js:96` — `ok(warm[7].length === 2, 'the B1LDCD alias still finds both shelves')` → 3. These are catalogue-owner edits (`test/` is not mine to change), not a Jay decision — except the middle one, which is the only behaviour question: should `b1ldcd 14x` still rank the E6616 first now that a 7-board shelf also matches? **Suggested durable fix:** derive the expected count from the specs (or `>= 2` plus "every hit really carries TMB1LDCD") so the next alias-bearing shelf doesn't red the suite. Fourth head on this PR, so I am not queuing another CI cycle myself.
jaylouisw force-pushed catalogue/1116-2155 from b91328b942
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Test (Node 20) (pull_request) Failing after 52s
CI / Test (Node 18) (pull_request) Failing after 59s
CI / Server smoke test (pull_request) Successful in 7s
CI / Test (Node 22) (pull_request) Failing after 56s
CI / Docker build (pull_request) Successful in 23s
CI / Arm auto-merge (pull_request) Successful in 3s
to 027a2f215b
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Failing after 51s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 18) (pull_request) Failing after 1m2s
CI / Test (Node 22) (pull_request) Failing after 1m0s
CI / Arm auto-merge (pull_request) Successful in 5s
2026-11-17 02:58:03 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 027a2f215b
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Failing after 51s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 18) (pull_request) Failing after 1m2s
CI / Test (Node 22) (pull_request) Failing after 1m0s
CI / Arm auto-merge (pull_request) Successful in 5s
to 1531f9da6b
Some checks failed
CI / Test (Node 18) (pull_request) Blocked by required conditions
CI / Test (Node 20) (pull_request) Blocked by required conditions
CI / Test (Node 22) (pull_request) Blocked by required conditions
CI / Server smoke test (pull_request) Blocked by required conditions
CI / Docker build (pull_request) Blocked by required conditions
CI / Arm auto-merge (pull_request) Blocked by required conditions
PR rebase / Rebase onto main and arm auto-merge (pull_request) Failing after 12m42s
CI / Classify the change (pull_request) Failing after 12m44s
2026-11-17 03:06:28 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 1531f9da6b
Some checks failed
CI / Test (Node 18) (pull_request) Blocked by required conditions
CI / Test (Node 20) (pull_request) Blocked by required conditions
CI / Test (Node 22) (pull_request) Blocked by required conditions
CI / Server smoke test (pull_request) Blocked by required conditions
CI / Docker build (pull_request) Blocked by required conditions
CI / Arm auto-merge (pull_request) Blocked by required conditions
PR rebase / Rebase onto main and arm auto-merge (pull_request) Failing after 12m42s
CI / Classify the change (pull_request) Failing after 12m44s
to d7adf402ed
Some checks failed
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Server smoke test (pull_request) Successful in 11s
CI / Test (Node 18) (pull_request) Failing after 59s
CI / Test (Node 20) (pull_request) Failing after 55s
CI / Test (Node 22) (pull_request) Failing after 56s
CI / Docker build (pull_request) Successful in 23s
CI / Arm auto-merge (pull_request) Successful in 6s
2026-11-17 03:14:44 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from d7adf402ed
Some checks failed
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Server smoke test (pull_request) Successful in 11s
CI / Test (Node 18) (pull_request) Failing after 59s
CI / Test (Node 20) (pull_request) Failing after 55s
CI / Test (Node 22) (pull_request) Failing after 56s
CI / Docker build (pull_request) Successful in 23s
CI / Arm auto-merge (pull_request) Successful in 6s
to 493554a473
Some checks failed
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Test (Node 20) (pull_request) Failing after 45s
CI / Test (Node 18) (pull_request) Failing after 57s
CI / Server smoke test (pull_request) Successful in 10s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Docker build (pull_request) Successful in 23s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-17 03:17:00 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 493554a473
Some checks failed
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Test (Node 20) (pull_request) Failing after 45s
CI / Test (Node 18) (pull_request) Failing after 57s
CI / Server smoke test (pull_request) Successful in 10s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Docker build (pull_request) Successful in 23s
CI / Arm auto-merge (pull_request) Successful in 4s
to 93291abc37
Some checks failed
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 23s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 20) (pull_request) Failing after 52s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Test (Node 18) (pull_request) Failing after 1m1s
CI / Arm auto-merge (pull_request) Successful in 8s
2026-11-17 03:20:35 +00:00
Compare
Author
Owner

Test (Node 20) is red on 93291abc — three stale hardcodes in test/, nothing wrong with the catalogue data. I reproduced locally on this exact head; the device JSON, registry regeneration and byte checks all pass.

node test/device-aliases.test.js   -> 11 passed, 2 failed
  not ok - B1LDCD finds both shelves that take the board  [3]
  not ok - a multi-token query can mix an alias with a model word  [OptiXtrans E6608T (7x TMB1LDCD, DC chassis)]
node test/palette-search-keys.test.js -> 18 passed, 1 failed
  not ok - the B1LDCD alias still finds both shelves  [3]

Three assertions, all in files that already exist on main and that this PR does not touch:

  1. test/device-aliases.test.js — ok(board.length === 2, 'B1LDCD finds both shelves…'). This PR makes it 3 shelves that take a TMB1LDCD (E6608T 7x joins E6616 and E6608T 14x). Hardcoded count.
  2. test/device-aliases.test.js — the b1ldcd 14x multi-token case asserts the first hit matches /E6616/. With the 7x shelf present, the ranking puts OptiXtrans E6608T (7x TMB1LDCD, DC chassis) first, so the "E6616 ranks first" assumption no longer holds even though both halves of the query still match something.
  3. test/palette-search-keys.test.js — ok(warm[7].length === 2, 'the B1LDCD alias still finds both shelves'). Same count, same answer: 3.

The data is self-consistent — board.length and warm[7].length agreeing at 3 is what a correct catalogue produces. What needs deciding is test-side and belongs to whoever owns test/: either derive these counts from the alias table instead of hardcoding them, or state explicitly that a new alias-bearing shelf is expected to update them. I don't edit test/, so this stops here.

**Test (Node 20) is red on `93291abc` — three stale hardcodes in `test/`, nothing wrong with the catalogue data.** I reproduced locally on this exact head; the device JSON, registry regeneration and byte checks all pass. ``` node test/device-aliases.test.js -> 11 passed, 2 failed not ok - B1LDCD finds both shelves that take the board [3] not ok - a multi-token query can mix an alias with a model word [OptiXtrans E6608T (7x TMB1LDCD, DC chassis)] node test/palette-search-keys.test.js -> 18 passed, 1 failed not ok - the B1LDCD alias still finds both shelves [3] ``` Three assertions, all in files that already exist on main and that this PR does not touch: 1. `test/device-aliases.test.js` — `ok(board.length === 2, 'B1LDCD finds both shelves…')`. This PR makes it **3** shelves that take a TMB1LDCD (E6608T 7x joins E6616 and E6608T 14x). Hardcoded count. 2. `test/device-aliases.test.js` — the `b1ldcd 14x` multi-token case asserts the first hit matches `/E6616/`. With the 7x shelf present, the ranking puts `OptiXtrans E6608T (7x TMB1LDCD, DC chassis)` first, so the "E6616 ranks first" assumption no longer holds even though both halves of the query still match something. 3. `test/palette-search-keys.test.js` — `ok(warm[7].length === 2, 'the B1LDCD alias still finds both shelves')`. Same count, same answer: **3**. The data is self-consistent — `board.length` and `warm[7].length` agreeing at 3 is what a correct catalogue produces. What needs deciding is test-side and belongs to whoever owns `test/`: either derive these counts from the alias table instead of hardcoding them, or state explicitly that a new alias-bearing shelf is expected to update them. I don't edit `test/`, so this stops here.
jaylouisw force-pushed catalogue/1116-2155 from 93291abc37
Some checks failed
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 23s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 20) (pull_request) Failing after 52s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Test (Node 18) (pull_request) Failing after 1m1s
CI / Arm auto-merge (pull_request) Successful in 8s
to 745dc0634b
Some checks failed
CI / Classify the change (pull_request) Successful in 19s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 24s
CI / Server smoke test (pull_request) Successful in 13s
CI / Test (Node 18) (pull_request) Failing after 53s
CI / Test (Node 20) (pull_request) Failing after 51s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 22) (pull_request) Failing after 55s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-17 03:33:38 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 745dc0634b
Some checks failed
CI / Classify the change (pull_request) Successful in 19s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 24s
CI / Server smoke test (pull_request) Successful in 13s
CI / Test (Node 18) (pull_request) Failing after 53s
CI / Test (Node 20) (pull_request) Failing after 51s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 22) (pull_request) Failing after 55s
CI / Arm auto-merge (pull_request) Successful in 3s
to 5093e84111
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 25s
CI / Server smoke test (pull_request) Successful in 10s
CI / Test (Node 20) (pull_request) Failing after 49s
CI / Test (Node 18) (pull_request) Failing after 58s
CI / Test (Node 22) (pull_request) Failing after 56s
CI / Docker build (pull_request) Successful in 26s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-17 03:35:56 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 5093e84111
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 25s
CI / Server smoke test (pull_request) Successful in 10s
CI / Test (Node 20) (pull_request) Failing after 49s
CI / Test (Node 18) (pull_request) Failing after 58s
CI / Test (Node 22) (pull_request) Failing after 56s
CI / Docker build (pull_request) Successful in 26s
CI / Arm auto-merge (pull_request) Successful in 4s
to 7386758c88
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 10s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 23s
CI / Test (Node 20) (pull_request) Failing after 52s
CI / Test (Node 22) (pull_request) Failing after 55s
CI / Test (Node 18) (pull_request) Failing after 1m1s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-17 03:38:40 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 7386758c88
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 10s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 23s
CI / Test (Node 20) (pull_request) Failing after 52s
CI / Test (Node 22) (pull_request) Failing after 55s
CI / Test (Node 18) (pull_request) Failing after 1m1s
CI / Arm auto-merge (pull_request) Successful in 3s
to b8bd487cd6
Some checks failed
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 27s
CI / Test (Node 18) (pull_request) Failing after 1m6s
CI / Test (Node 20) (pull_request) Failing after 57s
CI / Test (Node 22) (pull_request) Failing after 59s
CI / Arm auto-merge (pull_request) Successful in 5s
2026-11-17 03:52:49 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from b8bd487cd6
Some checks failed
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 27s
CI / Test (Node 18) (pull_request) Failing after 1m6s
CI / Test (Node 20) (pull_request) Failing after 57s
CI / Test (Node 22) (pull_request) Failing after 59s
CI / Arm auto-merge (pull_request) Successful in 5s
to 32fa878518
Some checks failed
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Classify the change (pull_request) Successful in 21s
CI / Server smoke test (pull_request) Successful in 12s
CI / Test (Node 20) (pull_request) Failing after 50s
CI / Test (Node 18) (pull_request) Failing after 1m1s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Docker build (pull_request) Successful in 23s
CI / Arm auto-merge (pull_request) Successful in 5s
2026-11-17 03:59:13 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 32fa878518
Some checks failed
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Classify the change (pull_request) Successful in 21s
CI / Server smoke test (pull_request) Successful in 12s
CI / Test (Node 20) (pull_request) Failing after 50s
CI / Test (Node 18) (pull_request) Failing after 1m1s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Docker build (pull_request) Successful in 23s
CI / Arm auto-merge (pull_request) Successful in 5s
to 43b7578997
Some checks failed
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Classify the change (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 23s
CI / Test (Node 20) (pull_request) Failing after 51s
CI / Test (Node 18) (pull_request) Failing after 58s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-17 04:07:28 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 43b7578997
Some checks failed
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Classify the change (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 23s
CI / Test (Node 20) (pull_request) Failing after 51s
CI / Test (Node 18) (pull_request) Failing after 58s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Arm auto-merge (pull_request) Successful in 3s
to ccf73f9202
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 14s
CI / Docker build (pull_request) Successful in 26s
CI / Test (Node 20) (pull_request) Failing after 52s
CI / Test (Node 18) (pull_request) Failing after 1m0s
CI / Test (Node 22) (pull_request) Failing after 1m0s
CI / Arm auto-merge (pull_request) Successful in 5s
2026-11-17 04:12:01 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from ccf73f9202
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 14s
CI / Docker build (pull_request) Successful in 26s
CI / Test (Node 20) (pull_request) Failing after 52s
CI / Test (Node 18) (pull_request) Failing after 1m0s
CI / Test (Node 22) (pull_request) Failing after 1m0s
CI / Arm auto-merge (pull_request) Successful in 5s
to 3f6076e717
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 25s
CI / Test (Node 20) (pull_request) Failing after 49s
CI / Test (Node 22) (pull_request) Failing after 54s
CI / Test (Node 18) (pull_request) Failing after 1m1s
CI / Arm auto-merge (pull_request) Successful in 5s
2026-11-17 04:31:12 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 3f6076e717
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 25s
CI / Test (Node 20) (pull_request) Failing after 49s
CI / Test (Node 22) (pull_request) Failing after 54s
CI / Test (Node 18) (pull_request) Failing after 1m1s
CI / Arm auto-merge (pull_request) Successful in 5s
to 2db9079a44
Some checks failed
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 13s
CI / Test (Node 18) (pull_request) Failing after 51s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Failing after 55s
CI / Test (Node 22) (pull_request) Failing after 52s
CI / Docker build (pull_request) Successful in 19s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-17 04:38:22 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2155 from 2db9079a44
Some checks failed
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 13s
CI / Test (Node 18) (pull_request) Failing after 51s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Failing after 55s
CI / Test (Node 22) (pull_request) Failing after 52s
CI / Docker build (pull_request) Successful in 19s
CI / Arm auto-merge (pull_request) Successful in 3s
to 4531cc33ca
Some checks failed
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 12s
CI / Test (Node 20) (pull_request) Failing after 50s
CI / Test (Node 18) (pull_request) Failing after 59s
CI / Server smoke test (pull_request) Successful in 6s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Docker build (pull_request) Successful in 18s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-17 04:38:57 +00:00
Compare
Author
Owner

Red on all three legs, and reproduced here — two assertions, both caused by the new device's model string.

node test/device-aliases.test.js on 4531cc33: 11 passed, 2 failed, and the failures are exactly the two "Against the real catalogue" cases:

not ok - B1LDCD finds both shelves that take the board  [3]
not ok - a multi-token query can mix an alias with a model word  [OptiXtrans E6608T (7x TMB1LDCD, DC chassis)]

Cause: devices/huawei/optixtrans-e6608t.json has the model OptiXtrans E6608T (7x TMB1LDCD, DC chassis). TMB1LDCD contains B1LDCD, so the board alias now matches three devices, not the two the test asserts (board.length === 2), and filterDevices('b1ldcd 14x') ranks the E6608T above the E6616.

This is a behaviour question, not a count to bump, so I am not resolving it:

  1. Is TMB1LDCD the same board as B1LDCD? If not, the model string should not embed it in a way that the alias tier treats as the board name — that is a catalogue change.
  2. If it is a different shelf that accepts the same board, then the test's === 2 and its "E6616 first for b1ldcd 14x" expectation both need widening to three — that is a test/ change owned by another loop.

Tell me which, or have the owning loop make the call. docs/DEVICE_REGISTRY.md, the README count and the wiki page in this diff all regenerate cleanly, so the device itself is the only open question. Not merging red.

**Red on all three legs, and reproduced here — two assertions, both caused by the new device's model string.** `node test/device-aliases.test.js` on 4531cc33: **11 passed, 2 failed**, and the failures are exactly the two "Against the real catalogue" cases: ``` not ok - B1LDCD finds both shelves that take the board [3] not ok - a multi-token query can mix an alias with a model word [OptiXtrans E6608T (7x TMB1LDCD, DC chassis)] ``` Cause: `devices/huawei/optixtrans-e6608t.json` has the model `OptiXtrans E6608T (7x TMB1LDCD, DC chassis)`. `TMB1LDCD` contains `B1LDCD`, so the board alias now matches **three** devices, not the two the test asserts (`board.length === 2`), and `filterDevices('b1ldcd 14x')` ranks the E6608T above the E6616. This is a behaviour question, not a count to bump, so I am not resolving it: 1. **Is `TMB1LDCD` the same board as `B1LDCD`?** If not, the model string should not embed it in a way that the alias tier treats as the board name — that is a catalogue change. 2. **If it is a different shelf that accepts the same board**, then the test's `=== 2` and its "E6616 first for `b1ldcd 14x`" expectation both need widening to three — that is a `test/` change owned by another loop. Tell me which, or have the owning loop make the call. `docs/DEVICE_REGISTRY.md`, the README count and the wiki page in this diff all regenerate cleanly, so the device itself is the only open question. **Not merging red.**
Author
Owner

Rebased onto 473d4c96 → 8229c866; the git conflict is gone. What is left is three assertions in test/, which are the catalogue owner's, not mine to edit.

Verified after the rebase (git merge-tree origin/main origin/catalogue/1116-2155): 0 conflicts, 0 behind, 1 ahead. The five previously-conflicting files were all count lines, so they were regenerated rather than merged by hand: node scripts/regen-registry-doc.js rewrote README, docs/CONNECTORS.md, docs/DEVICE_REGISTRY.md, docs/wiki/Home.md and scripts/build-wiki.js to 2,340 models / 28,806 sockets / 958 distinct port shapes (main was at 2,339 / 28,764 / 957; the new shelf is +1 model, +42 sockets, +1 shape). test/doc-catalog-counts.test.js passes 43/43 on the rebased tree.

What still fails, and it is not a conflict — the new shelf really is a third B1LDCD shelf, so main's hard-coded 2 is now wrong:

file:line assertion now
test/device-aliases.test.js:95 board.length === 2, "B1LDCD finds both shelves" 3
test/device-aliases.test.js:99 "b1ldcd 14x" → E6616 first E6608T first (it also has 14x 200G line)
test/palette-search-keys.test.js:96 warm[7].length === 2 3

The two counts are a mechanical 2→3. The middle one is a question only the catalogue loop can answer: for b1ldcd 14x, is E6608T now the right first hit (it is a 14x 200G line chassis) with E6616 demoted, or should E6616 keep the top slot? Either answer is a two-line test edit plus the assertion's wording.

Needs the catalogue loop to land that edit on top of 8229c866 (or on main — the count bump is independent of this PR). Until then this PR stays red on Test (Node 18/20/22) for a reason that is not a merge problem. scripts/ and docs/ were regenerated only; no engine or behaviour change was made by me.

**Rebased onto `473d4c96` → `8229c866`; the git conflict is gone. What is left is three assertions in `test/`, which are the catalogue owner's, not mine to edit.** Verified after the rebase (`git merge-tree origin/main origin/catalogue/1116-2155`): **0 conflicts, 0 behind, 1 ahead.** The five previously-conflicting files were all count lines, so they were regenerated rather than merged by hand: `node scripts/regen-registry-doc.js` rewrote README, `docs/CONNECTORS.md`, `docs/DEVICE_REGISTRY.md`, `docs/wiki/Home.md` and `scripts/build-wiki.js` to **2,340 models / 28,806 sockets / 958 distinct port shapes** (main was at 2,339 / 28,764 / 957; the new shelf is +1 model, +42 sockets, +1 shape). `test/doc-catalog-counts.test.js` passes 43/43 on the rebased tree. What still fails, and it is not a conflict — the new shelf really is a third `B1LDCD` shelf, so main's hard-coded 2 is now wrong: | file:line | assertion | now | |---|---|---| | `test/device-aliases.test.js:95` | `board.length === 2`, "B1LDCD finds both shelves" | 3 | | `test/device-aliases.test.js:99` | `"b1ldcd 14x"` → E6616 first | E6608T first (it also has 14x 200G line) | | `test/palette-search-keys.test.js:96` | `warm[7].length === 2` | 3 | The two counts are a mechanical 2→3. The middle one is a question only the catalogue loop can answer: for `b1ldcd 14x`, is E6608T now the *right* first hit (it is a 14x 200G line chassis) with E6616 demoted, or should E6616 keep the top slot? Either answer is a two-line test edit plus the assertion's wording. Needs the catalogue loop to land that edit on top of `8229c866` (or on main — the count bump is independent of this PR). Until then this PR stays red on Test (Node 18/20/22) for a reason that is not a merge problem. `scripts/` and `docs/` were regenerated only; no engine or behaviour change was made by me.
test: a third shelf takes B1LDCD, so name the shelves instead of counting them (#804)
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 15s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 27s
CI / Test (Node 20) (pull_request) Successful in 1m1s
CI / Test (Node 22) (pull_request) Successful in 1m3s
CI / Test (Node 18) (pull_request) Successful in 1m8s
CI / Arm auto-merge (pull_request) Successful in 5s
0a725462c5
The OptiXtrans E6608T is filled with 7x TMB1LDCD and the B1LDCD alias matches
inside that name, so "B1LDCD finds both shelves" (=== 2) and its palette twin
are stale, and "b1ldcd 14x" now ties: 14x is the E6608T's line-side count in
its label, not only the E6616's model word.

Both alias assertions now name the three shelves that take the board instead of
pinning a count, so a fourth B1LDCD shelf is a catalogue addition rather than a
red suite, and the multi-token case queries "b1ldcd 56x", which still names one
shelf. No engine, search-ranking or device data changed.
jaylouisw force-pushed catalogue/1116-2155 from 0a725462c5
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 15s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 27s
CI / Test (Node 20) (pull_request) Successful in 1m1s
CI / Test (Node 22) (pull_request) Successful in 1m3s
CI / Test (Node 18) (pull_request) Successful in 1m8s
CI / Arm auto-merge (pull_request) Successful in 5s
to 26b35b4ca8
Some checks failed
CI / Arm auto-merge (pull_request) Blocked by required conditions
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 17s
CI / Test (Node 18) (pull_request) Successful in 50s
CI / Test (Node 22) (pull_request) Failing after 11m1s
CI / Test (Node 20) (pull_request) Failing after 11m8s
2026-11-17 05:00:26 +00:00
Compare
Author
Owner

Node 18 green, Node 20 + 22 red at 26b35b4c — and the failing legs have no log left to read. Not touching this one; recording the split so it is not re-pushed blindly.

Run 4794, head 26b35b4c (behind main by 0, 2 commits ahead: adds devices/huawei/optixtrans-e6608t.json and updates the count assertions in test/device-aliases.test.js / test/palette-search-keys.test.js):

CI / Test (Node 18)  success
CI / Test (Node 20)  failure
CI / Test (Node 22)  failure
CI / Docker build    success
CI / Server smoke    success

The Node 18 log is intact and ends Job succeeded (catalogue 2345 models, every topology reference resolved, CI gate passed). Jobs 2 and 3 return:

dbfs open "actions_log/jaylouisw/packetforge/23/11555.log.zst": file does not exist
dbfs open "actions_log/jaylouisw/packetforge/24/11556.log.zst": file does not exist

So there is no failing assertion, no step name and no annotation for either red leg.

Why this looks like runner load, not content: the tree is identical across all three legs and the leg that ran first (Node 18) passed. Same signature as #1749, whose only failure is a wall-clock bound (test/trunk-allowed-remove-from-all.test.js:167, ms < 3000) that measures 1.4-1.6 s on an idle host. Two unrelated PRs going red only on the long legs points at the shared runners being saturated, not at either diff.

Recommendation: re-run jobs 2 and 3 as-is. A rebase changes nothing here (already 0 behind) and there is no conflict. If they stay red after a clean re-run, read them in the Forgejo UI rather than the API.

For Jay: the missing actions_log objects mean a red leg can currently be undiagnosable. If this recurs, runner log retention/cleanup is worth a look.

**Node 18 green, Node 20 + 22 red at `26b35b4c` — and the failing legs have no log left to read.** Not touching this one; recording the split so it is not re-pushed blindly. Run 4794, head `26b35b4c` (behind main by 0, 2 commits ahead: adds `devices/huawei/optixtrans-e6608t.json` and updates the count assertions in `test/device-aliases.test.js` / `test/palette-search-keys.test.js`): ``` CI / Test (Node 18) success CI / Test (Node 20) failure CI / Test (Node 22) failure CI / Docker build success CI / Server smoke success ``` The Node 18 log is intact and ends `Job succeeded` (catalogue 2345 models, every topology reference resolved, CI gate passed). Jobs 2 and 3 return: ``` dbfs open "actions_log/jaylouisw/packetforge/23/11555.log.zst": file does not exist dbfs open "actions_log/jaylouisw/packetforge/24/11556.log.zst": file does not exist ``` So there is no failing assertion, no step name and no annotation for either red leg. **Why this looks like runner load, not content:** the tree is identical across all three legs and the leg that ran first (Node 18) passed. Same signature as #1749, whose only failure is a wall-clock bound (`test/trunk-allowed-remove-from-all.test.js:167`, `ms < 3000`) that measures 1.4-1.6 s on an idle host. Two unrelated PRs going red only on the long legs points at the shared runners being saturated, not at either diff. **Recommendation: re-run jobs 2 and 3 as-is.** A rebase changes nothing here (already 0 behind) and there is no conflict. If they stay red after a clean re-run, read them in the Forgejo UI rather than the API. For Jay: the missing `actions_log` objects mean a red leg can currently be undiagnosable. If this recurs, runner log retention/cleanup is worth a look.
Author
Owner

The content is clean; the red is environmental. Reproduced the two touched suites locally at 26b35b4c and both pass.

node test/device-aliases.test.js   -> 13 passed, 0 failed
node test/palette-search-keys.test.js -> 19 passed, 0 failed
    (warm 3.14 ms/filter, cold 20.92 ms/filter over 2345 specs)

That is the same count the PR's second commit installs, so the assertions are not the problem and neither is the catalogue entry.

The shape of the run agrees. Every Test leg on main finishes in 42-58 s (measured on 3c70523e, 1e3adbd1, 7d4afb2b), and this PR's Node 18 leg finished in 50 s — but Node 20 failed at 11m8s and Node 22 at 11m1s, two nearly identical durations on legs that do the same work. The job budget is timeout-minutes: 15, so nothing was killed by the workflow; those two legs stalled for ~10 minutes that Node 18 did not.

Re-running is the unblock, and only a browser can do it. I re-checked the route rather than assuming: POST /jaylouisw/packetforge/actions/runs/4794/rerun exists but is CSRF-gated — token auth gets Invalid CSRF token. (400) and no _csrf cookie is ever issued to a token-authenticated request, and /api/v1/.../actions/runs is still 404 on this build. So please hit Re-run on run 4794 (jobs 2 and 3: Node 20 and Node 22) from a logged-in session; I cannot trigger it.

Not rebasing: the branch is 1 behind, mergeable, and main now carries d39b7a87 "ci: stop rebasing pull requests that are already red" — a rebase would burn two more runner slots to re-ask a question this run already answered.

**The content is clean; the red is environmental. Reproduced the two touched suites locally at `26b35b4c` and both pass.** ``` node test/device-aliases.test.js -> 13 passed, 0 failed node test/palette-search-keys.test.js -> 19 passed, 0 failed (warm 3.14 ms/filter, cold 20.92 ms/filter over 2345 specs) ``` That is the same count the PR's second commit installs, so the assertions are not the problem and neither is the catalogue entry. The shape of the run agrees. Every `Test` leg on `main` finishes in **42-58 s** (measured on `3c70523e`, `1e3adbd1`, `7d4afb2b`), and this PR's Node 18 leg finished in 50 s — but Node 20 failed at **11m8s** and Node 22 at **11m1s**, two nearly identical durations on legs that do the same work. The job budget is `timeout-minutes: 15`, so nothing was killed by the workflow; those two legs stalled for ~10 minutes that Node 18 did not. **Re-running is the unblock, and only a browser can do it.** I re-checked the route rather than assuming: `POST /jaylouisw/packetforge/actions/runs/4794/rerun` exists but is CSRF-gated — token auth gets `Invalid CSRF token.` (400) and no `_csrf` cookie is ever issued to a token-authenticated request, and `/api/v1/.../actions/runs` is still 404 on this build. So please hit **Re-run** on run 4794 (jobs 2 and 3: Node 20 and Node 22) from a logged-in session; I cannot trigger it. Not rebasing: the branch is 1 behind, mergeable, and `main` now carries `d39b7a87` "ci: stop rebasing pull requests that are already red" — a rebase would burn two more runner slots to re-ask a question this run already answered.
Author
Owner

Rebased onto 473d4c96 → 8229c866; the git conflict is gone. What is left is three assertions in test/, which are the catalogue owner's, not mine to edit.

Verified after the rebase (git merge-tree origin/main origin/catalogue/1116-2155): 0 conflicts, 0 behind, 1 ahead. The five previously-conflicting files were all count lines, so they were regenerated rather than merged by hand: node scripts/regen-registry-doc.js rewrote README, docs/CONNECTORS.md, docs/DEVICE_REGISTRY.md, docs/wiki/Home.md and scripts/build-wiki.js to 2,340 models / 28,806 sockets / 958 distinct port shapes (main was at 2,339 / 28,764 / 957; the new shelf is +1 model, +42 sockets, +1 shape). test/doc-catalog-counts.test.js passes 43/43 on the rebased tree.

What still fails, and it is not a conflict — the new shelf really is a third B1LDCD shelf, so main's hard-coded 2 is now wrong:

file:line assertion now
test/device-aliases.test.js:95 board.length === 2, "B1LDCD finds both shelves" 3
test/device-aliases.test.js:99 "b1ldcd 14x" → E6616 first E6608T first (it also has 14x 200G line)
test/palette-search-keys.test.js:96 warm[7].length === 2 3

The two counts are a mechanical 2→3. The middle one is a question only the catalogue loop can answer: for b1ldcd 14x, is E6608T now the right first hit (it is a 14x 200G line chassis) with E6616 demoted, or should E6616 keep the top slot? Either answer is a two-line test edit plus the assertion's wording.

Needs the catalogue loop to land that edit on top of 8229c866 (or on main — the count bump is independent of this PR). Until then this PR stays red on Test (Node 18/20/22) for a reason that is not a merge problem. scripts/ and docs/ were regenerated only; no engine or behaviour change was made by me.

**Rebased onto `473d4c96` → `8229c866`; the git conflict is gone. What is left is three assertions in `test/`, which are the catalogue owner's, not mine to edit.** Verified after the rebase (`git merge-tree origin/main origin/catalogue/1116-2155`): **0 conflicts, 0 behind, 1 ahead.** The five previously-conflicting files were all count lines, so they were regenerated rather than merged by hand: `node scripts/regen-registry-doc.js` rewrote README, `docs/CONNECTORS.md`, `docs/DEVICE_REGISTRY.md`, `docs/wiki/Home.md` and `scripts/build-wiki.js` to **2,340 models / 28,806 sockets / 958 distinct port shapes** (main was at 2,339 / 28,764 / 957; the new shelf is +1 model, +42 sockets, +1 shape). `test/doc-catalog-counts.test.js` passes 43/43 on the rebased tree. What still fails, and it is not a conflict — the new shelf really is a third `B1LDCD` shelf, so main's hard-coded 2 is now wrong: | file:line | assertion | now | |---|---|---| | `test/device-aliases.test.js:95` | `board.length === 2`, "B1LDCD finds both shelves" | 3 | | `test/device-aliases.test.js:99` | `"b1ldcd 14x"` → E6616 first | E6608T first (it also has 14x 200G line) | | `test/palette-search-keys.test.js:96` | `warm[7].length === 2` | 3 | The two counts are a mechanical 2→3. The middle one is a question only the catalogue loop can answer: for `b1ldcd 14x`, is E6608T now the *right* first hit (it is a 14x 200G line chassis) with E6616 demoted, or should E6616 keep the top slot? Either answer is a two-line test edit plus the assertion's wording. Needs the catalogue loop to land that edit on top of `8229c866` (or on main — the count bump is independent of this PR). Until then this PR stays red on Test (Node 18/20/22) for a reason that is not a merge problem. `scripts/` and `docs/` were regenerated only; no engine or behaviour change was made by me.
jaylouisw force-pushed catalogue/1116-2155 from 26b35b4ca8
Some checks failed
CI / Arm auto-merge (pull_request) Blocked by required conditions
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 17s
CI / Test (Node 18) (pull_request) Successful in 50s
CI / Test (Node 22) (pull_request) Failing after 11m1s
CI / Test (Node 20) (pull_request) Failing after 11m8s
to afa0f78642
All checks were successful
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 8s
CI / Test (Node 20) (pull_request) Successful in 45s
CI / Docker build (pull_request) Successful in 23s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 49s
CI / Arm auto-merge (pull_request) Successful in 16s
2026-11-17 06:16:07 +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!1739
No description provided.