v0.3.55 — Fail fast before Unity can do the wrong thing

Why this matters

A missing or invalid argument used to open Unity, start a bridge session, and only then fail. That wasted time and made a rejected call look like a compile or operation failure. Stale editor state could also look healthy.

What this gives you

• Required arguments are checked before Unity is opened or changed, and the response says clearly that nothing ran.
• Valid values and enum choices are shown in the refusal, so the next attempt is easier to fix.
• False values such as approve=false and zero values such as width=0 are treated as real inputs, not as missing data.
• A quiet Editor.log is no longer mistaken for a rotated log, so anchored searches keep working during normal idle periods.
• Dead editors and stale transport files no longer report ready; readiness now means a request can actually be delivered.
• UI scope truncation names scenes that were not reached instead of implying they were searched.

Validation

• Argument, liveness, transport, log-anchor, and UI-scope regressions are covered by the release test suite.