v0.3.67 — Passing compile matrices stay passed

v0.3.67 — Passing compile matrices stay passed

Why

The multi-project runner could turn a successful GUI-fallback compile matrix into
failed_wrapper_unity_unproven, print total=0, and exit 1. Unity had actually
returned passed with all six configurations green; the aggregator understood
the older full response shape but not the compact shape now emitted by default.

What changed

• Outcome evidence is resolved from the nested result summary, compact top-level
  fields, the named summary artifact, and finally a Unity-confirmed result
  artifact.
• Per-project status records identify the source used for Unity outcome,
  transport outcome, and compile-matrix evidence.
• Missing matrix counters are reported as unavailable instead of invented
  zeroes.
• Regression coverage protects compact success, both artifact fallbacks, and
  unavailable-counter output.

What this gives you

A successful Unity compile matrix remains successful at the portfolio layer,
including when a batch lane reuses an already-open editor and falls back to the
GUI transport. Release and maintenance sweeps no longer stop on this false
wrapper failure.

Validation

• Focused multi-project runner suites: 12/12 passed.
• Full host discovery: 996 passed with 14 expected platform skips, including
  live TCP loopback transport coverage.
• Public documentation UI checks: 42/42 passed in desktop and narrow Chromium
  viewports.
• Release consistency, documentation freshness, and public-safety checks pass.

Known limitations

Compile-warning totals and rebuilt-versus-cache-hit assembly counts remain open
evidence gaps. Hosted Unity Package CI also remains explicitly waived because
the runners do not have Unity license credentials. A fresh local package-matrix
attempt was blocked before tests by the same local licensing channel; package C#
source is unchanged, so the latest completed Unity 2022.3 and Unity 6000 package
evidence remains the v0.3.66 release proof.