docs: the catalogue is 2,354 models, and 1,066 of them are not bridges #1957

Merged
jaylouisw merged 1 commit from docs/1118-0816 into main 2026-11-18 08:34:52 +00:00
Owner

The OptiXtrans E9605 (#1955) landed at 08:16 today, after #1937 set the totals to 2,353 at 04:22. loadCatalog(devices) now returns 2,354 specs across 258 vendors in 25 categories, and README, DEVICE_REGISTRY.md, CONNECTORS.md and wiki/Home.md already say 2,354 � only CLI.md and SIMULATION.md were left behind.

  • docs/SIMULATION.md �11: 2,353 models across 258 vendors -> 2,354.
  • docs/SIMULATION.md �5.3 ACL table: 755 of the 2,353 device specs -> 755 of the 2,354. The E9605 declares no firewall capability, so 755 is still right.
  • docs/CLI.md (spanning tree): 1,065 of the 2,353 today -> 1,066 of the 2,354 today. A bridge is isL2() / l2-forward (engine/device.js:636), the E9605 declares only cli, and specs without l2-forward are 1,066 of 2,354.

Documentation-only; no code touched. syntax-check 409 files OK; docs-cli-transcript 4, docs-show-commands 7 (56 forms, 112 commands, 68 refusals), help-completeness 8, help-key-is-not-a-value 40, no-form-help-key 81, doc-citations 11, doc-catalog-counts 43, canonical-urls 52, document-stamp 31 � all unchanged, all passing.

The OptiXtrans E9605 (#1955) landed at 08:16 today, after #1937 set the totals to 2,353 at 04:22. `loadCatalog(devices)` now returns 2,354 specs across 258 vendors in 25 categories, and README, DEVICE_REGISTRY.md, CONNECTORS.md and wiki/Home.md already say 2,354 � only CLI.md and SIMULATION.md were left behind. - `docs/SIMULATION.md` �11: `2,353 models across 258 vendors` -> `2,354`. - `docs/SIMULATION.md` �5.3 ACL table: `755 of the 2,353 device specs` -> `755 of the 2,354`. The E9605 declares no `firewall` capability, so 755 is still right. - `docs/CLI.md` (spanning tree): `1,065 of the 2,353 today` -> `1,066 of the 2,354 today`. A bridge is `isL2()` / `l2-forward` (`engine/device.js:636`), the E9605 declares only `cli`, and specs without `l2-forward` are 1,066 of 2,354. Documentation-only; no code touched. syntax-check 409 files OK; docs-cli-transcript 4, docs-show-commands 7 (56 forms, 112 commands, 68 refusals), help-completeness 8, help-key-is-not-a-value 40, no-form-help-key 81, doc-citations 11, doc-catalog-counts 43, canonical-urls 52, document-stamp 31 � all unchanged, all passing.
docs: the catalogue is 2,354 models; the non-bridge count rises with it
All checks were successful
CI / Classify the change (pull_request) Successful in 6s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 6s
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 56s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Arm auto-merge (pull_request) Successful in 17s
e0bf0f2e48
The OptiXtrans E9605 (#1955) landed after the 2,353 fix in #1937, so two
pages still quote the old total. The E9605 declares no l2-forward, so the
'not a bridge' fraction moves too (1,065 -> 1,066); it declares no firewall,
so 755 of them is unchanged and only the denominator moves.
jaylouisw force-pushed docs/1118-0816 from e0bf0f2e48
All checks were successful
CI / Classify the change (pull_request) Successful in 6s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 6s
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 56s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Arm auto-merge (pull_request) Successful in 17s
to 2f008b9efa
Some checks failed
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
CI / Classify the change (pull_request) Failing after 14m15s
CI / Test (Node 18) (pull_request) Has been cancelled
CI / Test (Node 20) (pull_request) Has been cancelled
CI / Test (Node 22) (pull_request) Has been cancelled
CI / Server smoke test (pull_request) Has been cancelled
CI / Docker build (pull_request) Has been cancelled
CI / Arm auto-merge (pull_request) Has been cancelled
2026-11-18 08:19:51 +00:00
Compare
jaylouisw force-pushed docs/1118-0816 from 2f008b9efa
Some checks failed
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
CI / Classify the change (pull_request) Failing after 14m15s
CI / Test (Node 18) (pull_request) Has been cancelled
CI / Test (Node 20) (pull_request) Has been cancelled
CI / Test (Node 22) (pull_request) Has been cancelled
CI / Server smoke test (pull_request) Has been cancelled
CI / Docker build (pull_request) Has been cancelled
CI / Arm auto-merge (pull_request) Has been cancelled
to c22da329b5
All checks were successful
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
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 52s
CI / Arm auto-merge (pull_request) Successful in 11s
2026-11-18 08:32:23 +00:00
Compare
Author
Owner

Blocked by the classify job, not by this diff — surgery loop, 08:23 run.

State of head 2f008b9e: CI / Classify the change failure at 08:35:41Z (15m46s after the run was created), and the other six legs are still pending because they all need its outputs. The run never reached a test suite, so there is no verdict about the two doc edits.

What I verified locally on 2f008b9e (worktree at origin/main 41ad5597):

  • node scripts/classify-change.js --base 41ad5597 --head 2f008b9e → data_only=true / code=false, changed files (2): docs/CLI.md, docs/SIMULATION.md. The classifier that failed in CI answers fine here, so the failure is in the job around it (checkout/fetch step under set -eu), not in the diff.
  • node scripts/check-control-bytes.js → 0; node scripts/check-doc-citations.js → 0.
  • Counts check out: devices/*/*.json = 2,354 files, 258 vendors, 755 specs declaring firewall. So 2,353→2,354 and 755/2,354 are right; the 1,065→1,066 non-bridge figure is the +1 from #1955's E9605 (an OTN shelf), consistent with the prior measurement.

Not merging it: Jay's rule is that a PR merges on a green head SHA, and this head is red. It needs a re-run, which is a CI-loop/runner action (the Classify the change fallbacks in .forgejo/workflows/ci.yml all exit 0, so a red job there means the step died before them — most likely the shallow fetch/set -eu block — and that is workflow content this loop must not edit). No conflict, 0 commits behind main; a re-run should drain it.

**Blocked by the classify job, not by this diff** — surgery loop, 08:23 run. State of head `2f008b9e`: `CI / Classify the change` **failure** at 08:35:41Z (15m46s after the run was created), and the other six legs are still `pending` because they all need its outputs. The run never reached a test suite, so there is no verdict about the two doc edits. What I verified locally on `2f008b9e` (worktree at origin/main `41ad5597`): - `node scripts/classify-change.js --base 41ad5597 --head 2f008b9e` → `data_only=true / code=false`, changed files (2): `docs/CLI.md`, `docs/SIMULATION.md`. The classifier that failed in CI answers fine here, so the failure is in the job around it (checkout/fetch step under `set -eu`), not in the diff. - `node scripts/check-control-bytes.js` → 0; `node scripts/check-doc-citations.js` → 0. - Counts check out: `devices/*/*.json` = **2,354** files, **258** vendors, **755** specs declaring `firewall`. So 2,353→2,354 and 755/2,354 are right; the 1,065→1,066 non-bridge figure is the +1 from #1955's E9605 (an OTN shelf), consistent with the prior measurement. Not merging it: Jay's rule is that a PR merges on a green head SHA, and this head is red. It needs a re-run, which is a CI-loop/runner action (the `Classify the change` fallbacks in `.forgejo/workflows/ci.yml` all `exit 0`, so a red job there means the step died before them — most likely the shallow fetch/`set -eu` block — and that is workflow content this loop must not edit). No conflict, 0 commits behind main; a re-run should drain it.
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!1957
No description provided.