AKUNUR 3.0.0-alpha.2 VALIDATION REPORT

Automated validation completed
- JavaScript syntax checking passed for every .js file.
- Core/Lab smoke test passed on Node.js 22.16.0.
- Full-history and lightweight-Lab execution remained identical for 150 consecutive
  deterministic decisions; legal action sets and gameplay state matched after each action.
- Search previews were verified not to mutate the source state and to retain no history,
  logs or UI state.
- Full execution was verified to retain action logs and undo history; undo restored the
  preceding gameplay state and execution profile.
- Alpha.1 and alpha.2 authoritative core behaviour matched for 250 consecutive
  deterministic decisions when history, logs and version metadata were excluded.
- Browser-style UMD loading and compatibility bindings passed in an isolated JavaScript
  context; the legacy agent selected and applied a legal action.

Performance observations in the build environment
- Seeded Random-versus-Legacy, 100 decisions:
    alpha.1: 18.142 seconds
    alpha.2:  3.959 seconds
  This was approximately 4.6 times faster for the same seeded benchmark.
- Alpha.2 Random-versus-Legacy reached 400 decisions in 18.333 seconds while printing
  progress every 25 decisions.
- Alpha.2 Legacy-versus-Legacy reached 200 decisions in 17.250 seconds.

These timings are diagnostic rather than hardware-independent guarantees. Chris's
Windows laptop uses Node.js 24.18.1 and should be tested separately.

Manual checks still required
- Open web/index.html through a static server and perform the UI test checklist.
- Confirm board appearance and interaction match 3.0.0-alpha.1 / 2.10.5.
- Exercise corner capture, bonus Echo Piece placement, Echo Point capture and undo.
- Run the supplied profile command on the Windows laptop and compare timings.
