ferravex
GitHub

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

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.

DemoMain migration and presentation work
EmberlineStart/pause/retry flow, checkpoint labels, jump/landing feedback, reset and camera cleanup.
Neon SwarmTick-based input, wave countdowns, attack warnings, hit markers and consistent retries.
Pocket RallyPausable race countdown, recovery and restart flow, measured HUD spacing at narrow widths.
Salvage PinballShared lifecycle, clearer ball/round feedback and a single pause presentation.
Orchard GuardBuild/wave/pause flow, checkpoint saves, usable keyboard controls and bounded pause-card text.
Marble RunPausable countdown excluded from trial time, course resumption and checkpoint/recovery feedback.
Dune SkimmerShared timing, boost/overheat feedback, gate progress and clean recovery controls.
Crystal CavernSession-driven menus and reset flow, preserving exploration and interaction.
Siege FoundrySession-driven controls, accepted-action feedback and readable ammo/status layout.
Sky CourierStart/pause/retry flow, flight feedback and readable wrapped menu text.
StrikeSession-aware host menus with pointer-capture, replay and authoritative-tick handling.
2D Physics LabShared lifecycle and clear pause/reset/status controls.
3D Physics LabShared lifecycle, pause/reset controls and single-step behavior while paused.
CourtyardSession-aware native/browser adapters and progress-preserving pause/resume.
Orbit BreakerSession-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.json

Its 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:

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.