v0.36.0 — the download loses its test suite

Everyone in a match needs this build to fight. The room protocol is
unchanged, so a 0.36.0 game and a 0.35.0 one still find each other and share
a lobby — but the door compares mod versions, so a battle between them is
refused, with a message naming both. Worth grabbing together.

You could be knocked out for touching the grass

With another overworld mod installed, walking into a wild encounter during
the SAFARI could eliminate you on the spot. The guard meant to excuse that
was listening on the wrong event and checking for the wrong phase, so it had
never once run — the refusal actually arrives a beat earlier than where it
was waiting, and it was watching the match rather than the hunt.

It runs now, and only during the SAFARI and the drop, where "no usable
POKéMON" honestly means "hasn't caught anything yet". Everywhere else that
still means a whiteout, and a whiteout still puts you out. Catching nothing
before the buzzer still ends your match.

The download is a third smaller

The zip was shipping the mod's own test suite — 27 files, 39% of what you
downloaded, and nothing in the game ever read one of them. It's 303KB down
to 191KB.

Files now sit at the top of the archive rather than inside a
battle_royale/ folder. The game reads either layout and installs to the
same place, so this changes nothing you can see.

The mod manager will ask for one more thing

The manifest now declares engine_internals, so enabling the mod shows an
extra line about reaching into engine code. Nothing behaves differently and
nothing new is happening — the mod has always needed those parts of the
game, and the manifest simply never said so.

Also in this build: a failed new-game left the save-event guard switched off
for the rest of the session, the career and stats files stopped carrying two
copies of the same parser, and a handful of log lines that claimed success
when nothing had happened now tell the truth.