Clarify Java whitelist console setup and JSON edits
The Java guide mixes in-game command syntax with panel-console instructions and labels JSON examples as YAML. This change separates the console and in-game forms, adds a group example with a final list check, and explains how to preserve existing JSON entries without trailing commas. It also fixes two typos in the Java section.
Disclosure: I maintain ServerBuddy. The optional roster helper removes duplicate names and flags invalid syntax; the example works without it, and the text explains that syntax checks do not verify account existence. I can remove the optional link while keeping the documentation corrections.
Validation: npm ci using the existing lockfile and npm run build passed. All four Java JSON examples parse, the local /whitelist page returns HTTP 200, and a separate typo/claim review found no blocking issue. The helper was checked with duplicate and invalid names; three valid add commands remained, two invalid entries were excluded, and no UUIDs were generated. The final guide was also inspected in Stagehand.