Branch policy

Due to the nature of this fork (fast-moving/flakiness of many parts, including upstream stockfish, emscripten, wasm simd spec, etc...) and also in the hope of merging this back to the upstream, I decided to rebase commits on the upstream master frequently. I also change Github's default branch accordingly.

To make it easier to differentiate branches, I employ this branch naming convention:

emscripten-<rebase top of upstream commit>-<emsdk/emscripten version to be used>.

Currently, there exist following branches:

Branch	Detail
emscripten-76daa88c-2.0.11	First version. Upstream 76daa88c is a few commits before Stockfish 13. npm package is [email protected].
emscripten-237ed1ef-2.0.26	Upstream 237ed1ef is some commits after Stockfish 14. npm package is [email protected].
emscripten-1946a675-2.0.26	This includes another new NNUE architecrue update after Stockfish 14. npm package is [email protected].
emscripten-1946a675.smolnet-2.0.26	On top of 1946a675, this version uses Sopel97's 4x smaller net. npm package is [email protected].
emscripten	Same as emscripten-76daa88c-2.0.11. I will keep this branch as it is since there exist some public URLs referencing this branch.
master	Same as upstream's master