feedback7: version 0.2.2 — package.json / package-lock.json / APP_VERSION (DEV_BUILD turns false), README release form, CHANGELOG 0.2.2 — 2026-10-09, DESIGN versions line

docs/DESIGN.md

@@ -4,7 +4,7 @@ This is the **single source of truth** for every implementer. Research lives in
 
 Language: player-facing text is **Simplified Chinese** by default, with an English switch since 0.2.0 (§25.2, docs/I18N.md: UI strings through `t('中文')`, game texts from the official Chinese data or the official EN client's). Code, comments and identifiers are English.
 
-Versions: the first public release was **0.1.0** (2026-10-02, the state of §0–§20.15); the releases after it add the player feedback and GitHub reports — 0.1.1 §21, 0.1.2 §22, 0.1.3 §23, 0.1.4 §24 — and **0.2.0** (2026-10-07; `CHANGELOG.md`) the maintainability refactor, two languages, 补位, 自选编队 and their fidelity work — §25 — and **0.2.1** (2026-10-07; `package.json`, `shared/constants.js APP_VERSION`) the 联防 battlefield restored, full potential and the GitHub fixes after it — §26. The 0.2.2 dev line (`package.json`, `shared/constants.js APP_VERSION`: `0.2.2-dev`) adds §27 and is the state described by this document. The labels v1 / v2 / v2.1–v2.5.2 in §0, §14–§20 and in the BALANCE / SIM comparisons name the design generations and the private playtest builds that came before it; they are kept as history.
+Versions: the first public release was **0.1.0** (2026-10-02, the state of §0–§20.15); the releases after it add the player feedback and GitHub reports — 0.1.1 §21, 0.1.2 §22, 0.1.3 §23, 0.1.4 §24 — and **0.2.0** (2026-10-07; `CHANGELOG.md`) the maintainability refactor, two languages, 补位, 自选编队 and their fidelity work — §25 — **0.2.1** (2026-10-07) the 联防 battlefield restored, full potential and the GitHub fixes after it — §26 — and **0.2.2** (2026-10-09; `package.json`, `shared/constants.js APP_VERSION`) per-operator 潜能 / 练度, Japanese voices, the statistics page, 失衡, whole-frame attack timing and the GitHub fixes after 0.2.1 — §27, the state described by this document. The labels v1 / v2 / v2.1–v2.5.2 in §0, §14–§20 and in the BALANCE / SIM comparisons name the design generations and the private playtest builds that came before it; they are kept as history.
 
 ---
 
@@ -33,4 +33,4 @@ normative lines it rewrote).
 | §24 | [history/0.1.4.md](history/0.1.4.md) | 0.1.4 — community reports after 0.1.3 |
 | §25 | [history/0.2.0.md](history/0.2.0.md) | 0.2.0 |
 | §26 | [history/0.2.1.md](history/0.2.1.md) | 0.2.1 — after the 0.2.0 release |
-| §27 | [history/0.2.2.md](history/0.2.2.md) | 0.2.2 — after the 0.2.1 release |
+| §27 | [history/0.2.2.md](history/0.2.2.md) | 0.2.2 — after the 0.2.1 release (2026-10-09) |

docs/history/0.2.2.md

@@ -4,7 +4,7 @@ Part of [DESIGN.md](../DESIGN.md) (the index; section numbers are global).
 
 ## 27. 0.2.2 — after the 0.2.1 release
 
-0.2.2 is built on `feedback7`, branched from the 0.2.1 release (tag v0.2.1) and marked `0.2.2-dev` until it ships. Its
+0.2.2 is built on `feedback7`, branched from the 0.2.1 release (tag v0.2.1) and marked `0.2.2-dev` until it shipped (2026-10-09). Its
 workstreams branched off it as `fb7-*` (some carried out by Grok coding runs on statically reviewed pull requests), each
 reviewed with an interaction pass before it was merged with its golden scenarios named; where a merge moved a scenario
 neither side moved alone, the merge commit explains the interaction. Each rule was checked against the official data and