Extend Stonehue — Pluggable Board-Game AI Engine

.github/dependabot.yml

@@ -0,0 +1,6 @@
+version: 2
+updates:
+  - package-ecosystem: github-actions
+    directory: "/"
+    schedule:
+      interval: weekly

.github/workflows/ci.yml

@@ -1,10 +1,14 @@
 name: CI
 
 on:
+  workflow_dispatch:
   push:
     branches: [main]
   pull_request:
 
+permissions:
+  contents: read
+
 jobs:
   test:
     name: Test
@@ -38,6 +42,13 @@ jobs:
       - name: Smoke test the engine
         run: |
           printf 'boardsize 9\nname\nversion\nplay b D4\ngenmove w\nshowboard\nquit\n' | ./build/stonehue.exe | grep -c '^='
+      - name: Smoke test search evidence
+        run: |
+          printf 'stonehue_iterations 0
+genmove b
+stonehue_search_info
+quit
+' | ./build/stonehue.exe | grep -q 'transposition-entries 1'
       - name: Smoke test SGF export
         run: |
           printf 'boardsize 9\nplay b D4\nplay w F4\nplay b D6\nprintsgf\nquit\n' | ./build/stonehue.exe | grep -q 'FF\[4\]'

CHANGELOG.md

@@ -6,7 +6,15 @@ This project uses semantic versioning.
 
 ## Unreleased
 
-No changes yet.
+Search depth slice.
+
+Added:
+
+- State-safe MCTS transposition statistics.
+- `stonehue_iterations` for exact search budgets.
+- `stonehue_search_info` for search table evidence.
+- Deterministic search, engine, and GTP tests.
+- A GTP session that demonstrates the table contract.
 
 ## 0.2.0 - 2026-08-03
 

CONTRIBUTING.md

@@ -0,0 +1,31 @@
+# Contributing
+
+Read `README.md` before changing the engine.
+Keep public APIs stable unless tests require a correction.
+
+## Checks
+
+Install SBCL and FiveAM.
+Run clean compilation.
+Run the FiveAM suite.
+Run the standalone build.
+
+```text
+sbcl --load scripts/check-clean.lisp
+sbcl --load scripts/run-tests.lisp
+sbcl --load scripts/build.lisp
+```
+
+Keep generated files out of commits.
+The repository ignores Lisp fasls and build output.
+
+## Changes
+
+Add deterministic tests for core behavior.
+Update the README when commands or behavior change.
+Update `ROADMAP.md` when roadmap work changes.
+Keep examples runnable through GTP.
+
+Use active voice in public documentation.
+Keep instructions short.
+Describe limitations without performance claims.