Пишите сюжет на доске. Игра говорит вашими словами.

You are an agent in my game repository. A Coming Soon board is running beside it: http://127.0.0.1:7741 (if it does not answer, ask me for the port). Task: move the game's story onto the board — characters, places, scenes, quests, dialogues, and key items — as they exist now in the code and data.

1. Before doing anything, read the board's documentation in full:
   curl -s http://127.0.0.1:7741/docs/connect.md
   curl -s http://127.0.0.1:7741/docs/board.md
   That is the format of nodes and projects, project.json, and the whole REST API. After that, use only what is described there.

2. Find the story project: curl -s http://127.0.0.1:7741/api/projects. If it does not exist, create it: POST /api/projects {"id":"story","title":"Story","mode":"story"}. Read its vocabulary: curl -s 'http://127.0.0.1:7741/api/graph?p=story' (the vocab field: types, parts, statuses, edge kinds, places).

3. Walk the game: README, CLAUDE.md, scenes and levels, story and quest scripts, dialogues, localization, flags, and saves. Make yourself a list: characters, places, scenes and cutscenes, quests, dialogues, key items; for each, where it is in the repository (path:line) and which part of the game it belongs to.

4. Places and parts of the game. If events happen in places, write them into "rooms" in .скоро-будет/projects/story/project.json (a latin id → the name). If the parts of the game do not match the default "gates", replace those too. Do not edit any other board file by hand.

5. Create nodes only through the API: every change lands in the journal, and I can undo any of them. Characters first (cluster "character", ids like c-name), then the rest:
   curl -s -X POST http://127.0.0.1:7741/api/node -H 'Content-Type: application/json' -H 'X-Project: story' -H 'X-Actor: claude-code' -d '{"id":"…","title":"…","cluster":"scene","gate":"…","room":"…","status":"done","cast":["c-…"],"files":["path"],"body":"…"}'
   - id — latin letters, digits, and hyphens;
   - status: done — it is in the game and works, doing — partly done, missing — intended (in the docs or a TODO) but not in the game;
   - cast — characters who take part; files — where this is in the repository;
   - body — markdown: what happens, who takes part, conditions and flags, what it gives, [[id]] links to neighboring nodes.

6. Link the nodes: POST /api/story/edge {"source":"…","target":"…","kind":"…"} — next (what follows), requires (what requires what), gives (what gives an item or a flag). Do not link characters: they take part through cast.

7. If the line text lives in the game data, move it into dialogues: PUT /api/dialogue/<node id> in the format from /docs/board.

8. Do not change the game's code, and do not commit anything. At the end, report: how many of each thing you created, what you found but did not understand, where the story in the code disagrees with the documents, and what I should check on the board.