# Meridian v1 code review

These are manual review findings, not objective model scores. The reference was written by the reviewer and then repaired; no independent/blind review is claimed.

## Qwen original

- Confirmed runtime failure: `partEls` values are objects containing `{layer, part, front, back}`, but `rotSVG` dereferences `part.dataset.layer`. The first render throws before scheduling its next frame. This halts the clock, gear animation, and visible rotation updates. Browser console and unchanged assembly transform confirm the impact.
- SVG builders are called twice for front/back faces with repeated IDs (`handHour`, `handMin`, `handSec`, gradients and coils). Document-level ID lookup updates only one matching element. This deserves a follow-up check after fixing the crash; it was not repaired in this experiment.
- Separate perpetual animation loops drive the movement and explosion. Their idle cost has not been measured.
- Component data and procedural geometry are separated sensibly. Keyboard and pointer handlers are present, but code presence is not proof that the interaction works: the stopped render loop makes that distinction visible here.
- No external asset references found. JavaScript syntax check passed. Both results coexist with a runtime failure.

## Astra reviewed reference

- A single animation loop and centralized state simplify the interaction model.
- Four groups of reviewer edits are retained separately from the original artifact. These include bounds/layout corrections and rotation/selection fixes.
- Mechanism pause stops its motion but still runs requestAnimationFrame and updates real-time clock hands. Do not describe it as zero CPU or as a measured low-memory implementation.
- `prefers-reduced-motion` is read at startup; live OS preference changes are not observed.
- Geometry is a simplified illustration, not an accurate mechanical simulation. Realistic gear meshing and clockmaking accuracy were not validated.

## Not measured

Frame time, energy, peak RAM, touch hardware behavior, full accessibility compliance, and repeat-run reliability. No aggregate /100 score is warranted yet.

## Ornith assisted continuation

- Browser checks found no runtime errors during tested controls. Keyboard rotation, selection, explosion, and reset respond.
- Mobile width check fails: a 390px iframe has clientWidth 373 and scrollWidth 392. Desktop visual review also shows excess vertical spacing and overlapping hero/watch/information regions.
- `applyExplode` and `updateMovement` overwrite transforms on the same component nodes. Running animation discards each gear's individual explosion translation; pausing leaves the translation transform and resets its angle. This is a structural animation-state issue, beyond whether the toggle works.
- Explode button labels are reversed relative to the next action after toggling.
- The agent wrote a full file but then hit the six-minute continuation cap during its own review. That time limit is not a browser failure or a claim of completed agent verification.