feat(runner): redesign the interactive page, with an Appearance panel accessibility themes and a tour of tripwire

README.md

@@ -20,7 +20,9 @@ The assertion side offers both `assert.*` functions and a Chai-style `expect(x).
 dependencies to a minimum so that a dependency update elsewhere cannot break your test run -- which
 is how the project started, when the frameworks we tested Worker code with stopped working.
 
-**New here?** Read [Why tripwire](https://nevware21.github.io/tripwire/why-tripwire.html) for what is automatic, what is fast, how it
+**New here?** See [Tripwire in action](https://nevware21.github.io/tripwire/tour.html) -- tripwire's own suite run once on node, in
+Chrome and in a web worker, with coverage and the interactive browser page -- then read
+[Why tripwire](https://nevware21.github.io/tripwire/why-tripwire.html) for what is automatic, what is fast, how it
 compares with Mocha, Karma, Jest and Vitest, and when it is not the right tool. Coming from one of
 those? There is a [migration guide](#documentation) for each.
 

docs/README.md

@@ -14,6 +14,9 @@
 
 ### Documentation
 
+- [Tripwire in action](tour.md) - tripwire's own suite run once on node, in Chrome and in a web
+  worker, coverage from the command line, and the interactive browser page, with screenshots of
+  each
 - [Why tripwire](why-tripwire.md) - what is automatic across node, browser and worker, what is
   fast, how it compares with Mocha, Karma, Jest and Vitest, and when not to use it
 - [Performance](performance.md) - the runner's mechanisms, measured benchmark results against