@@ -84,9 +84,9 @@ v2.0.0
 
 ---
 
-## V3 — In Progress
+## V3 — Completed
 
-V3 has been re-scoped.
+V3 was re-scoped during development.
 
 The old V3 goal was:
 
@@ -110,33 +110,38 @@ Therefore:
 
 Ground-truth completeness is now explicitly a V4 concern.
 
----
+Delivered:
 
-# 3. Current Development Focus
+- accounts and authentication (argon2, server-side sessions in an httpOnly cookie)
+- user-owned attempts, with ownerless pre-account attempts kept until claimed
+- per-user analytics and isolation
+- English / 中文 interface
+- existing-content cleanup, plus a cross-wiki move mapping for every boss in `research/ground_truth/semantic/wiki_mapping/`
+- four required CI jobs, including a check that data survives a Docker restart
 
-## V3 — Multi-User Product Foundation
+Released as:
 
-V3 answers:
+```text
+v3.0.0
+```
 
-> **Can different players reliably use the application with isolated personal data?**
+---
+
+# 3. Current Development Focus
 
-Completed:
+## V4 — Combat Ground Truth Foundation
 
-1. Accounts and authentication
-2. User-owned attempts
-3. Per-user analytics and isolation
-4. Bilingual interface
+V4 answers:
 
-Remaining:
+> **What boss actions actually exist, and what evidence supports the semantic moves used by the product?**
 
-5. Existing-content cleanup
-6. V3 hardening and release
+Start with V4 Milestone 1 (research foundation) and Milestone 2 (Genichiro runtime pilot). See sections 18–36.
 
-Public deployment has moved to V4.
+V3 is released. Sections 7–17 remain the reference for how the current product is built; their product rules (lightweight attempt recording, honest analytics, per-user isolation, one language per page) still apply.
 
-Practice recommendations have moved to V5.
+Public deployment is V4 Milestone 9.
 
-Full boss ground-truth completeness has moved to V4.
+Practice recommendations are part of V5.
 
 ---
 
@@ -458,7 +463,7 @@ The user reviewed all Chinese content.
 
 ---
 
-# 12. V3 Milestone 5 — Existing-Content Cleanup
+# 12. V3 Milestone 5 — Existing-Content Cleanup ✅
 
 This milestone has changed significantly from the old roadmap.
 
@@ -505,7 +510,7 @@ The existing content was reviewed against both Fextralife and Fandom, and the us
 - move types made consistent
 - the cross-wiki mapping for every boss is in `research/ground_truth/semantic/wiki_mapping/`; it records what both wikis say, including what the product does not use
 
-Still open: whether Lady Butterfly and Guardian Ape adopt Fandom's more specific move lists, or keep their current lists until V4 rebuilds them.
+Decided: Lady Butterfly and Guardian Ape keep their current move lists. Fandom's more specific lists are recorded in the mapping, and V4 rebuilds these movesets from engine evidence.
 
 ---
 
@@ -566,7 +571,7 @@ Engine completeness belongs to V4.
 
 ---
 
-# 15. V3 Milestone 6 — Hardening and Release
+# 15. V3 Milestone 6 — Hardening and Release ✅
 
 Before releasing V3:
 
@@ -580,6 +585,7 @@ Before releasing V3:
 - Docker smoke test passes
 - authentication isolation remains covered
 - bilingual behavior is tested
+- data survives a Docker Compose restart (checked by the `docker` CI job)
 
 The application remains locally deployable through Docker Compose.
 
@@ -1575,24 +1581,19 @@ Examples currently not justified by default:
 
 # 53. Current Priority Order
 
-Until V3 is released:
+V3 is released. Work through V4 in milestone order:
 
 ```text
-1. Bilingual interface
-2. Existing-content cleanup
-3. V3 tests / docs
-4. Release v3.0.0
+1. Research foundation (V4 Milestone 1)
+2. Genichiro runtime pilot (V4 Milestone 2)
+3. Static engine mapping (V4 Milestone 3)
+4. Genichiro semantic catalog (V4 Milestone 4)
+5. Completeness review (V4 Milestone 5)
 ```
 
-However, a small V4 research spike may run in parallel if necessary to resolve a specific uncertain move.
-
-Such research must:
+The later V4 milestones (Resurrection, product integration, boss expansion, public deployment) follow once Genichiro's pipeline is proven.
 
-- stay isolated from production schema
-- not destabilize V3
-- not require all-boss extraction
-- preferably begin with Genichiro
-- document evidence
+Keep the released V3 product working: fix product bugs on `dev` as they appear, and do not change the production schema for ground-truth research until V4 Milestone 7.
 
 ---
 
 
@@ -188,16 +188,16 @@ V2 runs locally with Docker Compose.
 
 ## V3 — Multi-User Product Foundation
 
-### In Progress
+### V3.0 — Completed
 
-V3 turns the single-user local app into a foundation that several players can use, each with their own data.
+V3 turned the single-user local app into a foundation that several players can use, each with their own data.
 
 * ✅ **Accounts and authentication:** registration, login and logout, argon2-hashed passwords, and server-side sessions in an httpOnly cookie. Boss data stays browsable without an account.
 * ✅ **User-owned attempts:** every attempt belongs to the player who recorded it. Attempts recorded before accounts existed are kept and can be claimed with `scripts.claim_attempts`.
 * ✅ **Per-user analytics:** attempt history, boss analytics, progression, and the Sekiro dashboard only cover your own attempts.
 * ✅ **English / 中文 interface:** a language switch, with each language showing only its own text. The choice is saved on the account, or in the browser for visitors. Most Chinese move names and descriptions are translations of the English source material.
-* **Existing content cleanup:** correcting the current boss data rather than adding more bosses from wikis.
-* **Release `v3.0.0`.**
+* ✅ **Existing content cleanup:** the current boss data was checked against two wikis (Fextralife and Fandom); errors and misleading text were fixed and phase structures corrected, rather than adding more bosses from wikis. The comparison for every boss is kept in [`research/ground_truth/semantic/wiki_mapping/`](research/ground_truth/semantic/wiki_mapping/README.md) as the starting point for V4.
+* ✅ **Hardening:** the four required CI jobs also check that accounts and attempts survive a Docker restart.
 
 While expanding boss coverage, community wiki movesets turned out to be incomplete and sometimes inconsistent with each other. V3 therefore treats boss data as human-readable reference content, not as a complete record of every attack in the game. Verifying movesets against the game itself is the job of V4.
 
@@ -274,7 +274,7 @@ Requires [Docker](https://www.docker.com/) (Docker Desktop on Windows or macOS).
 
    On every start the backend applies database migrations and loads the bosses from `backend/seed/bosses.json`.
 
-3. Open http://localhost:8080 and create an account. Boss movesets can be browsed without one; recording attempts and viewing analytics need a login. The API documentation is at http://localhost:8000/docs.
+3. Open http://localhost:8080 and create an account. Boss movesets can be browsed without one; recording attempts and viewing analytics need a login. Switch between English and 中文 in the top-right corner. The API documentation is at http://localhost:8000/docs.
 
 To open the app on a phone on the same network, use `http://<your computer's LAN IP>:8080`. On Windows, find the IP with `ipconfig` under the Ethernet or Wi-Fi adapter, not the `vEthernet (WSL)` one.
 
 
@@ -188,16 +188,16 @@ V2 使用 Docker Compose 在本地运行。
 
 ## V3 — 多用户产品基础
 
-### 进行中
+### V3.0 — 已完成
 
 V3 把单用户的本地应用，变成可以供多名玩家使用、每人数据互相独立的产品基础。
 
 * ✅ **账号与认证：** 注册、登录、登出；密码用 argon2 哈希保存；登录状态是存在 httpOnly cookie 里的服务器端会话。不登录也能浏览 Boss 资料。
 * ✅ **攻略记录归属用户：** 每条记录都属于记录它的玩家。有账号系统之前的旧记录都保留着，可以用 `scripts.claim_attempts` 认领。
 * ✅ **按用户的分析：** 攻略历史、Boss 分析、进度图和只狼总览都只统计你自己的记录。
 * ✅ **中英文界面：** 可以切换语言，每种语言只显示该语言的文字。登录用户的选择保存在账号里，访客的选择保存在浏览器里。大部分中文招式名和说明译自英文资料。
-* **清理现有内容：** 修正现有的 Boss 数据，而不是继续从 Wiki 补充更多 Boss。
-* **发布 `v3.0.0`。**
+* ✅ **清理现有内容：** 对照两个 Wiki（Fextralife 和 Fandom）检查了现有的 Boss 数据，修正了错误和有误导性的描述，也修正了阶段结构，没有继续从 Wiki 补充更多 Boss。每个 Boss 的对照结果保存在 [`research/ground_truth/semantic/wiki_mapping/`](research/ground_truth/semantic/wiki_mapping/README.md)，作为 V4 的起点。
+* ✅ **加固：** 4 个必须通过的 CI 任务还会检查重启 Docker 后账号和攻略记录是否仍然保留。
 
 在扩充 Boss 数据的过程中，我们发现社区 Wiki 的招式资料并不完整，不同 Wiki 之间有时还互相矛盾。所以 V3 把 Boss 数据定位为方便阅读的参考资料，而不是游戏里全部攻击的完整记录。用游戏本身验证招式数据，是 V4 的工作。
 
@@ -274,7 +274,7 @@ V1 刻意使用 JSON 持久化，因为初始数据集很小，主要目标是
 
    后端每次启动时都会执行数据库迁移，并从 `backend/seed/bosses.json` 同步 Boss 数据。
 
-3. 打开 http://localhost:8080 并注册一个账号。不登录也可以浏览 Boss 的招式，但记录尝试和查看分析需要登录。API 文档在 http://localhost:8000/docs。
+3. 打开 http://localhost:8080 并注册一个账号。不登录也可以浏览 Boss 的招式，但记录尝试和查看分析需要登录。右上角可以切换 English / 中文。API 文档在 http://localhost:8000/docs。
 
 在同一网络下用手机访问时，打开 `http://<电脑的局域网 IP>:8080`。Windows 上可以用 `ipconfig` 查看 IP，要看 Ethernet 或 Wi-Fi 网卡下面的地址，不是 `vEthernet (WSL)` 那一个。
 
 
@@ -107,7 +107,7 @@ Released as `v2.0.0`.
 
 ---
 
-# V3 — Multi-User Product Foundation 🚧
+# V3 — Multi-User Product Foundation ✅
 
 ## Core Question
 
@@ -198,7 +198,7 @@ Do not describe translated terminology as official unless an authoritative sourc
 
 ---
 
-## Milestone 5 — Existing Content Cleanup
+## Milestone 5 — Existing Content Cleanup ✅
 
 Review the boss data already present in the application.
 
@@ -225,6 +225,8 @@ It may remain explicitly uncertain or be deferred to V4 ground-truth research.
 
 This milestone also records a per-boss mapping between the product's moves and the Fextralife and Fandom entries (`research/ground_truth/semantic/wiki_mapping/`). It measures how far the two wikis disagree, which is a lower bound on the gap to ground truth, and it becomes the starting point for V4.
 
+Delivered: obvious errors and misleading descriptions fixed, phase structures corrected (True Corrupted Monk; Genichiro, Way of Tomoe added to the Isshin fight), actions that cannot end an attempt removed from the movesets, move-level sources for moves taken from another page, and the mapping for all 8 bosses. Across 106 product moves, 52 match one-to-one between the two wikis.
+
 ### Important Boundary
 
 V3 does **not** require:
@@ -240,7 +242,7 @@ Those belong to V4.
 
 ---
 
-## Milestone 6 — V3 Hardening and Release
+## Milestone 6 — V3 Hardening and Release ✅
 
 Before release:
 
@@ -252,6 +254,7 @@ Before release:
 - Docker Compose build and smoke test pass
 - authentication isolation remains covered
 - bilingual behavior is tested
+- data survives a Docker Compose restart
 - documentation reflects the new roadmap
 
 The application remains reproducibly runnable locally with Docker Compose.
@@ -262,6 +265,8 @@ Release:
 v3.0.0
 ```
 
+Released as `v3.0.0`.
+
 ---
 
 ## V3 Non-Goals
 
@@ -107,7 +107,7 @@ V2 刻意只在本地部署。
 
 ---
 
-# V3 — 多用户产品基础 🚧
+# V3 — 多用户产品基础 ✅
 
 ## 核心问题
 
@@ -198,7 +198,7 @@ Boss 内容的翻译必须保留原始资料的含义。
 
 ---
 
-## Milestone 5 — 清理现有内容
+## Milestone 5 — 清理现有内容 ✅
 
 审核应用中已有的 Boss 数据。
 
@@ -225,6 +225,8 @@ Boss 内容的翻译必须保留原始资料的含义。
 
 这个里程碑还会为每个 Boss 记录一份产品招式与 Fextralife、Fandom 条目之间的对照表（`research/ground_truth/semantic/wiki_mapping/`）。它衡量两个 Wiki 之间的分歧有多大，这是和真实数据之间差距的下限；它也是 V4 工作的起点。
 
+已交付：修正了明显的错误和有误导性的描述；修正了阶段结构（宫内破戒僧；剑圣一心战加入了巴流 苇名弦一郎阶段）；从招式列表中移除了不会结束一次尝试的动作；为取自其他页面的招式记录了招式级来源；完成了全部 8 个 Boss 的对照表。在 106 个产品招式中，两个 Wiki 能一一对应的有 52 个。
+
 ### 重要边界
 
 V3 **不**要求：
@@ -240,7 +242,7 @@ V3 **不**要求：
 
 ---
 
-## Milestone 6 — V3 加固与发布
+## Milestone 6 — V3 加固与发布 ✅
 
 发布前：
 
@@ -252,6 +254,7 @@ V3 **不**要求：
 - Docker Compose 构建和冒烟测试通过
 - 认证隔离仍然有测试覆盖
 - 双语行为有测试覆盖
+- 重启 Docker Compose 后数据仍然保留
 - 文档反映新的路线图
 
 应用仍然可以通过 Docker Compose 在本地可复现地运行。
@@ -262,6 +265,8 @@ V3 **不**要求：
 v3.0.0
 ```
 
+已发布为 `v3.0.0`。
+
 ---
 
 ## V3 不做的内容