25 checks · failures stay fixed
Protect the edge. Preserve the evidence.
Regression checks lock down atomic validation, task-error recovery, idle behavior, control flags, the no-WeakMap performance contract, every documentation target, local artwork, vanilla-test attribution, and deployment wiring.
8 core + 17 repository
All 25 Regression checks.
Core failure modes and repository evidence are kept separate so a broken edge never hides inside a broad success case.
Queue regressions · 8
- invalid add input rejects the entire batch atomically
- non-array contents replacement preserves pending work
- invalid contents members preserve the previous array
- a synchronous task failure is rethrown unchanged
- a synchronous task failure returns the queue to idle
- remaining work can resume after a task failure
- next on an empty queue is an idle no-op
- clear preserves caller-controlled queue flags
Repository and documentation regressions · 17
- documentation remains split into fifteen focused pages
- documentation pages retain their required short contracts
- every documentation page links to the Playground route
- every local page target and fragment resolves
- documentation loads no remote runtime or content assets
- README begins with the generated local repository header
- README links every primary focused documentation route
- repository header remains a responsive panoramic PNG
- vanilla-test artwork remains a substantial panoramic PNG
- repository and site visibly credit vanilla-test
- Testing page publishes all four non-overlapping layers
- package scripts expose every test layer independently
- vanilla-test and native coverage load every core layer
- Playground page and controller retain safe module wiring
- CI and Pages retain all delivery gates and curated assets
- modern queue runtimes do not restore WeakMap state
- project remains JavaScript-only
Run this layer
Regression only, or documentation alone.
npm run test:regression
npm run test:docs