@chengzhao-dev/dsh-cpp-workflow 0.1.0 → 0.2.0

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 chengzhao-dev
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+MIT License
+
+Copyright (c) 2026 chengzhao-dev
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.

package/README.en.md

@@ -2,41 +2,38 @@
 
 [中文](README.md)
 
-Two skills for C++20 source work and build work. The plugin registers a skill provider only; it does not register tools, compile, download a toolchain, or write project files.
+Two skills for C++11–C++23 source and build work; new projects default to C++23. The plugin registers a skill provider only; it does not register tools, compile, download a toolchain, or write project files.
 
 ## What it provides
 
 | Skill | Covers | Open it when |
 | --- | --- | --- |
-| `developing-cpp` | Behavior, boundaries, declarations, implementation; naming, exceptions, and source comments in `.h` / `.cpp` | The user names source code, or the work is a new project or whole-stage refactor |
+| `developing-cpp` | Behavior, boundaries, declarations, implementation; naming, exceptions, and source comments in `.h` / `.cc` | The user names source code, or the work is a new project or whole-stage refactor |
 | `building-cpp` | Build setup, tool configuration, checks; CMake, Ninja, Clang config, build scripts, and environment combinations | The change touches build files, tool config, or the environment declaration, or the project is first connected to a build |
 
-Both skills read the project skill `cpp-workflow-project` first. Without it, the workspace gate never exposes these names.
+The exception material follows the C++ Core Guidelines' Error handling section and guides source and examples only during development; the plugin runtime never compiles or executes those rules. Both skills read the project skill `cpp-workflow-project` first. Without it, the workspace gate never exposes these names.
 
 ## Install
 
 Pinned npm install:
 
 ```bash
-dsh plugin --profile web add npm:@chengzhao-dev/dsh-cpp-workflow@0.1.0
+dsh plugin --profile web add npm:@chengzhao-dev/dsh-cpp-workflow@0.2.0
 ```
 
 The matching Git tag:
 
 ```bash
-dsh plugin --profile web add github:chengzhao-dev/dsh-cpp-workflow#v0.1.0
+dsh plugin --profile web add github:chengzhao-dev/dsh-cpp-workflow#v0.2.0
 ```
 
 The desktop app owns the `desktop` profile. If the command-line `add` is rejected, add the plugin in the app settings and use the same pinned npm version. A Git tag install uses the prebuilt `lib/` committed in the repository and runs no build on the target machine; the package has no install script that needs approval.
 
 ## Workspace gate
 
-Both conditions must hold before either skill appears:
+Only one condition must hold before either skill appears: walking up from the current directory to the Git root, the path contains `.agents/skills/cpp-workflow-project/SKILL.md`.
 
-1. Walking up from the current directory to the Git root, the path contains `.agents/skills/cpp-workflow-project/SKILL.md`.
-2. Inside the same Git repository that owns the marker, outside the skipped directories, there is a first-party `CMakeLists.txt`, or a `.c`, `.cc`, `.cpp`, `.cxx`, `.h`, `.hh`, `.hpp`, or `.hxx` source file.
-
-If either condition fails, the list is empty: without the project skill, CMake or `.cpp` files alone do not match; with the project skill but no first-party CMake or C++ source file in the repository, the result is also empty. A docs-only repository or one that only copied the template does not match. Scan limits, skipped directories, and the eight boundary cases are in [docs/plugin-boundaries.md](https://github.com/chengzhao-dev/dsh-cpp-workflow/blob/main/docs/plugin-boundaries.md).
+The project skill marker is the repository's opt-in declaration. The plugin no longer requires a first-party `CMakeLists.txt` or C++ source file in the same repository: a docs-only repository, a repository that only copied the template, or a repository with no source files yet still matches; with an empty environment axis, the four source steps still work but build setup stops. Without the marker the list is empty, even when the repository contains CMake or `.cpp` files. Scan limits and boundary cases are in [docs/plugin-boundaries.md](https://github.com/chengzhao-dev/dsh-cpp-workflow/blob/main/docs/plugin-boundaries.md).
 
 The packaged skills use rank 550. A project `.agents/skills` skill uses rank 200 and overrides a plugin skill with the same name; do not copy `developing-cpp` or `building-cpp` into a project.
 
@@ -49,7 +46,7 @@ Copy [templates/cpp-workflow-project](templates/cpp-workflow-project) into the t
 - an entry command that runs from the repository root;
 - stage-table path and terminology additions.
 
-Keep one `environment.json` per repository. Its three axes are intentionally empty in the template and must be filled with the project's real combination after copying; while empty, the four source steps still work, but build setup stops. The stage table records observable behavior, not internal refactors.
+Keep one `environment.json` per repository. Its first three environment axes are intentionally empty in the template and must be filled with the project's real combination after copying; `standard` defaults to `c++23` and may be changed to `c++11`–`c++23`. While the axes are empty, the four source steps still work, but build setup stops. The stage table records observable behavior, not internal refactors.
 
 ## Environment combinations
 
@@ -58,6 +55,9 @@ Keep one `environment.json` per repository. Its three axes are intentionally emp
 | `host` | `windows`, `linux`, `macos` | Where the editor and agent shell run |
 | `build_host` | `native`, `wsl` | `wsl` is valid only with `host=windows` |
 | `compiler` | `clang`, `gcc` | One compiler per configuration |
+| `standard` | `c++11`, `c++14`, `c++17`, `c++20`, `c++23` | New projects default to `c++23`; one standard per project |
+
+The standard lives in `environment.json` as `standard` and must match the CMake target and compile database. New projects default to C++23; for C++11–C++20, lower `standard`, `cxx_std_*`, `CXX_STANDARD`, and the `.clang-format` parsing level together, not one at a time. Per-standard facilities, tooling, and downgrade tables are in the [standard directory](skills/building-cpp/references/standards/README.md).
 
 The generator is always Ninja. Build directories are `build/clang/` and `build/gcc/`; they are never shared. Analysis tools are always `clang-format`, `clang-tidy`, and `clangd`; GCC mode does not switch to another analyzer.
 
@@ -68,7 +68,9 @@ node "<skill-dir>/scripts/checking-environment.mjs" --project .
 node "<skill-dir>/scripts/checking-environment.mjs" --project . --live
 ```
 
-`windows + native` is a valid combination, but this version ships no PowerShell build script; `--live` reports the missing POSIX shell, not a missing compiler. The checker never installs, downloads, or edits PATH.
+`windows + native` is not a valid combination in this version: the declaration check returns `ok: false` with the single issue `本版本不能在 Windows 原生壳里构建`. Stop there; do not add a PowerShell script or work around it by editing the declaration. The checker never installs, downloads, or edits PATH.
+
+The project root carries only `.vscode/extensions.json` and `settings.json`: clangd (editing, completion, formatting), CMake Tools (the single configure/build/run/debug entry point), and the C/C++ extension (debug backend for CMake quick debugging only). There is no `tasks.json` or `launch.json`, so there is no second build or launch path. On Windows, open the project root through Remote - WSL; select the launch target in the CMake sidebar and run `CMake: Debug`. clangd reads the language standard from `build/<compiler>/compile_commands.json`; do not put `-std` in `.clangd`. The C/C++ extension's IntelliSense is disabled so editing and diagnostics come only from clangd.
 
 ## Package layout
 
@@ -95,12 +97,12 @@ Requires Node.js 22 or newer.
 
 ```bash
 npm ci
-npm test           # build, structural check, gate/environment/schema tests
-npm run check      # same as npm test
-npm run pack:check # inspect the npm package contents
+npm test              # build, structural check, gate/environment/schema tests
+npm run test:matrix   # real build matrix: 4 templates x 5 standards
+npm run pack:check    # inspect the npm package contents
 ```
 
-Source lives in `src/`; `npm run build` writes `lib/`. The structural check is `scripts/checking-skill-links.mjs`. Tests do not invoke a local compiler; the environment checks use fixed version strings.
+Source lives in `src/`; `npm run build` writes `lib/`. The structural check is `scripts/checking-skill-links.mjs`. Tests do not invoke a local compiler; the environment checks use fixed version strings. The standard matrix needs `cmake`, `ninja`, `perl`, and `clang++` (or the compiler named by `CXX`) on a POSIX host such as WSL, Linux, or macOS.
 
 ## License
 

package/README.md

@@ -2,41 +2,38 @@
 
 [English](README.en.md)
 
-把 C++20 的源码工作和构建工作收成两个技能。插件只注册技能 provider，不注册工具、不编译、不下载工具链、不写项目文件。
+把 C++11–C++23 的源码工作和构建工作收成两个技能，新工程默认 C++23。插件只注册技能 provider，不注册工具、不编译、不下载工具链、不写项目文件。
 
 ## 提供什么
 
 | 技能 | 管什么 | 什么时候打开 |
 | --- | --- | --- |
-| `developing-cpp` | 定行为、定边界、定声明、定实现；`.h` / `.cpp` 的命名、异常和源码注释 | 用户点名源码，或需要新建/整段重构源码 |
+| `developing-cpp` | 定行为、定边界、定声明、定实现；`.h` / `.cc` 的命名、异常和源码注释 | 用户点名源码，或需要新建/整段重构源码 |
 | `building-cpp` | 定构建、定工具配置、通过检查；CMake、Ninja、Clang 配置、构建脚本和环境组合 | 改动落在构建文件、工具配置或环境声明上，或第一次接构建 |
 
-两个技能都先读项目技能 `cpp-workflow-project`。没有项目技能时，门禁不会放出这两个名字。
+异常条文采用 C++ Core Guidelines 的 Error handling，只在开发阶段指导源码和示例；插件运行时不编译、不执行这些规则。两个技能都先读项目技能 `cpp-workflow-project`。没有项目技能时，门禁不会放出这两个名字。
 
 ## 安装
 
 npm 安装钉死版本：
 
 ```bash
-dsh plugin --profile web add npm:@chengzhao-dev/dsh-cpp-workflow@0.1.0
+dsh plugin --profile web add npm:@chengzhao-dev/dsh-cpp-workflow@0.2.0
 ```
 
 同版本的 Git 标签：
 
 ```bash
-dsh plugin --profile web add github:chengzhao-dev/dsh-cpp-workflow#v0.1.0
+dsh plugin --profile web add github:chengzhao-dev/dsh-cpp-workflow#v0.2.0
 ```
 
 桌面应用独占 `desktop` profile。命令行 `add` 被拒绝时，在应用设置里添加插件，地址填同一个 npm 版本。Git 标签安装使用仓库内已构建的 `lib/`，不在目标机器上重新构建；包内也不含需要授权执行的安装脚本。
 
 ## 工作区门禁
 
-一个会话里要同时满足两件事，技能才会出现：
+一个会话里只需要满足一件事，技能就会出现：从当前目录向上、停在 git 根，沿途有 `.agents/skills/cpp-workflow-project/SKILL.md`。
 
-1. 从当前目录向上、停在 git 根，沿途有 `.agents/skills/cpp-workflow-project/SKILL.md`。
-2. 这份标记所在的 git 仓库里，跳过目录之外，有第一方 `CMakeLists.txt`，或有 `.c`、`.cc`、`.cpp`、`.cxx`、`.h`、`.hh`、`.hpp`、`.hxx` 源文件。
-
-缺一件就返回空列表：没有项目技能时，即使仓库里有 CMake 或 `.cpp` 也不命中；有项目技能、但仓库里没有第一方 CMake 或 C++ 源文件，同样不命中。纯文档仓库、只复制了模板的仓库也不命中。扫描上限、跳过目录和八类边界情形见 [docs/plugin-boundaries.md](https://github.com/chengzhao-dev/dsh-cpp-workflow/blob/main/docs/plugin-boundaries.md)。
+项目技能标记就是仓库选择加入本工作流的声明。插件不再要求同一仓库里已经有第一方 `CMakeLists.txt` 或 C++ 源文件：纯文档仓库、只复制了模板、还没有任何源文件的仓库也会出现；环境轴为空时，源码四步仍能做，但定构建会停。没有标记就返回空列表，即使仓库里有 CMake 或 `.cpp`。扫描上限和边界情形见 [docs/plugin-boundaries.md](https://github.com/chengzhao-dev/dsh-cpp-workflow/blob/main/docs/plugin-boundaries.md)。
 
 插件技能 rank 550。项目自己的 `.agents/skills` 技能 rank 200，会以同名覆盖插件；不要在项目里复制 `developing-cpp` 或 `building-cpp`。
 
@@ -49,7 +46,7 @@ dsh plugin --profile web add github:chengzhao-dev/dsh-cpp-workflow#v0.1.0
 - 从仓库根能直接运行的入口命令；
 - 阶段表路径和术语增补。
 
-`environment.json` 一个仓库只有一份。模板里的三个轴故意留空，复制后必须填成工程的真实组合；留空时源码四步仍能做，但定构建会停。阶段表只写可观察行为，不写内部重构。
+`environment.json` 一个仓库只有一份。模板里的前三个环境轴故意留空，`standard` 预置为 `c++23`；复制后把环境轴填成工程的真实组合，需要旧标准时再改 `standard`。环境轴留空时源码四步仍能做，但定构建会停。阶段表只写可观察行为，不写内部重构。
 
 ## 环境组合
 
@@ -58,6 +55,9 @@ dsh plugin --profile web add github:chengzhao-dev/dsh-cpp-workflow#v0.1.0
 | `host` | `windows`、`linux`、`macos` | 编辑器和代理壳在哪 |
 | `build_host` | `native`、`wsl` | `wsl` 只在 `host=windows` 时合法 |
 | `compiler` | `clang`、`gcc` | 一次配置一个编译器 |
+| `standard` | `c++11`、`c++14`、`c++17`、`c++20`、`c++23` | 新工程默认 `c++23`；一个工程一个标准 |
+
+标准写在 `environment.json` 的 `standard`，并同步到 CMake target 和编译数据库。新工程默认 C++23；C++11–C++20 工程把 `standard`、`cxx_std_*`、`CXX_STANDARD` 和 `.clang-format` 的解析档位一起降级，不要只改一处。每档的设施、工具和降档表见 [标准目录](skills/building-cpp/references/standards/README.md)。
 
 生成器固定 Ninja，构建目录是 `build/clang/` 与 `build/gcc/`，不共用 `build/`。诊断工具固定 `clang-format`、`clang-tidy`、`clangd`；GCC 模式也不换成别的分析器。
 
@@ -68,7 +68,9 @@ node "<skill-dir>/scripts/checking-environment.mjs" --project .
 node "<skill-dir>/scripts/checking-environment.mjs" --project . --live
 ```
 
-`windows + native` 是合法组合，但本版没有 PowerShell 构建脚本；`--live` 会明确报告缺 POSIX 壳，而不是缺编译器。环境脚本不安装、不下载、不改 PATH。
+`windows + native` 在本版本中不是合法组合：声明校验直接返回 `ok: false`，`issues` 只有一句「本版本不能在 Windows 原生壳里构建」。停在这里，不要补 PowerShell 脚本，也不要靠改声明绕过。环境脚本不安装、不下载、不改 PATH。
+
+工程根只带 `.vscode/extensions.json` 和 `settings.json`：推荐 clangd（编辑、补全、格式化）、CMake Tools（唯一的配置、构建、运行和调试入口）与 C/C++ 扩展（只作为 CMake 快速调试的后端）。不提供 `tasks.json` 或 `launch.json`，不维护第二套构建或启动路径。Windows 上用 Remote - WSL 打开工程根；在 CMake 侧栏选中 Launch target 后按 `CMake: Debug`。clangd 从 `build/<compiler>/compile_commands.json` 读语言标准，`.clangd` 不写 `-std`；C/C++ 扩展的 IntelliSense 关闭，编辑与诊断只由 clangd 提供。
 
 ## 包结构
 
@@ -95,12 +97,12 @@ dsh-cpp-workflow/
 
 ```bash
 npm ci
-npm test           # 构建、结构检查、门禁/环境/schema 测试
-npm run check      # 同 npm test
-npm run pack:check # 核对 npm 包内容
+npm test              # 构建、结构检查、门禁/环境/schema 测试
+npm run test:matrix   # 四套模板 × 五档标准的真实构建矩阵
+npm run pack:check    # 核对 npm 包内容
 ```
 
-源码在 `src/`，`npm run build` 生成 `lib/`。结构检查在 `scripts/checking-skill-links.mjs`；测试不调用本机编译器，环境检查用固定版本字符串。
+源码在 `src/`，`npm run build` 生成 `lib/`。结构检查在 `scripts/checking-skill-links.mjs`；测试不调用本机编译器，环境检查用固定版本字符串。标准矩阵需要 POSIX 宿主上的 `cmake`、`ninja`、`perl` 和 `clang++`（或 `CXX` 指定的编译器），在 WSL/Linux/macOS 上运行。
 
 ## 许可
 

package/cordis.patch.yml

@@ -4,11 +4,8 @@
 # replaced. The row loads this package's `main` entry, which registers the
 # packaged developing-cpp and building-cpp skills through `ctx.skills`.
 #
-# Install from npm or from the matching Git tag, for example:
-#
-#   dsh plugin --profile web add npm:@chengzhao-dev/dsh-cpp-workflow@0.1.0
-#   dsh plugin --profile web add github:chengzhao-dev/dsh-cpp-workflow#v0.1.0
-#
+# Install with `dsh plugin --profile <name> add <package>`. Pinned npm and Git
+# tag addresses are in the README's Install section.
 - insert:
     - id: cpp-workflow
       name: "@chengzhao-dev/dsh-cpp-workflow"

package/lib/index.js

@@ -5,14 +5,13 @@
 // directory becomes the resourceBase so relative steps, references, examples
 // and assets resolve from the installed package.
 //
-// The provider scopes itself to real C++ workflow workspaces: `list()` returns
-// nothing unless the session cwd sits inside a git checkout that carries the
-// explicit `.agents/skills/cpp-workflow-project/SKILL.md` marker on the path to
-// the git root AND that checkout has first-party C++ or CMake evidence. A
-// Markdown-only repository, a docs folder, a project template, or a C++ sample
-// outside the checkout never sees these names. Source evidence is repository-
-// wide once the marker opts the checkout in; only the marker lookup ignores
-// sibling directories.
+// The provider scopes itself to opted-in workspaces: `list()` returns nothing
+// unless the session cwd sits inside a git checkout that carries the explicit
+// `.agents/skills/cpp-workflow-project/SKILL.md` marker on the path to the git
+// root. C++ or CMake evidence is intentionally not part of the gate: a freshly
+// copied template has no sources yet, and an empty project legitimately stops
+// at the build step. A C++ sample outside an opted-in checkout never sees these
+// names; the marker lookup ignores sibling directories.
 //
 // Rank 550 is lower priority than project/user skills (project `.agents/skills`
 // 200, user `.agents/skills` 500) and higher priority than the bundled root

package/lib/workspace.js

@@ -1,11 +1,11 @@
 // Workspace evidence for dsh-cpp-workflow.
 //
 // A repository opts in only when it carries the project skill on the path from
-// the session cwd up to the git root AND that repository carries first-party C++
-// or CMake evidence. A stray `CMakeLists.txt`, a sample under `templates/`, or a
-// CMake file above the git root is never enough. The git root is the
-// repository boundary: once the marker opts the repository in, evidence is
-// searched across the repository, not outside it or in a sibling checkout.
+// the session cwd up to the git root. The marker is the opt-in declaration;
+// first-party C++ or CMake evidence is deliberately not part of the gate, so a
+// freshly copied template still sees the workflow. The git root is the
+// repository boundary: marker lookup ignores sibling directories and never
+// searches above the root.
 import { access, readdir } from 'node:fs/promises';
 import path from 'node:path';
 export const PROJECT_SKILL = path.join('.agents', 'skills', 'cpp-workflow-project', 'SKILL.md');
@@ -66,7 +66,7 @@ export async function findGitRoot(cwd) {
 /**
  * Find the nearest project-skill marker between `cwd` and the git root,
  * inclusive. A marker above the git root never counts. The marker's directory
- * is also returned for diagnostics, but evidence is repository-wide.
+ * is also returned for diagnostics; it is not the repository boundary.
  */
 export async function findProjectSkill(cwd, gitRoot) {
     if (typeof cwd !== 'string' || cwd.trim() === '')
@@ -151,18 +151,18 @@ export async function hasCppProject(root) {
     return false;
 }
 /**
- * Session gate. Both halves are required:
- *   1. the project skill sits between `cwd` and the git root (inclusive), and
- *   2. that git repository contains first-party C++ or CMake evidence.
- * No cwd, no git checkout, a marker above the git root, a marker only in a
- * sibling directory, or a documentation-only repository returns false.
+ * Session gate. The project skill must sit between `cwd` and the git root
+ * (inclusive). First-party C++ or CMake evidence is deliberately not required:
+ * a freshly copied template still needs the workflow, and an empty project
+ * legitimately stops at the build step.
+ *
+ * No cwd, no git checkout, a marker above the git root, or a marker only in a
+ * sibling directory returns false.
  */
 export async function isCppWorkflowWorkspace(cwd) {
     const gitRoot = await findGitRoot(cwd);
     if (!gitRoot)
         return false;
     const project = await findProjectSkill(cwd, gitRoot);
-    if (!project)
-        return false;
-    return hasCppProject(gitRoot);
+    return project !== undefined;
 }

package/locale/en.json

@@ -1,6 +1,6 @@
 {
   "meta": {
     "title": "C++ Workflow",
-    "description": "Four source steps and three build steps for C++20 projects, checked against the environment the project declares."
+    "description": "Four source steps and three build steps for C++11–C++23 projects (C++23 by default), checked against the environment the project declares."
   }
 }

package/locale/zh.json

@@ -1,6 +1,6 @@
 {
   "meta": {
     "title": "C++ 工程流程",
-    "description": "用源码四步与构建三步推进 C++20 工程，并在项目声明的环境组合里核对构建与 clang 工具链。"
+    "description": "用源码四步与构建三步推进 C++11–C++23 工程（默认 C++23），并在项目声明的环境组合里核对构建与 clang 工具链。"
   }
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@chengzhao-dev/dsh-cpp-workflow",
-  "version": "0.1.0",
-  "description": "C++20 工程流程技能包：源码四步与构建三步，按项目声明的环境组合校验 · C++20 workflow skills for DeepSeek Harness",
+  "version": "0.2.0",
+  "description": "C++11–C++23 工程流程技能包：源码四步与构建三步，按项目声明的环境组合校验 · C++11–C++23 workflow skills for DeepSeek Harness",
   "type": "module",
   "main": "./lib/index.js",
   "exports": {
@@ -31,8 +31,8 @@
     "catalog": {
       "category": "skill",
       "summary": {
-        "zh": "按项目声明的环境组合，推进 C++20 源码与构建流程",
-        "en": "Advance C++20 source and build work with a project-declared environment"
+        "zh": "按项目声明的环境组合，推进 C++11–C++23 源码与构建流程",
+        "en": "Advance C++11–C++23 source and build work with a project-declared environment"
       },
       "capabilities": [
         "skills"
@@ -43,7 +43,7 @@
   "scripts": {
     "build": "tsc -p tsconfig.json",
     "test": "npm run build && node scripts/checking-skill-links.mjs && node --test tests/*.test.mjs",
-    "check": "npm test",
+    "test:matrix": "bash scripts/checking-standard-matrix.sh",
     "pack:check": "npm pack --dry-run"
   },
   "keywords": [

package/skills/building-cpp/SKILL.md

@@ -1,19 +1,19 @@
 ---
 name: building-cpp
-description: 用 CMake、Ninja、clang-format、clang-tidy、clangd 配置、构建和检查 C++20 工程时使用；按定构建、定工具配置、通过检查三步推进。不用于只改源码语义、文档、Python 或与 C++ 无关的文件。
+description: 用 CMake、Ninja、clang-format、clang-tidy、clangd 配置、构建和检查 C++11–C++23 工程时使用；新工程默认 C++23；按定构建、定工具配置、通过检查三步推进。一次改动同时碰到源码和构建文件时，先打开 developing-cpp。不用于只改源码语义、文档、Python 或与 C++ 无关的文件。
 metadata:
-  short-description: C++20 构建三步
+  short-description: C++11–C++23 构建三步
 ---
 
 # building-cpp
 
 ## 适用场景
 
-管 `CMakeLists.txt`、`cmake/`、`running-build.sh`、`.clang-format`、`.clang-tidy`、`.clangd`、`.vscode/` 和 `environment.json`。函数体、类型、命名、异常和源码注释只开 `developing-cpp`；一次改动同时越过库与程序的边界时，先做完 `developing-cpp` 的第 2 步，再开本技能。`.qmd`、仓库 README、Python 和非 C++ 文档不打开本技能。
+管 `CMakeLists.txt`、`cmake/`、`running-build.sh`、`.clang-format`、`.clang-tidy`、`.clangd`、`.vscode/` 和 `environment.json`。函数体、类型、命名、异常和源码注释只开 `developing-cpp`。一次改动同时碰到源码和构建文件时，先打开 `developing-cpp`：只改函数体、命名、异常或注释且入口命令可运行时，定实现后直接到本技能的通过检查；新增或移动源文件、改库与程序的边界、补测试 target 时，到本技能先做定构建，把文件写进 CMake，再决定是否定工具配置，最后通过检查。`.qmd`、仓库 README、Python 和非 C++ 文档不打开本技能。
 
 编译失败先分因：诊断指向函数体，回 `developing-cpp` 的定实现；诊断指向声明或类型，回定声明；诊断是找不到头、链接失败、没有编译数据库或工具不在 PATH，留在本技能的定构建或定工具配置。
 
-存在项目技能 `cpp-workflow-project` 时先读它的 `SKILL.md`、`environment.json` 和 `stages/stage-table.md`。三个轴为空或组合非法时停在定构建，不猜 WSL、Clang 或构建目录；环境组合空着时源码四步仍可做，只是不能构建。
+存在项目技能 `cpp-workflow-project` 时先读它的 `SKILL.md`、`environment.json` 和 `stages/stage-table.md`。三个环境轴为空、`standard` 非法或组合非法时停在定构建，不猜 WSL、Clang 或构建目录；`windows` + `native` 直接拒绝，提示「本版本不能在 Windows 原生壳里构建」，不要给出补 PowerShell 的路线。环境组合空着时源码四步仍可做，只是不能构建。
 
 ## 两种走法
 
@@ -36,9 +36,9 @@ metadata:
 
 ## 完成判据
 
-- 项目 `environment.json` 的三个轴齐全且是合法组合；没有靠猜。
+- 项目 `environment.json` 的三个环境轴齐全且是合法组合，`standard` 在 `c++11`–`c++23` 内；新工程默认 `c++23`，没有靠猜。
 - 配置命令固定 Ninja 和单一编译器，`build/<compiler>/compile_commands.json` 存在，根 `build/compile_commands.json` 指向当前编译器。
-- 标准写在 target 上，`CXX_EXTENSIONS OFF`，没有全局 `include_directories()` 或 GLOB。
+- 标准写在 target 上（`CXX_STANDARD` + `CXX_STANDARD_REQUIRED ON` + `cxx_std_*`），`CXX_EXTENSIONS OFF`；`compile_commands.json` 的实际 `-std` 与 `environment.json` 一致，没有全局 `include_directories()` 或 GLOB。
 - `clang-format --dry-run --Werror` 与 `clang-tidy` 在项目源码上零告警；只扫描项目源码和项目头。
 - CTest 全绿，程序从该编译器的构建目录启动；失败时报告的是具体角色和原因。
 - 没有改源码语义，没有覆盖已有工程文件，也没有安装或下载任何工具。

package/skills/building-cpp/assets/config/.clang-format

@@ -1,40 +1,5 @@
-# 100 列：模板与格式化串在 80 列下换行过碎；全工程统一。
+# Google 预设给 80 列、2 空格、不用 tab、包含顺序。
+# clang-format 21/22 不接受 Standard: c++23；Latest 会按当前工具支持的最高标准解析。
 Language: Cpp
 BasedOnStyle: Google
-Standard: c++20
-ColumnLimit: 100
-ReflowComments: true
-AlignAfterOpenBracket: Align
-AlignOperands: Align
-BreakBeforeTernaryOperators: true
-DerivePointerAlignment: false
-PointerAlignment: Left
-AccessModifierOffset: -1
-EmptyLineBeforeAccessModifier: Always
-EmptyLineAfterAccessModifier: Never
-IndentWidth: 2
-TabWidth: 2
-UseTab: Never
-MaxEmptyLinesToKeep: 1
-KeepEmptyLinesAtTheStartOfBlocks: false
-AllowShortFunctionsOnASingleLine: Empty
-AllowShortIfStatementsOnASingleLine: Never
-AllowShortLoopsOnASingleLine: false
-AllowShortCaseLabelsOnASingleLine: false
-BreakAfterAttributes: Never
-AlwaysBreakTemplateDeclarations: Yes
-BreakConstructorInitializers: BeforeColon
-ConstructorInitializerIndentWidth: 4
-SpacesBeforeTrailingComments: 2
-IncludeBlocks: Regroup
-IncludeCategories:
-  # C 系统头先于 C++ 标准库；gtest 归第三方，不排到标准库前面。
-  - Regex: '^<[^/>]*\.h>'
-    Priority: 1
-  - Regex: '^<gtest/'
-    Priority: 3
-  - Regex: '^<.*>'
-    Priority: 2
-  # 其余引号头（本项目组件头）排最后。
-  - Regex: '.*'
-    Priority: 4
+Standard: Latest

package/skills/building-cpp/assets/config/.clang-tidy

@@ -1,35 +1,11 @@
-#===--------------------------------------------------------------------------------------------===#
-# 与 .clang-format 同一套命名；关闭项及理由集中写在 Checks 上方。
-#===--------------------------------------------------------------------------------------------===#
-
+# Google C++ Style Guide 是唯一基线。这里只跑 google-* 检查族，再加一条
+# 命名规则；不再整包启用 cppcoreguidelines-*，也不靠本地关闭项维持风格。
 InheritParentConfig: false
 
-# 关闭项：
-# - bugprone-easily-swappable-parameters：相邻同型参数的顺序错误靠接口设计和 review，不靠命名噪声。
-# - modernize-use-trailing-return-type：Google 风格不要求尾置返回类型。
-# - portability-avoid-pragma-once：项目统一使用 #pragma once。
-# - readability-identifier-length：短循环变量和测试数据（i、x）是领域习惯。
-# - readability-magic-numbers 与 cppcoreguidelines-avoid-magic-numbers：阈值、尺寸和测试数据常直接写字面量。
 Checks: >
   -*,
-  bugprone-*,
-  cppcoreguidelines-*,
-  misc-*,
-  modernize-*,
-  performance-*,
-  portability-*,
-  readability-*,
-  clang-analyzer-core.*,
-  google-build-using-namespace,
-  google-explicit-constructor,
-  google-global-names-in-headers,
-  google-readability-casting,
-  -bugprone-easily-swappable-parameters,
-  -cppcoreguidelines-avoid-magic-numbers,
-  -modernize-use-trailing-return-type,
-  -portability-avoid-pragma-once,
-  -readability-identifier-length,
-  -readability-magic-numbers
+  google-*,
+  readability-identifier-naming
 
 WarningsAsErrors: '*'
 # 头文件过滤由调用方按项目目录传入；这里不写 .*，避免把第三方头纳入。
@@ -37,7 +13,9 @@ FormatStyle: file
 UseColor: true
 
 CheckOptions:
-  # 类型与函数 PascalCase；变量 snake_case；私有成员尾随 _；常量 k 前缀。
+  # 命名按 Google：类型/函数 PascalCase，变量 snake_case，私有成员尾随 _，
+  # 常量 k 前缀。Google 允许访问器写成 count()/set_count()，因此不设
+  # FunctionCase，避免把 snake_case 访问器误报。
   - key: readability-identifier-naming.NamespaceCase
     value: lower_case
   - key: readability-identifier-naming.ClassCase
@@ -50,8 +28,6 @@ CheckOptions:
     value: CamelCase
   - key: readability-identifier-naming.EnumConstantPrefix
     value: 'k'
-  - key: readability-identifier-naming.FunctionCase
-    value: CamelCase
   - key: readability-identifier-naming.TypeAliasCase
     value: CamelCase
   - key: readability-identifier-naming.TypedefCase
@@ -62,6 +38,7 @@ CheckOptions:
     value: lower_case
   - key: readability-identifier-naming.ParameterCase
     value: lower_case
+  # 结构体成员不加尾随下划线；只有类的私有成员用 _ 后缀。
   - key: readability-identifier-naming.FieldCase
     value: lower_case
   - key: readability-identifier-naming.PrivateMemberCase
@@ -82,11 +59,3 @@ CheckOptions:
     value: 'k'
   - key: readability-identifier-naming.MacroDefinitionCase
     value: UPPER_CASE
-  # 函数长度：Google 建议短函数，超过 40 行提示。
-  - key: readability-function-size.LineThreshold
-    value: 40
-  - key: readability-function-size.StatementThreshold
-    value: 50
-  # 空容器/默认构造成员不加 {}；与 NSDMI 规则配套。
-  - key: readability-redundant-member-init.IgnoreBaseInCopyConstructors
-    value: true

package/skills/building-cpp/assets/config/.clangd

@@ -1,10 +1,7 @@
-# 指向当前编译器目录；GCC 模式改成 build/gcc，不要两套并存。
+# 标准来自 build/clang/compile_commands.json，不要在这里写死 -std：
+# 否则 C++23 工程会被降成 .clangd 里的旧标准。
 CompileFlags:
   CompilationDatabase: build/clang
-  Add:
-    - -std=c++20
-    - -Wall
-    - -Wextra
 Diagnostics:
   # 静态检查规则只在 .clang-tidy 里维护；这里不复制检查列表。
   Suppress:

package/skills/building-cpp/assets/config/.vscode/extensions.json

@@ -1,6 +1,7 @@
 {
   "recommendations": [
     "llvm-vs-code-extensions.vscode-clangd",
-    "ms-vscode.cmake-tools"
+    "ms-vscode.cmake-tools",
+    "ms-vscode.cpptools"
   ]
 }

package/skills/building-cpp/assets/config/.vscode/settings.json

@@ -6,10 +6,25 @@
     "--header-insertion=never",
     "--background-index"
   ],
+  // VSCode 的配置、构建、运行和调试入口都留在 CMake Tools。
+  // 不另建 launch.json / tasks.json，避免出现第二套构建或启动路径。
   "cmake.buildDirectory": "${workspaceFolder}/build/clang",
   "cmake.generator": "Ninja",
   "cmake.configureOnOpen": false,
-  // 格式化统一交给 clangd，避免 cpptools 与 clang-format 两套结果。
+  "cmake.buildBeforeRun": true,
+  "cmake.exportCompileCommandsFile": true,
+  // CMake Tools 的快速调试默认使用 C/C++ 扩展的 cppdbg 适配器；
+  // 这里只把它的调试后端改成 LLDB。GCC 模式改成 gdb + /usr/bin/gdb。
+  "cmake.debugConfig": {
+    "type": "cppdbg",
+    "request": "launch",
+    "MIMode": "lldb",
+    "miDebuggerPath": "/usr/bin/lldb",
+    "stopAtEntry": false,
+    "externalConsole": false
+  },
+  // cpptools 只作为 CMake 的调试后端，不再提供 IntelliSense；
+  // 补全、跳转、诊断和格式化都由读取 compile_commands.json 的 clangd 负责。
   "C_Cpp.intelliSenseEngine": "disabled",
   "editor.formatOnSave": true,
   "[cpp]": {