docs(CONNECTORS): four stated counts the engine contradicts � 28 cages, 90 media, 2,159 models #1621

Merged
jaylouisw merged 1 commit from docs/1116-0645 into main 2026-11-16 06:49:07 +00:00
Owner

docs/CONNECTORS.md states four counts, and three of them are from a smaller catalogue than the one in the tree. The fourth was wrong from the day it was written.

Where Said Code says
line 26, vocabulary table CAGES (18 entries) 28 � Object.keys(CAGES).length; the page itself says That is 28 cages at line 77, one table below the 18
line 27, vocabulary table MEDIA (53 entries) 90 � Object.keys(MEDIA).length; the page’s own §8 walks "all 90 media"
line 1018 2,128 models built from 827 distinct port shapes 2,159 models, 851 shapes
line 1025, transcript (2128 models, 23160 sockets, 827 distinct port shapes) (2159 models, 24006 sockets, 851 distinct port shapes)

Evidence is the test that prints that transcript line, run at this tree:

$ node test/faceplate-catalogue.test.js
    (2159 models, 24006 sockets, 851 distinct port shapes)
  ...
14 passed, 0 failed

So the indented transcript now reproduces exactly as printed. The 2,128 figure was accurate when #1611 corrected it from 2,121; the catalogue has since taken #1595, #1608, #1613 and #1617 (+31 models, +846 sockets, +24 shapes). The cage and medium counts drifted the same way, and the 18-vs-28 pair had been contradicting each other inside the page, which is why nobody caught it: the table was legible and the number in the last column was not read.

Docs-only: no engine, no test, no behaviour changes. Nothing was added to a guard — these are prose counts on a page with no test watching them, so the honest fix is the number, and the next person who grows the catalogue will find them stale again unless somebody writes that guard.

Guards at this commit: syntax-check 339 files OK; docs-show-commands 7/7; help-completeness 8/8; help-key-works-in-every-prompt 9/9; doc-catalog-counts 24/24; canonical-urls 52/52; faceplate-catalogue 14/14; check-control-bytes clean.

`docs/CONNECTORS.md` states four counts, and three of them are from a smaller catalogue than the one in the tree. The fourth was wrong from the day it was written. | Where | Said | Code says | |---|---|---| | line 26, vocabulary table | `CAGES` (18 entries) | 28 � `Object.keys(CAGES).length`; the page itself says *That is **28 cages*** at line 77, one table below the 18 | | line 27, vocabulary table | `MEDIA` (53 entries) | 90 � `Object.keys(MEDIA).length`; the page’s own §8 walks "all 90 media" | | line 1018 | **2,128 models built from 827 distinct port shapes** | 2,159 models, 851 shapes | | line 1025, transcript | `(2128 models, 23160 sockets, 827 distinct port shapes)` | `(2159 models, 24006 sockets, 851 distinct port shapes)` | Evidence is the test that prints that transcript line, run at this tree: ``` $ node test/faceplate-catalogue.test.js (2159 models, 24006 sockets, 851 distinct port shapes) ... 14 passed, 0 failed ``` So the indented transcript now reproduces exactly as printed. The 2,128 figure was accurate when #1611 corrected it from 2,121; the catalogue has since taken #1595, #1608, #1613 and #1617 (+31 models, +846 sockets, +24 shapes). The cage and medium counts drifted the same way, and the 18-vs-28 pair had been contradicting each other *inside the page*, which is why nobody caught it: the table was legible and the number in the last column was not read. Docs-only: no engine, no test, no behaviour changes. Nothing was added to a guard — these are prose counts on a page with no test watching them, so the honest fix is the number, and the next person who grows the catalogue will find them stale again unless somebody writes that guard. Guards at this commit: syntax-check 339 files OK; docs-show-commands 7/7; help-completeness 8/8; help-key-works-in-every-prompt 9/9; doc-catalog-counts 24/24; canonical-urls 52/52; faceplate-catalogue 14/14; check-control-bytes clean.
docs(CONNECTORS): the counts the page states are the ones the engine holds — 28 cages, 90 media, 2,159 models
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 17s
CI / Test (Node 18) (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Has been skipped
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
f702181ad4
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-16 06:48:48 +00:00
jaylouisw force-pushed docs/1116-0645 from f702181ad4
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 17s
CI / Test (Node 18) (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Has been skipped
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
to 57733a699b
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 14s
CI / Test (Node 18) (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Has been skipped
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
2026-11-16 06:48:51 +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!1621
No description provided.