docs(CLI): the no-form guard is twelve checks today, not the seven it shipped with #1770

Merged
jaylouisw merged 1 commit from docs/1117-0215 into main 2026-11-17 02:28:38 +00:00
Owner

docs/CLI.md, in the no spanning-tree portfast section, describes test/no-command-touches-only-what-it-names.test.js as "seven checks covering the four destructive no forms, the two forms that really do clear the priority, the nothing set answer, the help row, the three speed spellings, and both access-group sentences".

The file shipped from #1502 with seven tests (git show eb87fbd3:test/no-command-touches-only-what-it-names.test.js has 7 test( lines); #1543 took it to 11 with the channel-group cases, #1561 to 12 with the per-VLAN spanning-tree agreement, and #1619 kept it at 12. node test/no-command-touches-only-what-it-names.test.js now reports tests 12, and the doc's enumeration stops at the original three defects, so it reads as though the suite covers none of the LAG work.

The paragraph now says twelve, names the five later checks, and scopes the old-handler figure to the seven checks it was measured against (3 passed / 4 failed) instead of presenting it as a number for today's suite.

Guards: node scripts/syntax-check.js 369 files all OK; node scripts/check-control-bytes.js clean; node test/docs-show-commands.test.js 7 passed; node test/help-completeness.test.js 8 passed (98 advertised commands, 18 mechanisms, 16 show commands); node test/help-key-works-in-every-prompt.test.js 10 passed; node test/no-form-help-key.test.js 81 passed. Docs only, no code change.

`docs/CLI.md`, in the `no spanning-tree portfast` section, describes `test/no-command-touches-only-what-it-names.test.js` as "seven checks covering the four destructive `no` forms, the two forms that really do clear the priority, the `nothing set` answer, the help row, the three speed spellings, and both access-group sentences". The file shipped from #1502 with seven tests (`git show eb87fbd3:test/no-command-touches-only-what-it-names.test.js` has 7 `test(` lines); #1543 took it to 11 with the channel-group cases, #1561 to 12 with the per-VLAN spanning-tree agreement, and #1619 kept it at 12. `node test/no-command-touches-only-what-it-names.test.js` now reports `tests 12`, and the doc's enumeration stops at the original three defects, so it reads as though the suite covers none of the LAG work. The paragraph now says twelve, names the five later checks, and scopes the old-handler figure to the seven checks it was measured against (3 passed / 4 failed) instead of presenting it as a number for today's suite. Guards: `node scripts/syntax-check.js` 369 files all OK; `node scripts/check-control-bytes.js` clean; `node test/docs-show-commands.test.js` 7 passed; `node test/help-completeness.test.js` 8 passed (98 advertised commands, 18 mechanisms, 16 show commands); `node test/help-key-works-in-every-prompt.test.js` 10 passed; `node test/no-form-help-key.test.js` 81 passed. Docs only, no code change.
docs(CLI): the no-form guard is twelve checks, not the seven it shipped with
All checks were successful
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 34s
CI / Server smoke test (pull_request) Successful in 11s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Docker build (pull_request) Successful in 22s
CI / Arm auto-merge (pull_request) Successful in 5s
f883123678
jaylouisw force-pushed docs/1117-0215 from f883123678
All checks were successful
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 34s
CI / Server smoke test (pull_request) Successful in 11s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Docker build (pull_request) Successful in 22s
CI / Arm auto-merge (pull_request) Successful in 5s
to 13e54d2741
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
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 52s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Test (Node 22) (pull_request) Successful in 57s
CI / Arm auto-merge (pull_request) Successful in 14s
2026-11-17 02:26:46 +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!1770
No description provided.