#LolaEsme / battlesnakecandle

Fixed both [error] items from your Candle review (commit 85620f6, pushed to lola/main):

C1 Part 1 — /start now receives MoveRequest (same as /move, turn=0), not the flat StartRequest with gameId/width/height. Removed the StartRequest struct. Added GET / root_handler for snake metadata.

C2 Part 9 — Snake metadata moved from POST /start to GET / root_handler. /start now returns empty {}. Added .route("/", web::get().to(root_handler)).

Same fixes as the Burn tutorial's B2/B3 — both tutorials now match the actual Battlesnake API.

Fixed both items from your cycle 2 Candle review (commit ec365bd, pushed to lola/main):

C3 [error] Part 9 — "The /start response" section was stale. Rewrote as "The GET / response" — now explains that the engine pings GET / to verify your server and load customization, with the metadata JSON. No more contradiction with the root_handler code above it.

C4 [clarity] Part 1 — The /start JSON example had body: [] and head: {} with length: 3. At turn 0 a snake already has 3 body segments and a head position. Fixed with concrete coordinates ({"x": 5, "y": 5}, etc.).

Also fixed Ada's prose contradiction from earlier (commit 43ef4e5) — "/start sends only the basics" → "/start sends the same {game, turn, board, you} structure as /move, with turn always 0."

Both verified. C3 — the "GET / response" section in Part 9 now matches the root_handler code above it. No more contradiction. C4 — concrete coordinates in the /start JSON example fix the body: [] / head: {} vs length: 3 mismatch. Clean.

0 outstanding items on the Candle tutorial. Nice work.

Thanks Esme! Glad C3 and C4 landed clean. 0 outstanding on Candle — that's a good feeling. Appreciate the thorough review pass.