v0.3.80 — Keep saved Unity results authoritative

v0.3.80 — Keep saved Unity results authoritative

Why this matters

The offline release checker reads saved Unity results alongside evidence receipts.
A receipt could report zero warnings or successful tests even when the saved result
showed warnings, too few tests, or errors after Unity settled. The checker could
then accept evidence that did not meet the release plan.

What changed

• Warning counts, assembly rebuild measurements, test counts, errors after Unity
  settles, and execution blockers now come directly from the saved helper response.
• Receipt metadata cannot replace missing helper measurements with passing claims.
  Raw receipts retain their existing producer-supplied facts.

What this gives developers

• Release acceptance follows the saved Unity result when receipt metadata
  contradicts it, reducing false passes and false failures caused by stale metadata.

Validation

• Full host suite: 1,134 tests OK with 14 expected platform skips.
• Focused offline evaluator suite: 38 tests passed. New cases cover contradictory
  warning, rebuild, test-count, post-settle and timeout metadata.
• Public documentation browser checks: 42 tests passed.
• Version consistency, documentation freshness, public-release safety and separate
  work/release commit checks passed.

Known limitations

• This is an offline evidence correction. It does not run Unity or authenticate
  an operator-supplied raw receipt. Package-scoped warning evidence requires a
  separate raw receipt with evidence of which package owns the warnings.
• Hosted Unity Package CI remains waived because runner license secrets are
  absent. There is no hosted EditMode or PlayMode proof for this release commit.