v0.3.58 — Know when Play Mode is really running

Why this matters

A healthy editor heartbeat does not prove that the game loop is advancing. An unfocused Unity editor can report Play Mode while frames are effectively stopped, and a compact project-action result could hide whether the requested mutation was actually evidenced.

What this gives you

• Status responses report frame progress and label Play Mode as advancing, throttled, paused, not playing, or unknown.
• When the editor is throttling the game loop, the response says why and how to recover.
• Project actions return a compact result with the action id, outcome, evidence summary, and mutation trust verdict; the full payload remains available when needed.
• Scenario runs can perform their own remediation flow instead of being blocked at dispatch by a compile problem.
• UI click results state exactly what EventSystem scope was checked, avoiding a misleading project-wide conclusion.
• Compiler diagnostics carry their trust level, and mutation-delta warnings link to the contract an action hook must satisfy.
• The direct Play Mode exit path remains available when compilation is broken, avoiding a recovery deadlock.

Validation

• Play Mode liveness, scenario gating, project-action, compiler-trust, and mutation-delta contracts are covered by host and Unity regression tests.