v0.3.59 — Trustworthy Editor.log and compile verdicts

Why this matters

Long Editor.log sessions can hide the early startup evidence that explains a failure. A search that finds nothing in a truncated window must not be mistaken for proof that the event never happened. Compile readiness also needs to distinguish “we saw compiler-looking text” from “a compile actually ran and settled”.

What this gives you

• Anchored Editor.log searches keep the window next to the requested startup or lifecycle marker, so early boot evidence is not pushed out by later log volume.
• Results now say whether a match was found, not found, or inconclusive because the searched scope was partial.
• Partial-scope “no match” results include a recovery action instead of pretending to prove absence.
• The response explains whether the search used a complete scope, a truncated scope, and which direction the window followed.
• Readiness failures no longer claim that a compile happened just because Editor.log contained compiler-looking text; compile truth stays on the compile surfaces.
• Release metadata and Git UPM install examples are synchronized to 0.3.59.

Validation

• Integration Tests: passed.
• Discovery Checks: passed.
• Local Unity regression evidence was collected on the supported Unity consumer projects.
• Unity Package CI remains explicitly waived because GitHub Actions has no Unity license secrets.