Skip to content

v0.3.79 — Keep incomplete Unity evidence out of release acceptance

Choose a tag to compare

View all tags
@FoxsterDev FoxsterDev released this 22 Sep 16:11
· 25 commits to main since this release
v0.3.79
73c8705

v0.3.79 — Keep incomplete Unity evidence out of release acceptance

Why this matters

Unity validation often arrives as separate compile, test, build, device, and MCP-client receipts. A successful helper response could previously be summarized too strongly even when a warning budget failed, a required rebuild was not measured, or the receipt came from the wrong execution channel.

What changed

  • Added the offline evaluate_validation_evidence.py evaluator and strict plan, receipt, and acceptance-report schemas.
  • The evaluator matches evidence on the exact stage, dimensions, scene, and execution channel, then applies warning, rebuild, test, and semantic policies separately from the operation result.
  • Reports retain the full required denominator, mark reused evidence, and return stable reason codes in a bounded compact envelope. Invalid input exits with code 2; it is not counted as a blocked validation row.

What this gives developers

  • A compile with a warning under a zero-warning policy, a build offered as device-runtime proof, or helper health offered as native MCP-client proof no longer looks release-ready.
  • The final report shows what passed, what is blocked, and why, without dropping required rows or hiding reused evidence.

Validation

  • Full host suite: 1132 tests passed with 14 expected platform skips, including 36 focused validation-acceptance tests.
  • A reference consumer release verdict retained all 40 platform rows: 23 passed (15 reused) and 17 remained blocked.
  • Public site checks passed 42/42 across desktop, mobile, and narrow browser profiles.
  • Required GitHub workflows passed for the release SHA: Integration Tests and Discovery Checks. The tag-triggered Release Tag Gate also passed.

Known limitations

  • Hosted Unity Package CI remains waived because its runners do not have Unity license secrets. This release therefore has no CI-recorded EditMode or PlayMode proof for the release SHA.
  • The released change is an offline evidence evaluator. Unity was not launched during its focused validation, and it does not change the editor bridge or transport.
Assets 2
Loading