Mouse oracle must track windows and cleanup through runtime wrappers #47

The full EigenScript consumer wave fails in the mouse oracle when the runtime is launched through the counting wrapper. On dynamics main 0d5f3ddaca87df6e7e6e97b88fdb439e264d1558, the font-atlas step ends with ERROR mouse oracle: app exited rc0, followed by the wrapper's missing-check diagnostic. The preceding physics and UI trajectory checks pass.

The runtime wrapper waits for a child executable so it can record its exit status. start_app() therefore returns the wrapper PID, while wait_for_window() requires the X window to belong to that exact PID. The real runtime child owns the window. The finite atlas exits normally before the test finds it. The bitmap-font fallback warning is expected and is not established as the cause.

This is a launch-ownership gap in the test harness following PR #46. Its direct-launch validation does not cover a non-exec proxy. The observed wave uses EigenScript candidate 96bbbb543fdbfe01e809eee09e7c67986085ed1d; this report does not establish a runtime regression.

Acceptance:

• Support both direct execution and a non-exec counting wrapper while retaining visible, exact-title window matching and verified ownership.
• Refuse unrelated windows and terminate/reap only the launched process family, including children when the launcher exits.
• Preserve all 16 interaction checks, the three real fault controls, pixel thresholds, and bounded waits.
• Show the current wrapper failure, then validate the fix with direct and wrapped launches and owned-process cleanup. Run normal CI and the complete consumer wave before claiming integration acceptance.

Local evidence is retained in release-blockers-20261003/1590-consumer-96-logs/run.hq9p9G/dynamics.log. The ongoing wave remains failed; its other rows are still being collected.