Skip to content

docs(engine): remove stale test and deployment claims #36

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
edwardnewgate710 merged 2 commits into from
Sep 5, 2026
Merged

docs(engine): remove stale test and deployment claims #36

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
20fa976
docs(engine): remove stale test and deployment claims
hessiun710 Sep 4, 2026
cfe1555
Merge remote-tracking branch 'origin/main' into gemini/engine-readme-…
hessiun710 Sep 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions packages/engine/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ EngineTransport the only I/O seam (native subprocess in prod, fake in test
```

Pluggable seams: `EnginePlugin` (register engines), `AnalysisCache` (in-process LRU by
default; Redis/Postgres are future drop-ins), `EngineTransport`, `FenValidator`, `Clock`.
default; persistent backends like PostgreSQL implement this interface), `EngineTransport`, `FenValidator`, `Clock`.

## Key properties

Expand Down Expand Up @@ -71,5 +71,10 @@ npm test # tsc -p tsconfig.test.json && node --test dist-test/test/
npm run lint # tsc --noEmit
```

The test suite (51 tests) is hermetic. A real-engine "golden" test is env-gated and lands
with the deployable service (M14), along with distributed workers and authority wiring.
The package test suite is hermetic, exercising the full stack using `FakeEngineTransport`
and injectable clocks without requiring native engine binaries.

Real-engine integration is tested via environment-gated smoke tests in CI (under
`@chess-platform/api` with pinned Stockfish and Fairy-Stockfish binaries against a real database).
In production runtime wiring, the engine bridge powers bot play in the gateway and analysis
endpoints in the API. Distributed remote engine workers remain deferred.