v0.3.57 — Smaller responses and release gates
Why this matters
Large repeated lifecycle payloads made normal MCP calls expensive to read and expensive to pass through an agent. At the same time, a release could be tagged without a reliable, repeatable check that the required workflows had run for that exact commit.
What this gives you
- Scene open, scene snapshot, and Game View configuration return the useful operation facts first instead of repeating the same lifecycle block.
- Console tails have a deterministic byte budget, so one noisy log cannot consume the whole response.
- Oversized output explains what was dropped and points to the compact grep route for deeper inspection.
- Refresh timeouts now say whether Unity was still importing, compiling, busy, or simply missing final idle confirmation, with a concrete next action.
- The release checklist is backed by Integration Tests, Unity Package CI, and Discovery Checks for the exact release commit, plus a tag gate that rechecks them.
Validation
- Host, site, Unity package, lifecycle, and release-gate contracts were exercised for this release.