v0.3.48 — Safer Android setup and mutation evidence
Why this matters
Android dependency resolution can finish before generated files are actually stable, and a Unity callback can say “done” even when the project did not change. That is risky when the next step is a build or rollout.
What this gives you
- Android dependency resolution now waits for EDM4U to finish and verifies the generated files and requested coordinates before reporting success.
- Project mutations now show what changed before and after, so a successful Unity callback is not mistaken for proof that the intended change happened.
- Generated SDK outputs can be checked even when they are untracked, using a fingerprinted project baseline.
- Diff reports are saved as durable artifacts, making rollout evidence easy to find later.
Validation
- Typed Android failure paths and generated-output stability checks are covered by host and Unity regression tests.