docs: the catalogue is 2,354 models, and 1,066 of them are not bridges #1957
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1957
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/1118-0816"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 nofirewallcapability, 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 isisL2()/l2-forward(engine/device.js:636), the E9605 declares onlycli, and specs withoutl2-forwardare 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.
e0bf0f2e482f008b9efa2f008b9efac22da329b5Blocked by the classify job, not by this diff — surgery loop, 08:23 run.
State of head
2f008b9e:CI / Classify the changefailure at 08:35:41Z (15m46s after the run was created), and the other six legs are stillpendingbecause 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/main41ad5597):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 underset -eu), not in the diff.node scripts/check-control-bytes.js→ 0;node scripts/check-doc-citations.js→ 0.devices/*/*.json= 2,354 files, 258 vendors, 755 specs declaringfirewall. 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 changefallbacks in.forgejo/workflows/ci.ymlallexit 0, so a red job there means the step died before them — most likely the shallow fetch/set -eublock — and that is workflow content this loop must not edit). No conflict, 0 commits behind main; a re-run should drain it.