The bundle's manual, in Chinese

scripts/deploy.py writes manual.en.json (kk-bundle-manual/1) into every bundle: each pad control and each key the bundle reads, what it does in each mode, how each mode is reached and left, and every mode switch. It is generated from the controller's own account of its controls (padGuide), so it cannot disagree with the bindings. The pad and the keyboard are two paths since 2026-09-29 and the manual lists them apart: in each mode controls is the pad and keys the keyboard, and each switch says which device it is on. The Chinese version is a translation of it, and this skill is how it is made: the build cannot write natural Chinese, and a person or an agent can.

Steps

1. Find the bundle directory. deploy.py prints it ([deploy] bundled <commit> -> …/out/bundle_<ts>/<name>) and then prints the --translate command with that path already filled in. It holds manual.en.json and bundle.json.
2. Read manual.en.json in full.
3. Write manual.zh.json somewhere outside the bundle (a scratch file):
   • the same JSON, field for field, in the same order;
   • "language": "zh";
   • translate only the text fields: source, summary, enter, leave, keyboard, pad, does -- and does wherever it is: in each mode's controls (the pad), in each mode's keys (the keyboard), and in switches. A pad that is null (a keyboard switch) stays null;
   • leave every other value exactly as it is -- schema, bundle, mode, task, default, control, with, device, from, the key of each entry in a mode's keys (W, ;, Space, ↑), and the keys lists of switches (Space, Ctrl + 1, Num 1). They are identifiers, and the check below refuses a translation that changes one.

4. Add it to the bundle, which checks it and packs the .app again:

   python scripts/deploy.py --translate out/bundle_<ts>/<name> --language zh --manual <scratch file>

   It refuses a file whose non-text fields differ from the English one, and holds the result to deploy/app.schema. Fix what it names and run it again.

5. If the .app is going to be committed (bundles are committed under out/bundle_<ts>/<name>.app), commit it after this step, not before: the translation changes the archive.

How to write it

For someone holding a gamepad or sitting at a keyboard, in plain Chinese. Keep mode names as identifiers where they name a mode (进入 jump), and say what the mode is in the sentence when the English does. The manual lists each mode's keys on their own; say what a key does, never which pad control it is -- the English never says that either.

A task's own words -- closes the left claw as far as it is held, from its controls.yaml -- are translated like any other text: 按多深，左爪就夹多紧; holds the carried arm straight out, thumb up, while held is 按住时手臂向前伸直，拇指朝上, and thumb-web up is 虎口朝上. A claw mode lists only its own side's claw (the left claw's lists LT and Space, not RT), so translate what is there and add nothing.

Why a separate step

The English is the build's and the Chinese is a translation of it, never the other way round: a manual written in Chinese first would have no generator to hold it to the bindings. --translate is what keeps the two the same manual in two languages -- it compares every identifier -- and it is also why a bundle built without an agent still ships the English one.