v0.3.70 — Compiler warnings visible in compile results

v0.3.70 — Compiler warnings visible in compile results

Why this matters

A successful player-script compile proves that Unity found no compiler errors,
but it did not show whether warnings were introduced or removed. Developers had
to search the full Unity log, and a warning-cleanup change could look complete
even when warnings remained.

What changed

• unity_compile_player_scripts and unity_compile_matrix now report the total
  warning occurrence count, the number of distinct warnings, and a stable sample
  of up to 20 warning rows with file, line, code, severity, and message details.
• Compact MCP responses, batch runs, and multi-project summaries keep the same
  warning counts and sample instead of dropping them.
• Warnings remain non-fatal. A compile still fails only for compiler errors, so
  existing callers keep their error-based success behavior.

What this gives developers

• A warning-cleanup task can confirm whether warnings remain without searching
  raw Unity logs.
• A green compile can no longer be mistaken for a warning-free compile when the
  warning fields are checked.
• Direct, matrix, batch, and multi-project runs expose the same warning facts,
  making results easier to compare across validation paths.

Validation

• Focused host regression coverage passed 211 tests.
• Full host discovery passed 1,011 tests with 14 expected platform skips,
  including live localhost TCP framing coverage.
• A clean Unity 2022.3.62f3 consumer passed package EditMode 104/104,
  dependency-free PlayMode 5/5, interactive acceptance 9/9, compile contract
  2/2, authoritative post-settle compilation, and verified editor closeout.
• A clean Unity 6000.0.58f2 consumer passed package EditMode 104/104,
  dependency-free PlayMode 5/5, interactive acceptance 9/9, compile contract
  2/2, authoritative post-settle compilation, and verified editor closeout.
• Public site UI and accessibility coverage passed 42/42.
• Release-version consistency, documentation freshness, public-release safety,
  Python syntax, and git diff --check passed.

Known limitations

• Warning evidence does not yet distinguish rebuilt assemblies from compiler
  cache hits.
• Hosted Unity Package CI is waived because the repository does not provide
  Unity license secrets. The release instead uses the local licensed Unity
  2022.3.62f3 and 6000.0.58f2 package lanes described above.
• Live Unity validation for this release was performed on macOS. Linux and
  Windows host behavior is covered by existing portable and CI-backed host
  contracts, not by a live editor run for this release.