TODO: docs

squash this into the commit that first added all_tests.ts, we don't even
want to have a trace of it left

for the cli ones, we can simply iterate the filesystem relative our
location. for the web one, we determine it on launch and expose it as an
endpoint from the server which the client queries

cmd/mbf/internal/pkgserver/ui/jstest/jstest.ts

@@ -249,16 +249,22 @@ export class StreamReporter implements Reporter {
         case "success":
             this.#successes.push({ path, ...result });
             // NOTE: emojis are used instead of colored Unicode symbols as
-            // coloring isn't possible through all streams, which would make
+            // coloring isn't possible through all streams and there detecting
-            // this terminal-specific, and even in terminals and emulators
+            // if colors should be used is very difficult¹. Furthermore,
-            // thereof, it's very tedious to correctly detect whether one should
+            // ensuring reasonable contrast is retained on every possible theme
-            // use colors (https://no-color.org, https://bixense.com/clicolors,
+            // is difficult, with reverse video often being the only way, and
-            // https://force-color.org), ensure reasonable contrast is retained
+            // the Unicode characters might be too small to be immediately
-            // on every possible theme (using reverse video is often the only
+            // noticeable. Emojis have an upper hand in that they're more common
-            // way), and be immediately noticeable. Emojis have an upper hand in
+            // than obscure Unicode characters—which also means you're more
-            // that they're more common than obscure Unicode characters—which
+            // likely to have an emoji font but not a font with those
-            // also means you're more likely to have an emoji font but not
+            // symbols—and that they're double-width.
-            // a font with those symbols—and that they're double-width.
+            //
+            // ¹This necessitates checking if the stream is a TTY, checking if
+            //  $TERM is `dumb` when connected to a TTY, checking
+            //  https://no-color.org, https://bixense.com/clicolors, and
+            //  https://force-color.org, checking if setting the
+            //  ENABLE_VIRTUAL_TERMINAL_PROCESSING bit on the TTY works when on
+            //  on Windows, and doing something similar for Cygwin
             if (this.verbose) this.stream.writeln(`✅️ ${pathStr}`);
             break;
         case "failure":