docs: step 2 只留环境验证，进度表挪到 step 3 的可选 note

step 2 摆两条命令、再解释「第一条绿第二条红」，等于在验证环境这一步塞了
一个当下用不上的概念。step 2 现在只做一件事：

    mcpp test -p solutions       # 验证环境: 52 份参考答案, 应当全绿

裸 `mcpp test`（你自己的进度表）本来就属于「不经过 d2x 怎么练」这一类，
归到 step 3 已有的那条可选 note 里，和 `mcpp test -p src/cpp11` 放一起：

    > 不想经过 d2x? 练习就是测试 —— `mcpp test` 打印你的完整进度表(动手前
    > 全红), `mcpp test -p src/cpp11` 只跑某一章。

同步的地方：
- README 三语 + book 两语：step 2 收敛为一条命令；<details> 里 clone 那条
  路的环境验证也跟着改成 `mcpp test -p solutions`（原来还是裸 mcpp test）
- chapter_1 两语：「验证环境」节同样只留参考答案那条；裸 `mcpp test` 落到
  已有的「原生模式(可选)」节，作为该节三条命令里的第一条

Author: Sunrisepeak

README.md

@@ -78,13 +78,10 @@ xlings install d2x mcpp -y   # d2x: exercise framework CLI | mcpp: C++ build & t
 d2x install d2mcpp           # download the course, toolchain auto-configured
 cd d2mcpp
 mcpp test -p solutions       # verify the environment: 52 reference answers, all green
-mcpp test                    # your progress table: the exercises, all red for now
 ```
 
-> `solutions/` is a real mcpp package, so the first command compiles and runs all 52
-> reference answers — an unambiguous green tick that your toolchain works. The second
-> one is your own progress table: the exercises **are** the tests and they ship
-> unfinished, so red is exactly where you start.
+> `solutions/` is a real mcpp package, so this compiles and runs all 52 reference
+> answers — an unambiguous green tick that your toolchain is ready.
 
 <details>
   <summary>optional - start from the git source instead</summary>
@@ -95,7 +92,7 @@ mcpp test                    # your progress table: the exercises, all red for n
 git clone https://github.com/mcpp-community/d2mcpp.git   # or your fork
 cd d2mcpp
 xlings install -y            # toolchain pinned by .xlings.json
-mcpp test                    # same environment check
+mcpp test -p solutions       # same environment check
 ```
 
 > Tip: fork this repo and clone your fork — `git commit / push` keeps your practice progress in your own repository.
@@ -111,7 +108,9 @@ d2x checker                  # practice loop: edit -> save -> auto-check -> adva
 d2x status                   # progress overview
 ```
 
-> Want to run a single chapter without d2x? `mcpp test -p src/cpp11` works too.
+> Prefer plain mcpp? The exercises **are** the tests — `mcpp test` prints your whole
+> progress table (all red until you start), and `mcpp test -p src/cpp11` runs a single
+> chapter.
 
 **👉 [more details...](https://mcpp-community.github.io/d2mcpp/base/chapter_1.html)**
 

README.zh.hant.md

@@ -78,12 +78,10 @@ xlings install d2x mcpp -y   # d2x: 練習框架 CLI | mcpp: C++ 建置與測試
 d2x install d2mcpp           # 下載課程,環境自動配置
 cd d2mcpp
 mcpp test -p solutions       # 驗證環境: 52 份參考答案, 應當全綠
-mcpp test                    # 你的進度表: 練習還沒做, 此刻全紅
 ```
 
-> `solutions/` 本身就是一個 mcpp 工程, 所以第一條指令會真的編譯並執行全部 52 份參考答案 ——
-> 全綠即工具鏈沒問題, 這是個不含糊的訊號。第二條才是你自己的進度表: 練習**就是**測試,
-> 而且發下來時是沒做完的, 全紅正是起點。
+> `solutions/` 本身就是一個 mcpp 工程, 所以這條指令會真的編譯並執行全部 52 份參考答案 ——
+> 全綠即工具鏈就緒, 這是個不含糊的訊號。
 
 <details>
   <summary>可選 - 改用 clone 專案原始碼的方式</summary>
@@ -94,7 +92,7 @@ mcpp test                    # 你的進度表: 練習還沒做, 此刻全紅
 git clone https://github.com/mcpp-community/d2mcpp.git   # 或你 fork 後的倉庫
 cd d2mcpp
 xlings install -y            # 按 .xlings.json 安裝固定版本工具鏈
-mcpp test                    # 同樣的環境驗證
+mcpp test -p solutions       # 同樣的環境驗證
 ```
 
 > 建議: 先 fork 本倉庫再 clone 自己的 fork —— 通過 `git commit / push` 把練習進度保存到自己的倉庫裡。
@@ -110,7 +108,8 @@ d2x checker                  # 練習循環: 編輯 -> 保存 -> 自動偵測 ->
 d2x status                   # 進度總覽
 ```
 
-> 想單獨跑某一章而不經過 d2x? 直接 `mcpp test -p src/cpp11` 同樣可用。
+> 不想經過 d2x? 練習**就是**測試 —— `mcpp test` 印出你的完整進度表(動手前全紅),
+> `mcpp test -p src/cpp11` 只跑某一章。
 
 **👉 [更多細節...](https://mcpp-community.github.io/d2mcpp/base/chapter_1.html)**
 

README.zh.md

@@ -78,12 +78,10 @@ xlings install d2x mcpp -y   # d2x: 练习框架 CLI | mcpp: C++ 构建与测试
 d2x install d2mcpp           # 下载课程,环境自动配置
 cd d2mcpp
 mcpp test -p solutions       # 验证环境: 52 份参考答案, 应当全绿
-mcpp test                    # 你的进度表: 练习还没做, 此刻全红
 ```
 
-> `solutions/` 本身就是一个 mcpp 工程, 所以第一条命令会真的编译并运行全部 52 份参考答案 ——
-> 全绿即工具链没问题, 这是个不含糊的信号。第二条才是你自己的进度表: 练习**就是**测试,
-> 而且发下来时是没做完的, 全红正是起点。
+> `solutions/` 本身就是一个 mcpp 工程, 所以这条命令会真的编译并运行全部 52 份参考答案 ——
+> 全绿即工具链就绪, 这是个不含糊的信号。
 
 <details>
   <summary>可选 - 改用 clone 项目源码的方式</summary>
@@ -94,7 +92,7 @@ mcpp test                    # 你的进度表: 练习还没做, 此刻全红
 git clone https://github.com/mcpp-community/d2mcpp.git   # 或你 fork 后的仓库
 cd d2mcpp
 xlings install -y            # 按 .xlings.json 安装固定版本工具链
-mcpp test                    # 同样的环境验证
+mcpp test -p solutions       # 同样的环境验证
 ```
 
 > 建议: 先 fork 本仓库再 clone 自己的 fork —— 通过 `git commit / push` 把练习进度保存到自己的仓库里。
@@ -110,7 +108,8 @@ d2x checker                  # 练习循环: 编辑 -> 保存 -> 自动检测 ->
 d2x status                   # 进度总览
 ```
 
-> 想单独跑某一章而不经过 d2x? 直接 `mcpp test -p src/cpp11` 同样可用。
+> 不想经过 d2x? 练习**就是**测试 —— `mcpp test` 打印你的完整进度表(动手前全红),
+> `mcpp test -p src/cpp11` 只跑某一章。
 
 **👉 [更多细节...](https://mcpp-community.github.io/d2mcpp/base/chapter_1.html)**
 

book/en/src/README.md

@@ -74,13 +74,10 @@ xlings install d2x mcpp -y   # d2x: exercise framework CLI | mcpp: C++ build & t
 d2x install d2mcpp           # download the course, toolchain auto-configured
 cd d2mcpp
 mcpp test -p solutions       # verify the environment: 52 reference answers, all green
-mcpp test                    # your progress table: the exercises, all red for now
 ```
 
-> `solutions/` is a real mcpp package, so the first command compiles and runs all 52
-> reference answers — an unambiguous green tick that your toolchain works. The second
-> one is your own progress table: the exercises **are** the tests and they ship
-> unfinished, so red is exactly where you start.
+> `solutions/` is a real mcpp package, so this compiles and runs all 52 reference
+> answers — an unambiguous green tick that your toolchain is ready.
 
 <details>
   <summary>optional - start from the git source instead</summary>
@@ -91,7 +88,7 @@ mcpp test                    # your progress table: the exercises, all red for n
 git clone https://github.com/mcpp-community/d2mcpp.git   # or your fork
 cd d2mcpp
 xlings install -y            # toolchain pinned by .xlings.json
-mcpp test                    # same environment check
+mcpp test -p solutions       # same environment check
 ```
 
 > Tip: fork this repo and clone your fork — `git commit / push` keeps your practice progress in your own repository.
@@ -107,7 +104,9 @@ d2x checker                  # practice loop: edit -> save -> auto-check -> adva
 d2x status                   # progress overview
 ```
 
-> Want to run a single chapter without d2x? `mcpp test -p src/cpp11` works too.
+> Prefer plain mcpp? The exercises **are** the tests — `mcpp test` prints your whole
+> progress table (all red until you start), and `mcpp test -p src/cpp11` runs a single
+> chapter.
 
 **👉 [more details...](https://mcpp-community.github.io/d2mcpp/en/base/chapter_1.html)**
 

book/en/src/base/chapter_1.md

@@ -50,15 +50,14 @@ d2x install d2mcpp
 
 ### Verify the environment
 
-> Run the full test suite once inside the project to confirm the toolchain works
+> Run the reference answers once inside the project to confirm the toolchain works
 
 ```bash
 cd d2mcpp
 mcpp test -p solutions       # verify the environment: 52 reference answers, all green
-mcpp test                    # your progress table: the exercises, all red for now
 ```
 
-> `solutions/` is a real mcpp package (`solutions/mcpp.toml` + `solutions/tests/`), so the first command actually compiles and runs all 52 reference answers — green means your toolchain is fine. The second is your own progress table: the exercises **are** the tests and they ship unfinished, so red is exactly where you start.
+> `solutions/` is a real mcpp package (`solutions/mcpp.toml` + `solutions/tests/`), so this command actually compiles and runs all 52 reference answers — green means your toolchain is ready.
 >
 > An answer and its exercise are paired by their `tests/`-relative path:
 > `solutions/tests/cpp11/00-auto-and-decltype/0.cpp` ←→ `src/cpp11/tests/00-auto-and-decltype/0.cpp`.
@@ -101,6 +100,7 @@ d2x status
 > Every C++ standard directory is a real mcpp project and the exercises are its tests/ — you can practice with plain mcpp, no d2x involved:
 
 ```bash
+mcpp test                              # your whole progress table (all red before you start)
 mcpp test -p src/en/cpp11              # progress table for the whole cpp11 section
 mcpp test -p src/en/cpp11 03-trailing  # run only exercises matching the name
 ```

book/src/README.md

@@ -74,12 +74,10 @@ xlings install d2x mcpp -y   # d2x: 练习框架 CLI | mcpp: C++ 构建与测试
 d2x install d2mcpp           # 下载课程,环境自动配置
 cd d2mcpp
 mcpp test -p solutions       # 验证环境: 52 份参考答案, 应当全绿
-mcpp test                    # 你的进度表: 练习还没做, 此刻全红
 ```
 
-> `solutions/` 本身就是一个 mcpp 工程, 所以第一条命令会真的编译并运行全部 52 份参考答案 ——
-> 全绿即工具链没问题, 这是个不含糊的信号。第二条才是你自己的进度表: 练习**就是**测试,
-> 而且发下来时是没做完的, 全红正是起点。
+> `solutions/` 本身就是一个 mcpp 工程, 所以这条命令会真的编译并运行全部 52 份参考答案 ——
+> 全绿即工具链就绪, 这是个不含糊的信号。
 
 <details>
   <summary>可选 - 改用 clone 项目源码的方式</summary>
@@ -90,7 +88,7 @@ mcpp test                    # 你的进度表: 练习还没做, 此刻全红
 git clone https://github.com/mcpp-community/d2mcpp.git   # 或你 fork 后的仓库
 cd d2mcpp
 xlings install -y            # 按 .xlings.json 安装固定版本工具链
-mcpp test                    # 同样的环境验证
+mcpp test -p solutions       # 同样的环境验证
 ```
 
 > 建议: 先 fork 本仓库再 clone 自己的 fork —— 通过 `git commit / push` 把练习进度保存到自己的仓库里。
@@ -106,7 +104,8 @@ d2x checker                  # 练习循环: 编辑 -> 保存 -> 自动检测 ->
 d2x status                   # 进度总览
 ```
 
-> 想单独跑某一章而不经过 d2x? 直接 `mcpp test -p src/cpp11` 同样可用。
+> 不想经过 d2x? 练习**就是**测试 —— `mcpp test` 打印你的完整进度表(动手前全红),
+> `mcpp test -p src/cpp11` 只跑某一章。
 
 **👉 [更多细节...](https://mcpp-community.github.io/d2mcpp/base/chapter_1.html)**
 

book/src/base/chapter_1.md

@@ -50,15 +50,14 @@ d2x install d2mcpp
 
 ### 验证环境
 
-> 进入项目目录后跑一遍全量测试, 确认工具链是通的
+> 进入项目目录后跑一遍参考答案, 确认工具链是通的
 
 ```bash
 cd d2mcpp
 mcpp test -p solutions       # 验证环境: 52 份参考答案, 应当全绿
-mcpp test                    # 你的进度表: 练习还没做, 此刻全红
 ```
 
-> `solutions/` 本身就是一个 mcpp 工程(`solutions/mcpp.toml` + `solutions/tests/`), 所以第一条命令会真的编译并运行全部 52 份参考答案 —— 全绿即工具链没问题。第二条才是你自己的进度表: 练习**就是**测试, 而且发下来时是没做完的, 全红正是起点。
+> `solutions/` 本身就是一个 mcpp 工程(`solutions/mcpp.toml` + `solutions/tests/`), 所以这条命令会真的编译并运行全部 52 份参考答案 —— 全绿即工具链就绪。
 >
 > 答案与练习的对应关系就是 `tests/` 下的相对路径:
 > `solutions/tests/cpp11/00-auto-and-decltype/0.cpp` ←→ `src/cpp11/tests/00-auto-and-decltype/0.cpp`。
@@ -101,6 +100,7 @@ d2x status
 > 每个 C++ 标准目录都是真实的 mcpp 工程,练习就是它的 tests/——不经过 d2x,直接用 mcpp 也能练:
 
 ```bash
+mcpp test                           # 你的完整进度表(动手前全红, 那就是起点)
 mcpp test -p src/cpp11              # 整个 cpp11 的进度表(哪题绿哪题红)
 mcpp test -p src/cpp11 03-trailing  # 只跑名字匹配的练习
 ```