docs(simulation): no spanning-tree exists - the doc said it did not #2061

Merged
jaylouisw merged 1 commit from docs/1119-0047 into main 2026-11-19 02:39:40 +00:00
Owner

docs/SIMULATION.md §2.4 (spanning tree) said STP cannot be disabled bracketed by a false fact: "show spanning-tree exists, no spanning-tree does not".

The console accepts no spanning-tree: it is declared in engine/cli.js:697 ({ modes: ["config"], match: ["spanning-tree"], syntax: "no spanning-tree", effect: "clears the bridge priority" }) and answered by the shared spanning-tree handler. On a switch it prints No bridge priority set: the device is using the default 32768, and after spanning-tree priority 4096 it prints Bridge priority cleared (was 4096), back to the default 32768. docs/CLI.md documents the same line (#1502, "no spanning-tree … touch the priority").

The conclusion the row was making - STP runs on every l2-forward box and nothing turns it off - is still true; only the supporting claim was wrong. The row now says what the command does and cites where it is defined.

Guards unchanged: syntax-check 430 files OK; docs-cli-transcript 4, docs-show-commands 7 (59 forms / 118 commands), help-completeness 8 (102 rows), no-form-help-key 81 - all pass before and after.

`docs/SIMULATION.md` §2.4 (spanning tree) said STP cannot be disabled bracketed by a false fact: "`show spanning-tree` exists, `no spanning-tree` does not". The console accepts `no spanning-tree`: it is declared in `engine/cli.js:697` (`{ modes: ["config"], match: ["spanning-tree"], syntax: "no spanning-tree", effect: "clears the bridge priority" }`) and answered by the shared spanning-tree handler. On a switch it prints `No bridge priority set: the device is using the default 32768`, and after `spanning-tree priority 4096` it prints `Bridge priority cleared (was 4096), back to the default 32768`. `docs/CLI.md` documents the same line (#1502, "`no spanning-tree` … touch the priority"). The conclusion the row was making - STP runs on every `l2-forward` box and nothing turns it off - is still true; only the supporting claim was wrong. The row now says what the command does and cites where it is defined. Guards unchanged: syntax-check 430 files OK; docs-cli-transcript 4, docs-show-commands 7 (59 forms / 118 commands), help-completeness 8 (102 rows), no-form-help-key 81 - all pass before and after.
docs(simulation): STP cannot be turned off, but no spanning-tree does exist - it clears the priority
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 12s
CI / Server smoke test (pull_request) Successful in 13s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 22) (pull_request) Successful in 59s
CI / Test (Node 20) (pull_request) Successful in 59s
CI / Test (Node 18) (pull_request) Successful in 1m4s
CI / Arm auto-merge (pull_request) Successful in 3s
2d0dc86383
forgejo-actions force-pushed docs/1119-0047 from 2d0dc86383
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 12s
CI / Server smoke test (pull_request) Successful in 13s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 22) (pull_request) Successful in 59s
CI / Test (Node 20) (pull_request) Successful in 59s
CI / Test (Node 18) (pull_request) Successful in 1m4s
CI / Arm auto-merge (pull_request) Successful in 3s
to 527e010a05 2026-11-19 00:56:43 +00:00
Compare
jaylouisw force-pushed docs/1119-0047 from 527e010a05 to 4fd196abe6
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 4s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 18) (pull_request) Successful in 1m2s
CI / Test (Node 20) (pull_request) Successful in 1m8s
CI / Test (Node 22) (pull_request) Successful in 1m7s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-19 02:10:35 +00:00
Compare
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 02:20:27 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
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!2061
No description provided.