Files
VibemakerSandbox/app/test/fixtures/microduck
chenlin fa089d5f0c feat: release v0.2 multi-robot simulator
Add declarative robot packages, shared simulation lifecycle and Microban ONNX/PD walking with independent head control.

Unify comic UI and chase camera; default robot packages to a 4.5m arena with real collision walls. Include regression tests, asset provenance/licenses and verification evidence.
2026-10-28 14:00:26 +08:00
..

Accepted Microduck regression baselines

These nine trajectories were generated from original source commit 44d3681726468bdd00e88241894d5faa53e3c63e, before changing physics / policy semantics. The reference tree was independently materialized under /tmp from git archive, not taken from the newly refactored runtime.

Reference-only harness changes:

  1. Stop the background async control loop and allow single-owner explicit steps.
  2. Skip the title / BIOS render gates in test mode.
  3. Disable automatic ball spawning in the test-mode ceremony callback and park the ball, isolating policy trajectories from cosmetic randomness and collisions.
  4. Expose existing mode controls / observation / state for measurement.
  5. For the original wall-clock sit timer, wait 850 ms before the recorded physics interval. The refactored timer receives an equivalent explicit virtual 850 ms advance; the recorded input/target sequence is unchanged.

The first experimental harness did not fully isolate automatic ball spawning. Changing scene initialization then changed RNG consumption and revealed that problem. Those early fixtures were discarded. Accepted fixtures were regenerated from the independently archived original code with corrected isolation, then compared against the new implementation. No tolerances were widened to conceal that harness issue.

Environment: MuJoCo WASM 3.11.0, onnxruntime-web WASM 1.27.0, one thread, Chromium headless (Playwright 1.64.1), fixed initial state / commands.

Each case settles for 50 control ticks and records six snapshots spaced 25 ticks apart: qpos, qvel, ctrl, observation, lastAction, mode, recovery, simulation time. Cases: stand, walk, kick, sitstand, groundpick, roll, recovery, rollers, crouch. Comparisons are exact, including all recorded robot state; the parked ball is also present in each model state. They are representative trajectory windows, not proof that every possible long-running skill sequence is covered.

After the user-requested expansion to a 4.5 m default arena, this original-code oracle explicitly pins the original 3 m World through a test-only World response override. The production default remains 4.5 m, tested independently in bounded-world.spec.js. No accepted trajectory or tolerance was replaced to hide the intentional World-size change.

npm run test:regression reads these files. npm run baseline:record writes candidate files under ignored test-results/baseline-candidates/, never here. A baseline replacement needs an explicit reviewed cause and updated provenance. Node/native Python trajectories are not substituted for these WASM baselines.