From 5d258482fb84d58c966a7ccc1b467708278d28ad Mon Sep 17 00:00:00 2001
From: 魏曹先生 <1992414357@qq.com>
Date: Fri, 10 Jul 2026 16:54:57 +0800
Subject: refactor(devtools): rename dev_tools to .run and replace run-tools
 scripts

Replace the old run-tools.ps1/run-tools.sh scripts with a new
unified run.ps1/run.sh launcher that supports multiple languages
(PowerShell, Rust, Python, Go, C#, Nim, Perl, Ruby, Zig, and
arbitrary binaries) from the `.run/src/bin` directory.

Move all development tools from `dev_tools/` to `.run/`, update
Cargo workspace config and relevant documentation references.
---
 ABOUT-CI.md | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

(limited to 'ABOUT-CI.md')

diff --git a/ABOUT-CI.md b/ABOUT-CI.md
index 762fab8..4cbcd6f 100644
--- a/ABOUT-CI.md
+++ b/ABOUT-CI.md
@@ -1,6 +1,6 @@
 # About Mingling CI Process
 
-Mingling's CI process is built into the project, with its execution logic located in `dev_tools/src/bin/ci.rs`. You can run it locally via the `cargo ci` command, which produces the same results as the `CI` workflow in GitHub Actions.
+Mingling's CI process is built into the project, with its execution logic located in `.run/src/bin/ci.rs`. You can run it locally via the `cargo ci` command, which produces the same results as the `CI` workflow in GitHub Actions.
 
 During development, you can run `cargo ci` at any time to verify that your code hasn't introduced regressions.
 
@@ -10,7 +10,7 @@ An alias is defined in `.cargo/config.toml` at the project root:
 
 ```toml
 [alias]
-ci = "run --manifest-path dev_tools/Cargo.toml --bin ci --quiet --"
+ci = "run --manifest-path .run/Cargo.toml --bin ci --quiet --"
 ```
 
 Simply execute:
@@ -34,11 +34,11 @@ cargo ci
 - **Test all examples**: Runs the `test-examples` tool.
 - **Verify Markdown code blocks compile**: Runs the `test-all-markdown-code` tool to check code blocks in all `*.md` files. See [ABOUT_CODE_VERIFY](docs/_ABOUT_CODE_VERIFY.md) for details.
 - **Check if documentation is up to date**: Runs the following documentation refresh tools in sequence:
-    - `docs-code-box-fix`
-    - `docsify-sidebar-gen`
-    - `refresh-docs`
-    - `refresh-feature-mod`
-    - `sync-examples`
+  - `docs-code-box-fix`
+  - `docsify-sidebar-gen`
+  - `refresh-docs`
+  - `refresh-feature-mod`
+  - `sync-examples`
 - Finally, runs `cargo fmt` to unify code formatting.
 
 ### 3. File Normalization
@@ -50,11 +50,11 @@ Runs `git add --renormalize .` to ensure file attributes such as line endings co
 To ensure reproducible CI results, `ci.rs` imposes strict requirements on the workspace state:
 
 - If the current workspace is not clean and `--dirty` has not been specified, the script will prompt whether to create a temporary commit:
-    - The commit message is `[DO NOT PUSH] CI TEMP [DO NOT PUSH]`.
-    - Use `-y` to auto-confirm without interaction.
+  - The commit message is `[DO NOT PUSH] CI TEMP [DO NOT PUSH]`.
+  - Use `-y` to auto-confirm without interaction.
 - After CI finishes, the script automatically restores the workspace:
-    - First, `git reset --hard` discards all changes.
-    - If a temporary commit was created, it then runs `git reset --soft HEAD~1` and unstages everything, restoring the state to before CI started.
+  - First, `git reset --hard` discards all changes.
+  - If a temporary commit was created, it then runs `git reset --soft HEAD~1` and unstages everything, restoring the state to before CI started.
 - If `--dirty` is specified, the temporary commit and the final cleanliness check are skipped.
 
 > **Warning**: `git reset --hard` is executed at the end of CI. If you use `--dirty`, ensure you have no unsaved important changes.
-- 
cgit