Repository navigation
v0.3.84 — Clearer validation results and fixed Game View clicks
v0.3.84 — Clearer Unity validation results and fixed Game View clicks
Why this matters
Unity could finish a test successfully while an empty error object made the compact response look like a failure. After a domain reload, an idle Editor could also lack the evidence needed to prove that a particular refresh had finished. Both situations made it harder to decide whether to continue, reconcile the result, or repeat work.
What changed
- Compact results ignore empty error content while preserving meaningful errors, failed operation or test verdicts, and nonzero process exits.
- In a scenario (a scripted validation run), a refresh is marked complete only when settled evidence matches that request. Missing identity remains explicitly unresolved; idle state alone cannot turn it into success. Summaries distinguish actions already applied from actions still pending, and separate execution time from settle waiting.
- uGUI clicks check the active Screen dimensions against the existing Game View before calculating the target position and running EventSystem raycasts. The fixed preset and zoom remain unchanged. Unresolved coordinates return a refusal, and an actual overlay still blocks the click.
- Safe Mode diagnostics distinguish a prompt, entered mode and exit. Temporary diagnostic updates on standard error (stderr) can report a startup blocker while the readiness check continues; continued log output does not by itself cause an immediate terminal failure.
- Opt-in timing for the Python helper reports the measured phases and time outside those phases. When checking stale requests, the helper reads the request journal (recorded request events) once per inspection instead of once per candidate, preserving event order without a persistent cache.
- Prefab render results distinguish a PNG that was written from confirmation that its content is visually correct. The validation recipe covers visible content, delayed UI transitions, targeted queries and compile-first checks.
- Superseded pull-request discovery, site UI and integration CI runs are cancelled; platform tests and independent push, tag and manual evidence runs remain enabled.
What this gives developers
- Fewer misleading compact verdicts and clearer evidence about whether repeating an action could duplicate work.
- Click validation against the requested portrait view, including real obstruction checks, without changing the user's preset to make a test pass.
- More useful startup and timing diagnostics, with explicit boundaries between delivery, completion and visual acceptance.
Validation
- Local host Python suite: 1196 tests run, 1182 passed and 14 skipped, with no failures or errors. The skips cover native Windows behavior and the explicitly manual-only Unity workflow contract.
- Documentation website Playwright checks: 42 passed.
- Local Unity
6000.0.58f2on macOS: refresh EditMode29/29, prefab EditMode23/23, fixed-portrait PlayMode4/4, and asynchronous interaction PlayMode4/4, all without skips. Portrait tests used1440x3200, zoom0.35, the primary display, three canvas modes and a real occluder. - A no-reload refresh completed with matching identity. A controlled domain reload returned explicit unresolved accounting without replay. Runtime and test-assembly compile-negative fixtures failed; restored positive controls passed.
- Release version consistency, documentation freshness, public-safety checks with a nonempty private denylist, and separate work/release commit-shape checks passed. Both installed client helper targets were refreshed.
Known limitations
- Remote Unity Package CI remains waived because the runner has no Unity license. The release therefore has no CI-recorded Unity EditMode or PlayMode proof; local Unity results retain their stated platform and version scope.
- The focused Unity checks do not establish secondary-display behavior, other Unity versions or operating systems, or full application/device/backend acceptance.
- A refresh whose runtime identity is lost remains unresolved; this release does not promise automatic completion recovery or replay.
- Host timing excludes launcher startup and client latency. Dispatch timing includes transport waiting and must not be interpreted as pure Unity execution time.
- A produced prefab capture does not by itself prove that its content is visually correct.