* docs: adopt Collective Funds Guidelines 0.1

These were created by the Mocha maintainers with intent of being used for Mocha.

When #5197 is merged, do a follow up that adds the collective funds guidelines badge to the README

* Adding Collective Funds Guidelines badge

* Fix npm scripts on Windows

* Add prettier to Knip's ignore list

* use double quotes instead of removing quotes

* Fix tests for compatibility with Node ^22.7

--experimental-detect-module is default in Node 22.7 and later

* At least they pass...

* Format and cleanup new test

* Cleanup for fun

* Add newline for style

#5227)

* Format html.js

* Remove newlines between JSDoc comments and their symbols

* (temp) update template.html to run tests

* Color the stat result icon and text based on root suite result

* (temp) add template fail and template pass

* On first test fail, add fail indicator to stats

* Remove extra newline

* Format mocha.css with Prettier

* Make pass icon color accessible

* Cleanup mocha.css var names

* Restore template to main

* Remove thirteen-year-old comment

440e38c

* Revert "Format html.js"

This reverts commit 8552a91.

* Revert "Restore template to main"

This reverts commit 854ab12.

* Color passes and failures count as well

* Cleanup stats variables to consts

* Fix stats not updating on root suite end

* Revert "Remove extra newline"

This reverts commit 27a7958.

* Restore newlines :(

* Restore newlines for real

* Reapply "Remove extra newline"

This reverts commit c43bffe.

* Revert "Format mocha.css with Prettier"

This reverts commit 0898ed5.

* indent to 5, not 6 chars in mocha.css

* Re-add newline in mocha.css

* Reapply "Restore template to main"

This reverts commit 714ee15.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

- Add '^' and ' ' for a suite link so that a link for `Case1` won't hit `Case10 test1`.
- Add '^' and '$' for a test link so that a link for `CSS` won't hit `should fix invalid CSS`.

* fix: report syntax errors in package.json (fixes: #5141)

* fix(tests): incorrect test (should use existing result)

Since `readFileSync` is only stubbed `onFirstCall` we get a different answer
the second time around which is probably Not What You Want.  But also we
*already checked that config = false*.  So you could just remove this
test, it does nothing useful.

* fix: separate read and parse errors

* fix: clarify invalid JSON

Co-authored-by: Josh Goldberg ✨ <[email protected]>

* fix(test): expect only a SyntaxError nothing else

---------

Co-authored-by: Josh Goldberg ✨ <[email protected]>

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>