docs(CI): the local-checks block is a transcript again - prose moved out of the bash fence #1713
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!1713
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/1116-1915"
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?
docs/CI.md→ Running the same checks locally.What was untrue: the ```bash block was not a block of commands. It opened with
npm test, then carried the "Two suites are randomised on purpose…" paragraph and its two-item list inside the fence, then closed with the remaining four commands. Copied into a shell,Two suites are randomised on purpose, and both are seeded so a failure reproduces exactly:is executed as a command.Evidence the prose itself is right (so it was moved, not deleted):
test/property-validator.test.js:22-23— "a seeded PRNG … the seed is printed with every assertion message"; seeds 1..120 at line 105.test/fuzz-importer.test.js:147—for (let i = 0; i < 400; i++), asserted as "all 400 mutations were checked" at line 194.Fix: five typeable lines in the fence (
npm test,npm run syntax,npm run smoke,docker build -t pf .,npm run audit:ports— all present inpackage.jsonscripts), prose after the closing fence.Guards (before → after, none read CI.md, so identical): syntax-check 356 files OK; control-bytes clean; docs-show-commands 7 passed / 0 failed (51 forms, 102 commands, 60 refusals); help-completeness 8 passed / 0 failed. Fences in CI.md balanced (10 fence lines, 0 unbalanced).
Docs only — no engine change.
691d07622e1a695f78a1