The frontend interpreter recorded three library steps unlike the pure
runner, so three replayed programs differed from the model with no
difference in production:
- A detach leaves a nested copy's child plain when the loaded library no
longer has its main; the interpreter now records those children, as the
detach node does, and the oracle reads each as its main's child.
- A duplicate takes the reference inputs of the shapes it copies, so a
duplicate of a copy back on an older library holds that version.
- A library sync remembers its copies against the synced library as
loaded and the other libraries as accepted.
The detach node and the interpreter share `n/record-unlinked-children`.
Frontend generated tests replay the three programs.
Harness only; the benchmark is not run.
AI-assisted-by: claude-opus-5-5