repository layout: the Windows resource script of mcpp.exe moves to docs/res, the packaging and release scripts to tools, and the empty cdb.json committed by 2026.9.29.1 is removed

Author: speak-agent

.github/tools/check_modules_wiring.sh

@@ -100,7 +100,7 @@ fi
 # The two xmake source lists must actually carry the glob. Asserted by content
 # rather than by trusting the loop above: a renamed pattern would leave every
 # per-module check passing while compiling nothing.
-for f in scripts/bootstrap-macos.sh .github/workflows/bootstrap-macos.yml \
+for f in tools/bootstrap-macos.sh .github/workflows/bootstrap-macos.yml \
          bench/projects/mcpp/xmake.lua; do
     [[ -f "$f" ]] || { bad "$f is missing"; continue; }
     grep -qF 'modules/*/src/**.cppm' "$f" \
@@ -109,7 +109,7 @@ done
 
 # The vendored json header is reached through a private include dir. Its path
 # appears in three places and has already moved once.
-for f in scripts/bootstrap-macos.sh .github/workflows/bootstrap-macos.yml \
+for f in tools/bootstrap-macos.sh .github/workflows/bootstrap-macos.yml \
          bench/projects/mcpp/xmake.lua; do
     grep -qF 'modules/libs/src/json' "$f" \
         || bad "$f does not add the json include dir (modules/libs/src/json)"

.github/workflows/aur-publish.yml

@@ -58,7 +58,7 @@ jobs:
           TRIGGER: ${{ github.event_name }}
           MANUAL_PUBLISH: ${{ inputs.publish }}
           # Repository variable, absent until a human has watched one publish
-          # succeed. See "Arming the automatic triggers" in scripts/aur/README.md.
+          # succeed. See "Arming the automatic triggers" in tools/aur/README.md.
           AUTOPUBLISH: ${{ vars.AUR_AUTOPUBLISH }}
         run: |
           args=(
@@ -67,7 +67,7 @@ jobs:
             --summary "$GITHUB_STEP_SUMMARY"
           )
           [[ -z "$REQUESTED_TAG" ]] || args+=(--tag "$REQUESTED_TAG")
-          python3 scripts/aur/reconcile_mcpp_bin.py "${args[@]}"
+          python3 tools/aur/reconcile_mcpp_bin.py "${args[@]}"
 
           # An unattended push to a third-party service must be ARMED, not
           # inherited from a merge. `schedule` fires every six hours off the
@@ -102,7 +102,7 @@ jobs:
           install -dm700 "$HOME/.ssh"
           install -m600 /dev/null "$HOME/.ssh/aur"
           printf '%s\n' "$AUR_SSH_PRIVATE_KEY" > "$HOME/.ssh/aur"
-          install -m600 scripts/aur/aur.archlinux.org.known_hosts "$HOME/.ssh/known_hosts"
+          install -m600 tools/aur/aur.archlinux.org.known_hosts "$HOME/.ssh/known_hosts"
           ssh-keygen -lf "$HOME/.ssh/known_hosts" -E sha256 \
             | grep -F 'SHA256:RFzBCUItH9LZS0cKB5UE6ceAYhBD5C8GeOBip8Z11+4'
           install -m600 /dev/null "$HOME/.ssh/config"
@@ -145,7 +145,7 @@ jobs:
           # EVERY OTHER NON-ZERO CODE STILL FAILS. A refused downgrade (3) and
           # a permanent error (2) are this repository's problem and stay red.
           set +e
-          python3 scripts/aur/reconcile_mcpp_bin.py "${args[@]}"
+          python3 tools/aur/reconcile_mcpp_bin.py "${args[@]}"
           rc=$?
           set -e
           if [[ "$rc" == "75" ]]; then

.github/workflows/pypi-publish.yml

@@ -9,7 +9,7 @@ name: pypi-publish
 # CREDENTIALS: none stored. Publishing uses PyPI Trusted Publishing (OIDC):
 # PyPI trusts this repository + workflow file + the `pypi` environment, and
 # the job exchanges its GitHub OIDC token for a short-lived upload token.
-# One-time setup is in scripts/pypi/README.md.
+# One-time setup is in tools/pypi/README.md.
 #
 # ARMING: the automatic trigger builds, verifies and reports, and publishes
 # only when the repository variable PYPI_AUTOPUBLISH is `true`, for the reason
@@ -25,7 +25,7 @@ on:
   # latest release on every platform. A pull request never publishes.
   pull_request:
     paths:
-      - scripts/pypi/**
+      - tools/pypi/**
       - tests/scripts/test_pypi_wheels.py
       - .github/workflows/pypi-publish.yml
   workflow_dispatch:
@@ -116,7 +116,7 @@ jobs:
           echo "mcpp-bin $version from $tag; publish=$publish" >> "$GITHUB_STEP_SUMMARY"
 
       - name: Build wheels from the release manifest
-        run: python3 scripts/pypi/build_wheels.py --tag "${{ steps.resolve.outputs.tag }}" --out dist
+        run: python3 tools/pypi/build_wheels.py --tag "${{ steps.resolve.outputs.tag }}" --out dist
 
       - name: Check metadata
         run: |

.github/workflows/release.yml

@@ -818,7 +818,7 @@ jobs:
             > "$AUDIT_ROOT/release.json"
           gh release download "$TAG" --repo "$GITHUB_REPOSITORY" \
             --dir "$AUDIT_ROOT/assets"
-          python3 scripts/release/generate_manifest.py \
+          python3 tools/release/generate_manifest.py \
             --release-json "$AUDIT_ROOT/release.json" \
             --assets-dir "$AUDIT_ROOT/assets" \
             --version "$VERSION" \
@@ -856,7 +856,7 @@ jobs:
           gh release download "$TAG" --repo "$GITHUB_REPOSITORY" \
             --dir "$AUDIT_ROOT/final-assets"
           test -f "$AUDIT_ROOT/final-assets/mcpp-release.json"
-          python3 scripts/release/generate_manifest.py \
+          python3 tools/release/generate_manifest.py \
             --release-json "$AUDIT_ROOT/final-release.json" \
             --assets-dir "$AUDIT_ROOT/final-assets" \
             --version "$VERSION" \

README.md

@@ -159,7 +159,7 @@ yay -S mcpp-m        # or build from source (bootstrapped with mcpp-bin)
 
 Installs the `mcpp` command system-wide; per-user data still lives in `~/.mcpp/`.
 On Arch the name `mcpp` is an unrelated C preprocessor, so the packages are
-`mcpp-bin` / `mcpp-m` (see [`scripts/aur/`](scripts/aur/)).
+`mcpp-bin` / `mcpp-m` (see [`tools/aur/`](tools/aur/)).
 Stable-release automation reconciles `mcpp-bin` only; `mcpp-m` and `mcpp-git`
 remain manually maintained and may intentionally lag.
 
@@ -177,7 +177,7 @@ mcpp-bin` gives it an environment of its own. The wheels carry the same
 prebuilt release binary for Linux x86_64 / aarch64, macOS 14+ on Apple silicon
 and Windows x86_64. Per-user data still lives in `~/.mcpp/`, outside the Python
 environment. On PyPI the name `mcpp` belongs to an unrelated project, hence
-`mcpp-bin` (see [`scripts/pypi/`](scripts/pypi/)).
+`mcpp-bin` (see [`tools/pypi/`](tools/pypi/)).
 
 </details>
 

README.zh-CN.md

@@ -146,7 +146,7 @@ yay -S mcpp-bin      # 预编译 release 二进制
 yay -S mcpp-m        # 或源码构建（用 mcpp-bin 自举）
 ```
 
-`mcpp` 命令安装到系统级位置，每个用户的数据仍在各自的 `~/.mcpp/` 中。Arch 上 `mcpp` 这个名字属于一个无关的 C 预处理器，因此包名为 `mcpp-bin` / `mcpp-m`（见 [`scripts/aur/`](scripts/aur/)）。稳定版 release 的自动同步只管理 `mcpp-bin`；`mcpp-m` 与 `mcpp-git` 仍由人工维护，版本可能有意滞后。
+`mcpp` 命令安装到系统级位置，每个用户的数据仍在各自的 `~/.mcpp/` 中。Arch 上 `mcpp` 这个名字属于一个无关的 C 预处理器，因此包名为 `mcpp-bin` / `mcpp-m`（见 [`tools/aur/`](tools/aur/)）。稳定版 release 的自动同步只管理 `mcpp-bin`；`mcpp-m` 与 `mcpp-git` 仍由人工维护，版本可能有意滞后。
 
 </details>
 
@@ -157,7 +157,7 @@ yay -S mcpp-m        # 或源码构建（用 mcpp-bin 自举）
 pip install mcpp-bin
 ```
 
-`mcpp` 命令安装到当前的 Python 环境中；使用 `pipx install mcpp-bin` 则为它单独创建一个环境。wheel 中是同一份预编译 release 二进制，支持 Linux x86_64 / aarch64、Apple 芯片上的 macOS 14+ 与 Windows x86_64。每个用户的数据仍在各自的 `~/.mcpp/` 中，不在 Python 环境内。PyPI 上 `mcpp` 这个名字属于一个无关的项目，因此包名为 `mcpp-bin`（见 [`scripts/pypi/`](scripts/pypi/)）。
+`mcpp` 命令安装到当前的 Python 环境中；使用 `pipx install mcpp-bin` 则为它单独创建一个环境。wheel 中是同一份预编译 release 二进制，支持 Linux x86_64 / aarch64、Apple 芯片上的 macOS 14+ 与 Windows x86_64。每个用户的数据仍在各自的 `~/.mcpp/` 中，不在 Python 环境内。PyPI 上 `mcpp` 这个名字属于一个无关的项目，因此包名为 `mcpp-bin`（见 [`tools/pypi/`](tools/pypi/)）。
 
 </details>
 

bench/README.md

@@ -1069,7 +1069,7 @@ bench --project . --buildfiles bench/projects/mcpp \
 `--buildfiles` is what keeps these files **out of the repository root**. mcpp is
 built by mcpp; a CMakeLists.txt and an xmake.lua at the root are files every
 contributor has to learn to ignore, and one of them actively broke something:
-`scripts/bootstrap-macos.sh` generates its own root `xmake.lua` when none is
+`tools/bootstrap-macos.sh` generates its own root `xmake.lua` when none is
 present, and a bench-owned file at that path silently pre-empted it. cmake is
 pointed at the directory with `-S`, xmake with `-P`; mcpp reads the project's
 own manifest and ignores the flag. Copying the descriptions into the tree for

cdb.json

@@ -89,7 +89,7 @@ The workflow then downloads the public release again, regenerates the manifest,
 and requires a byte-for-byte match. A workflow rerun accepts an existing
 manifest only when it is already byte-identical; it never overwrites different
 bytes for the same tag. Downstream release consumers (notably the `mcpp-bin`
-AUR reconciler and the `mcpp-bin` PyPI wheel builder in `scripts/pypi/`) must consume this manifest instead of guessing completeness
+AUR reconciler and the `mcpp-bin` PyPI wheel builder in `tools/pypi/`) must consume this manifest instead of guessing completeness
 from a moving workspace or from a subset of release assets.
 
 Two steps are **not** automated:
@@ -156,7 +156,7 @@ AUDIT=$(mktemp -d)
 mkdir -p "$AUDIT/assets"
 gh api "repos/mcpp-community/mcpp/releases/tags/$TAG" > "$AUDIT/release.json"
 gh release download "$TAG" -R mcpp-community/mcpp --dir "$AUDIT/assets"
-python3 scripts/release/generate_manifest.py \
+python3 tools/release/generate_manifest.py \
   --release-json "$AUDIT/release.json" \
   --assets-dir "$AUDIT/assets" \
   --version "$V" \