What the first beta build does, and what it does not

Both halves of this are worth stating plainly, because a tester who installs the build expecting a game will conclude the server is broken, and it is not. It is early.

Working, and verified against the live server:

• The bootstrap handshake. The client asks where the world is and is told bravefrontier.xyz.
• Guest sign-in, and the feature flag set behind it.
• Account creation, and the same account still being there after a restart.
• The opening data payload, around 7.6 MB of it, and the account summary that follows.
• All 147 master data tables: every unit, mission, skill and drop the global game shipped with.
• The content library, 76,005 sprites, sounds and text files.

Not in this build:

• Separate accounts. Guest sign-in hands every device the same user id, so every tester is on one shared save. The server has never needed a second account until now, and the value is still hardcoded.
• Any link between the game and your Groot ID. The passport gates the download and nothing else; the client has never heard of it.
• Battles. Starting a mission returns nothing.
• Summoning. There are no gates and no pulls.
• Deck editing. A squad cannot be arranged yet.
• The home screen's live panels, and unit and inventory management.

The honest measure is that 11 of roughly 278 game commands have a handler behind them. Some of the remainder answer with an error the client treats as fatal to its connection, so a session can end abruptly when you reach for something that is not built. A build that returns an empty success instead of an error is finished and waiting, and it is the next thing to go out.

The order the rest are being built in is the home screen first, then deck editing, then the summon gates, then the battle loop. The battle loop is last because it needs message definitions that do not exist yet, not because it is wanted least.