KnightStackSys · Oct 9, 2026 · Oct 9, 2026 · Oct 9, 2026 · Oct 9, 2026 · Oct 9, 2026
diff --git a/.github/workflows/c-cpp.yml b/.github/workflows/c-cpp.yml
@@ -27,10 +27,12 @@ jobs:
           - name: 🐧 Linux GCC
             os: ubuntu-latest
             configure_args: -DCMAKE_BUILD_TYPE=Release
+            binary: build/ironphoenix
 
           - name: 🪟 Windows MSVC
             os: windows-latest
             configure_args: -A x64
+            binary: build/Release/ironphoenix.exe
 
     steps:
       - name: 📥 Checkout
@@ -49,6 +51,11 @@ jobs:
       - name: 🧪 Run tests
         run: ctest --test-dir build -C Release --output-on-failure
 
+      - name: 🖥️ Web GUI integration against compiled engine
+        env:
+          IRONPHOENIX_NATIVE_ENGINE: ${{ matrix.binary }}
+        run: node --test web/tests/native-engine.test.js
+
       - name: 🧠 Validate PhoenixNet Python
         if: ${{ hashFiles('nnue/*.py') != '' }}
         run: python -m py_compile nnue/model.py nnue/train.py nnue/export.py
diff --git a/.github/workflows/web-ui.yml b/.github/workflows/web-ui.yml
@@ -0,0 +1,25 @@
+name: IronPhoenix Web UI
+on:
+  push:
+    branches: [main]
+    paths: ["web/**", ".github/workflows/web-ui.yml"]
+  pull_request:
+    branches: [main]
+    paths: ["web/**", ".github/workflows/web-ui.yml"]
+  workflow_dispatch:
+
+jobs:
+  test-web:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '22'
+      - name: Check browser and server JavaScript syntax
+        run: |
+          node --check web/app.js
+          node --check web/server.js
+          node --check web/notation.js
+      - name: Test parser, local API and engine bridge
+        run: node --test web/tests/*.test.js
diff --git a/CMakeLists.txt b/CMakeLists.txt
@@ -24,15 +24,18 @@ add_library(ironphoenix_core STATIC
     src/tt.cpp
     src/eval.cpp
     src/nnue.cpp
+    src/tuning.cpp
     src/search.cpp
     src/multipv.cpp
     src/fen.cpp
     src/movegen.cpp
     src/preft.cpp
     src/uci.cpp
     include/ironphoenix/eval.hpp
+    include/ironphoenix/search_stack.hpp
     include/ironphoenix/lmr.hpp
     include/ironphoenix/nnue.hpp
+    include/ironphoenix/tuning.hpp
 )
 
 add_library(IronPhoenix::Core ALIAS ironphoenix_core)
@@ -173,7 +176,25 @@ if(IRONPHOENIX_BUILD_TESTS)
     target_compile_features(ironphoenix_property PRIVATE cxx_std_20)
     add_test(NAME ironphoenix_property COMMAND ironphoenix_property)
 
-    set_target_properties(ironphoenix_smoke ironphoenix_property PROPERTIES
+    add_executable(ironphoenix_search_stack tests/search_stack.cpp)
+    target_link_libraries(ironphoenix_search_stack PRIVATE IronPhoenix::Core)
+    target_compile_features(ironphoenix_search_stack PRIVATE cxx_std_20)
+    add_test(NAME ironphoenix_search_stack COMMAND ironphoenix_search_stack)
+
+    add_executable(ironphoenix_mate_stop tests/mate_stop.cpp)
+    target_link_libraries(ironphoenix_mate_stop PRIVATE IronPhoenix::Core)
+    target_compile_features(ironphoenix_mate_stop PRIVATE cxx_std_20)
+    add_test(NAME ironphoenix_mate_stop COMMAND ironphoenix_mate_stop)
+
+    add_executable(ironphoenix_reverse_futility tests/reverse_futility.cpp)
+    target_link_libraries(ironphoenix_reverse_futility PRIVATE IronPhoenix::Core)
+    add_test(NAME ironphoenix_reverse_futility COMMAND ironphoenix_reverse_futility)
+
+    add_executable(ironphoenix_attacking_pieces tests/attacking_pieces.cpp)
+    target_link_libraries(ironphoenix_attacking_pieces PRIVATE IronPhoenix::Core)
+    add_test(NAME ironphoenix_attacking_pieces COMMAND ironphoenix_attacking_pieces)
+
+    set_target_properties(ironphoenix_smoke ironphoenix_property ironphoenix_search_stack ironphoenix_mate_stop ironphoenix_reverse_futility ironphoenix_attacking_pieces PROPERTIES
         FOLDER "Tests"
     )
 endif()

diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -0,0 +1,156 @@
+# 🔥 IronPhoenix Code of Conduct
+
+## 🛡️ Our Commitment
+
+IronPhoenix is an open-source project focused on building and improving a high-performance four-player chess engine.
+
+We want the project to be a place where people can collaborate, experiment, learn, review code, test ideas, and disagree constructively. Everyone participating in the IronPhoenix community is expected to help maintain a respectful, technical, and welcoming environment.
+
+This Code of Conduct applies to contributors, maintainers, reviewers, testers, users, and anyone participating in project spaces.
+
+---
+
+## 🤝 Expected Behavior
+
+Participants are expected to:
+
+- Communicate respectfully and professionally.
+- Critique ideas, code, benchmarks, and technical decisions rather than attacking people.
+- Support technical claims with testing, measurements, examples, or reasoning when practical.
+- Give constructive code-review feedback that helps improve the project.
+- Be patient with contributors of different experience levels.
+- Ask questions when requirements, rules, benchmarks, or engine behavior are unclear.
+- Respect the complexity of four-player chess and recognize that reasonable technical approaches may differ.
+- Keep discussions focused on the project when using project issue trackers, pull requests, discussions, and other development channels.
+- Respect private information, credentials, unpublished work, and security-sensitive information.
+- Give appropriate credit for code, research, testing, ideas, and other contributions.
+
+---
+
+## 🚫 Unacceptable Behavior
+
+The following behavior is not acceptable:
+
+- Harassment, threats, intimidation, stalking, or targeted abuse.
+- Discrimination or derogatory comments based on personal characteristics or identity.
+- Personal insults, name-calling, humiliation, or repeated hostile behavior.
+- Sexual harassment or unwanted sexual attention.
+- Publishing another person's private information without permission.
+- Deliberately disrupting project discussions, reviews, testing, or development.
+- Spamming issues, pull requests, discussions, or other project channels.
+- Knowingly submitting malicious code, credential stealers, destructive payloads, or other harmful content.
+- Misrepresenting benchmark results, test results, authorship, or contribution history.
+- Plagiarizing code or knowingly violating software licenses.
+- Using the project community to organize harassment or abuse elsewhere.
+
+Strong disagreement about engine design, pruning techniques, evaluation, move ordering, architecture, benchmarks, or performance is allowed. Personal attacks are not.
+
+---
+
+## 🧪 Technical Discussions and Engine Testing
+
+IronPhoenix development depends heavily on experimentation and strength testing.
+
+When discussing engine changes:
+
+- Treat Elo estimates, SPRT results, NPS, node counts, depth, and benchmark results as evidence rather than personal status.
+- Clearly distinguish measured results from predictions or speculation.
+- Prefer isolated testing when evaluating search heuristics or evaluation terms.
+- Negative test results are useful information and should not be mocked or hidden.
+- Reproducible tests are encouraged whenever practical.
+- Do not knowingly falsify, selectively alter, or misrepresent testing data.
+- Respect existing project behavior and comments when modifying established engine code unless the change intentionally replaces them.
+
+A failed experiment is not a failed contribution. Good testing that shows an idea loses strength can still help the project.
+
+---
+
+## 🧑‍💻 Pull Requests and Code Review
+
+When opening or reviewing a pull request:
+
+- Keep the change focused when possible.
+- Explain what the change is intended to accomplish.
+- Include relevant testing information when available.
+- Avoid unrelated rewrites in a feature-specific pull request.
+- Review the implementation, not the contributor.
+- Be willing to revise code when review identifies correctness, performance, maintainability, or testing concerns.
+- Do not pressure maintainers to merge an experimental change before it has received appropriate review or testing.
+
+Maintainers may request that experimental engine-strength changes remain on separate branches until testing is complete.
+
+---
+
+## 🌐 Scope
+
+This Code of Conduct applies in official IronPhoenix project spaces, including:
+
+- GitHub repositories
+- Issues
+- Pull requests
+- Discussions
+- Testing and benchmarking channels
+- Project documentation
+- Other communication spaces officially used for IronPhoenix development
+
+It may also apply when someone is publicly representing the IronPhoenix project.
+
+---
+
+## 🚨 Reporting a Problem
+
+If you experience or witness behavior that violates this Code of Conduct, report it to the IronPhoenix repository owner or project maintainers through an appropriate private GitHub contact method when possible.
+
+Please include relevant information such as:
+
+- What happened
+- Where it happened
+- When it happened
+- Links, screenshots, or other evidence when available
+- Any additional context that may help the maintainers understand the situation
+
+Reports will be reviewed as fairly and confidentially as practical.
+
+Do not knowingly submit false or retaliatory reports.
+
+---
+
+## ⚖️ Enforcement
+
+Project maintainers are responsible for interpreting and enforcing this Code of Conduct.
+
+Depending on the severity and history of the behavior, maintainers may take actions including:
+
+1. **Correction** — A private or public request to change inappropriate behavior.
+2. **Warning** — A formal warning that continued behavior may result in further action.
+3. **Temporary restriction** — Temporary limits on participation in issues, pull requests, discussions, or other project spaces.
+4. **Permanent ban** — Permanent removal from participation in IronPhoenix project spaces.
+
+Severe behavior may result in immediate restriction or removal without first using every intermediate step.
+
+Enforcement decisions should be based on protecting the project community and maintaining a productive development environment.
+
+---
+
+## 🧭 Maintainer Responsibilities
+
+Maintainers are expected to:
+
+- Apply this Code of Conduct consistently and in good faith.
+- Avoid using enforcement as retaliation for technical disagreement.
+- Distinguish heated technical debate from harassment or abuse.
+- Protect confidential reports where practical.
+- Remove, edit, or reject comments, commits, code, issues, or contributions that violate this Code of Conduct.
+- Prioritize the safety and long-term health of the project community.
+
+---
+
+## 🔥 Project Values
+
+IronPhoenix values:
+
+**Performance. Correctness. Experimentation. Reproducibility. Respect.**
+
+We can disagree aggressively about algorithms while still treating each other well.
+
+♟️ **Build strong code. Test it honestly. Help the engine improve.**
diff --git a/README.md b/README.md
@@ -1,11 +1,13 @@
-# 🔥 IronPhoenix
+<p align="center">
+  <img src="bin/iron-phoenix.png" alt="Iron Phoenix logo" width="700">
+</p>
+
+# 💻 IronPhoenix
 
 **IronPhoenix** is a high-performance **4-player chess Teams engine** written in modern C++20.
 
 It is built around the chess.com-style 4PC cross board, team-aware search, fast move generation, handcrafted evaluation, and **PhoenixNet**, a purpose-built NNUE evaluator for four-player Teams chess.
 
-> ❤️ Built with love by Nick.
-
 ---
 
 ## ♟️ What IronPhoenix Plays
@@ -32,10 +34,14 @@ IronPhoenix includes a modern alpha-beta search stack designed specifically for
 
 - Negamax / PVS-style search
 - Quiescence search
+- Aspiration Windows
 - Transposition tables
 - History-based move ordering
 - Static Exchange Evaluation (SEE)
 - Late Move Reductions (LMR)
+- Late Move Pruning (LMP)
+- Null Move Pruning (NMP)
+- History Move Pruning (HMP)
 - Search pruning and reductions
 - Iterative deepening
 - Principal variation reporting
@@ -124,6 +130,31 @@ cmake --build out\build\x64-release --target ironphoenix_dataset
 
 ---
 
+## 🖥️ Local web analysis GUI
+
+Run IronPhoenix through a **localhost-only** web interface with a
+14×14 4-player Teams board, legal move input, engine PV arrows,
+MultiPV scores, and FEN4 / four-player PGN4 game loading.
+
+1. Build the native `ironphoenix` engine in Release mode.
+2. Copy the engine executable into the [`web/`](web/) folder, next to
+   `server.js` (on Windows: `web/ironphoenix.exe`). Copy
+   `ironphoenix.nnue` there too if desired.
+3. With Node.js 18+ installed, run:
+
+   ```cmd
+   cd web
+   node server.js
+   ```
+
+4. Open **http://127.0.0.1:8765** in your browser.
+
+On Windows you can also double-click `web/start.bat`. No npm dependencies
+are required. For supported notation, screenshots-independent setup and
+test instructions, read [`web/README.md`](web/README.md).
+
+---
+
 ## ▶️ Running the Engine
 
 Launch the engine executable and enter UCI-style commands:

diff --git a/bin/.gitkeep b/bin/.gitkeep
@@ -0,0 +1 @@
+
diff --git a/bin/iron-phoenix.png b/bin/iron-phoenix.png
diff --git a/docs/CNAME b/docs/CNAME
@@ -0,0 +1 @@
+iphoenix.art
diff --git a/docs/README.md b/docs/README.md
@@ -0,0 +1,24 @@
+# IronPhoenix website
+
+GitHub Pages serves this folder directly. There is no compilation step, package manager, or generated output to publish. All runtime assets are local. `index.html` contains the content, `assets/site.css` contains the theme, and `assets/site.js` provides progressive enhancements (mobile navigation, command copying, and a decorative board). The engine itself does not run in the browser.
+
+## Preview
+
+From the repository root, with Python 3 installed:
+
+```sh
+python -m http.server 8080 --directory docs
+```
+
+Open http://localhost:8080. Check desktop and mobile layouts, the navigation button and Escape key, command copying, and keyboard focus. Content, links, and navigation remain available with JavaScript disabled; the decorative board requires JavaScript. Clipboard buttons appear only in secure contexts where the Clipboard API exists.
+
+## Maintenance
+
+- Keep engine claims and commands aligned with the root README and `nnue/README.md`.
+- Bulma **1.0.4** is vendored from `https://cdn.jsdelivr.net/npm/bulma@1.0.4/css/bulma.min.css` in `assets/vendor/`. Its MIT license is included. To upgrade, replace the pinned CSS and license, update the link in `index.html`, and review both layouts.
+- The system font stack and SVG mark require no external requests.
+- Preserve `CNAME` exactly: it configures the existing custom domain, `iphoenix.art`.
+- Keep the existing Pages deployment source and workflows. Changes here require no new workflow or hosting service.
+- Relative asset links support both the custom domain and repository subpaths. If the domain changes, update the canonical and Open Graph URLs as well as the Pages domain setting.
+
+Before a PR, run `git diff --check`, serve `docs/`, and verify local assets, section anchors, the 160-square board, keyboard navigation, and narrow-screen overflow. Only website files should change.
diff --git a/docs/assets/phoenix.svg b/docs/assets/phoenix.svg