INTEGRATION REVISION 0.1.0-integration.1
Read CLOUD-INTEGRATION-ADDENDUM.txt FIRST before adopting Cloud integration.
Use the supplied MAIN-PLAYER-BRANCH.py.txt and MAIN-ONCE-DRAIN.py.txt hunks;
the addendum supersedes earlier synchronous player-dispatch instructions below.
Node bridge core, frozen helper and package lock remain exactly version 0.1.0.
This is reviewed source integration, not an automatic update or runtime start.

Reviewed source integration only; not an automatic updater or standalone node enrollment service.
Adopt agent/minecraft_players.py and api/routes_game_players.py in the matching Cloud source under coordinated ownership.
api/app.py imports routes_game_players.router as game_players_router and includes that router.
agent/main.py handles ctype minecraft_player using run_player_command(identity, command), then posts its typed result with the existing signed command result API.
current_inventory removes stale minecraft.players.v1 then merges minecraft_players.capability_labels().
Keep the existing canonical NodeCommand, Cloud credential/signature and Core MissionEngine ownership; never invent a node/mission/agent identity.
Configure IMC_MINECRAFT_PLAYERS=1 and IMC_MINECRAFT_PLAYER_BRIDGE_DIR to this extracted kit only for the modern, existing authorized agent.
Private account authentication must run under that same Windows identity. No Cloud/MS identity, password, token or cache is included.