Project history. This is an internal planning or implementation ledger, kept for reference. For using the engine, start with Getting started.
Journey50 implementation and verification
Completed locally on 2026-10-22. All fifty items in the implementation roadmap are implemented and integrated, including API migrations and presentation improvements across all fifteen catalog demos. Fifty implementation agents were launched, followed by focused integration work. Capacity failures were recovered; task 47's surviving implementation was independently checked and adopted by the parent. The original task outcomes remain in the local orchestration ledger.
What changed
- Engine entry points: a small facade prelude, runnable quickstart, renderer-independent
Applifecycle, sharedGameSession, and checked fixed timing make startup, updates, interpolation, pause and restart explicit. - Game authoring: typed input handles, tick snapshots, camera snap/reset, audio fades, accessible feedback, responsive HUD helpers and checked meshes reduce repeated host code and surface invalid input early.
- Systems and debugging: checked assets, recoverable saves, replay mismatch details, safe ECS multi-entity access, system-order diagnostics, typed resource initialization, event backpressure, guarded state transitions, physics query filters, contact lifecycle fixes, named RNG streams and scene hierarchy tools. Scene errors include repair context; diagnostics can be exported as JSON.
- Developer workflow: one local command, an environment doctor, runnable 2D and 3D scaffolds, a coding-agent guide, a migration cookbook, catalog audits, and a validation runner with machine-readable results and CI integration.
- Browser hosts: cancellable loading and retry, suspension and graphics recovery, and an accessible catalog. Custom game menus retain the controls editor without drawing a second pause banner.
The resolved Cargo graph remains first-party/std-only across all 28 packages, features and targets. Existing async renderer games, host entry points and serialized formats remain supported.
Demo migrations
Every catalog demo now uses the shared session contract where appropriate. Simulation-specific phases remain authoritative; local overlays preserve network/replay progression where required.
| Demo | Main migration and presentation work |
|---|---|
| Emberline | Start/pause/retry flow, checkpoint labels, jump/landing feedback, reset and camera cleanup. |
| Neon Swarm | Tick-based input, wave countdowns, attack warnings, hit markers and consistent retries. |
| Pocket Rally | Pausable race countdown, recovery and restart flow, measured HUD spacing at narrow widths. |
| Salvage Pinball | Shared lifecycle, clearer ball/round feedback and a single pause presentation. |
| Orchard Guard | Build/wave/pause flow, checkpoint saves, usable keyboard controls and bounded pause-card text. |
| Marble Run | Pausable countdown excluded from trial time, course resumption and checkpoint/recovery feedback. |
| Dune Skimmer | Shared timing, boost/overheat feedback, gate progress and clean recovery controls. |
| Crystal Cavern | Session-driven menus and reset flow, preserving exploration and interaction. |
| Siege Foundry | Session-driven controls, accepted-action feedback and readable ammo/status layout. |
| Sky Courier | Start/pause/retry flow, flight feedback and readable wrapped menu text. |
| Strike | Session-aware host menus with pointer-capture, replay and authoritative-tick handling. |
| 2D Physics Lab | Shared lifecycle and clear pause/reset/status controls. |
| 3D Physics Lab | Shared lifecycle, pause/reset controls and single-step behavior while paused. |
| Courtyard | Session-aware native/browser adapters and progress-preserving pause/resume. |
| Orbit Breaker | Session-aware native/browser adapters, input handling and consistent pause/retry presentation. |
Validation evidence
The full runner completed 54 commands: 54 passed, zero failed or skipped:
python3 -B scripts/validate.py --mode full --require-complete \
--report target/journey-50/final-validation.jsonIts report and per-command logs are local artifacts under target/journey-50/. The numbered implementation receipts are under target/journey-50/receipts/. The report covers:
- 1,132 Rust tests and doctests passed across 107 test groups; 14 tests were ignored by the ordinary run. All 12 GPU tests were run separately and passed on this Linux graphics environment.
- Workspace checks, strict Clippy, formatting and the dependency audit passed.
- All fifteen demos built in release mode for native and Wasm targets. Native smoke runs produced successful captures for all fifteen; Courtyard and Orbit Breaker use their software/headless capture paths.
- Actual-Wasm suites passed for UI, input, audio, effects, animation, content, materials, saves, replays, course progression and multiplayer. Native UDP authority, the WebSocket gateway and two Wasm clients passed integration.
- Python tooling and JavaScript host suites passed, including loader failure, lifecycle recovery, input and session-adapter regressions. Rustdoc and the generated site's link, search and player checks passed.
Additional integration checked both generated project templates: each passed three gameplay tests and one doctest, a release Wasm build, and 296 frames of Node/Wasm host integration. Eighteen documentation examples and 78 local links were checked. Live browser checks covered all fifteen demos, with desktop interaction and selected narrow layouts, pointer capture, controls, pause, resume and restart. Actual WebGL loss/restoration preserved Emberline's paused state. No application console errors were observed in those checks.
The last Orchard Guard text-layout adjustment was checked after the full run with targeted Rust tests and strict Clippy, fresh native/Wasm builds, the actual Wasm UI suite, a native capture and a live browser pause-card inspection. The final documentation and staged site were rebuilt and checked afterward.
Limits of this verification
These results cover the available Linux and desktop browser environment. Physical touch/controllers, Windows/macOS/mobile runtime behavior, prolonged performance, listening quality, every campaign to completion, and live WebRTC peer play were not established by this pass. Browser work ran alongside build and preview activity, so it does not establish a stable frame-rate target. Narrow desktop viewports are layout checks, not physical-device certification.
For use and further development, start with the quickstart, migration cookbook, coding-agent guide, and validation command guide.