2026.9.29.5: a workspace's build programs are reused across selections and run dependencies first, the build database and --configure-only plan by configuration, and the output names what it reports

The validation project's post-release run of 2026.9.29.4 showed five defects
in the commands around the workspace build (design document section 17.1).

- D1: a member program's graph document listed every requester in the plan,
  the virtual root included, so the program's re-run key followed the
  selection and -p, pack and emit reran the programs a --workspace build ran.
  The document lists the requests made inside the program's closure
  (graph_package_entry takes the closure's packages).
- The members' programs run dependencies first (depth-first over the plan's
  requests; a cycle skips its closing edge); they ran in discovery order.
- D2: `mcpp emit build-database` and `mcpp build --configure-only` plan a
  workspace by configuration, each member's tests included
  (BuildOverrides::member_targets), so a package the members share is described
  once per configuration; members that are programs and their tests are
  described as such. A configuration whose plan fails is planned member by
  member, so a member's failure affects that member only. Set names carry a
  configuration prefix only in a document of several configurations; a set and
  a compile command (file and output) are described once (SPEC-005 v1.6).
- A command that plans several configurations publishes the root
  compile_commands.json once, as the union of their databases; each
  configuration replaced it, a race under concurrent groups.
- D3: the build program status lines name the package.
- D4: a selected member is announced by its directory in a --workspace build.
- D5: `mcpp pack` reports more than eight outputs by the entry each lies in
  below their common directory, with a count; --verbose and
  --message-format json name every output.
- e2e 839, 840, 841; docs/07, docs/10, docs/30 in both languages; SPEC-005 v1.6;
  version 2026.9.29.5.

Author: speak-agent

.agents/docs/2026-09-29-workspace-build-graph-design.md

@@ -563,6 +563,10 @@ read from the member, or made a value of the plan:
 | the runtime files of a program shipped through `artifacts` (2026.9.29.3) | its link waited for the plan's deploy set, which a workspace plan does not place; its own runtime files were not in the member's directory | the link waits for no plan-level file; a member's runtime set includes the closures its `artifacts` edges reach | e2e 833 G9 |
 | the link line of a program shipped through `artifacts` (2026.9.29.4) | the plan's line, which pools the dependencies' flags and not a member's, so a library its package's build program states was missing | a link group of its own closure that places nothing (`LinkGroup::linkOnly`) | e2e 838 |
 | `${mcpp.bin_dir}` in a member's action (2026.9.29.4) | the plan's `bin/` | the declaring member's product directory | e2e 838 A4 |
+| a member program's graph document (2026.9.29.5) | listed every requester in the plan, the virtual root included, so the program's re-run key followed the selection | the requests made inside the program's closure | e2e 839 B3, B4 |
+| the order of the members' programs (2026.9.29.5) | discovery order | dependencies first (a cycle skips its closing edge) | e2e 839 B2 |
+| `emit build-database`, `--configure-only` (2026.9.29.5) | one plan per member | one plan per configuration, each member's tests included; a failed configuration planned member by member | e2e 840 |
+| the root compile database of several configurations (2026.9.29.5) | the last written configuration's, a race under concurrent groups | the union, published once by the command | e2e 840 B |
 
 Each criterion fails on 2026.9.29.1 and passes on 2026.9.29.2. The resource
 case also showed a defect of every build: a quoted `#include` in a script was

CHANGELOG.md

@@ -4,6 +4,52 @@
 > Each `## [<version>]` section is that release's notes. Entries are written in English
 > from 2026.9.28.3 on; earlier entries remain as written.
 
+## [2026.9.29.5] - 2026-09-29
+
+This release completes the workspace build graph in the commands around the
+build, from the validation project's post-release run of 2026.9.29.4: build
+programs are reused across selections and run dependencies first, the build
+database and `--configure-only` plan by configuration, and the output names
+what it reports.
+
+### Fixed
+
+- **A member's build program is reused whichever members a command selects.**
+  Its graph document listed every requester in the plan, the virtual root
+  included, so the program's re-run key followed the selection: `-p`, `mcpp
+  pack` and `mcpp emit build-database` reran the programs a `--workspace`
+  build had run (7 to 15 s each in the validation project). A program's
+  document now lists the requests made inside its own closure (e2e 839).
+- **A member's build program runs after those of the members it depends on.**
+  They ran in discovery order, so a member's program could run before its
+  dependency's had applied its directives (e2e 839).
+- **`mcpp emit build-database` and `mcpp build --configure-only` plan a
+  workspace by configuration, as the build does.** They planned each member
+  separately, so a package two members use was described once per member,
+  each time with other arguments (the validation project's core library three
+  times). A member that is a program is described as one, and its tests as
+  tests. A configuration whose plan fails is planned member by member, so a
+  member's failure still affects that member only (e2e 840; SPEC-005 v1.6).
+- **A command that plans several configurations writes the root
+  `compile_commands.json` once**, as the union of their databases. Each
+  configuration replaced it, and under `mcpp build --workspace`, whose
+  configurations build at the same time, the file was the last one's (e2e 840).
+
+### Behaviour changes
+
+- **The build program status lines name the package**:
+  `build.mcpp compiling <package>`, `running <package>`,
+  `up to date <package> (cached)` (e2e 839).
+- **A selected member is announced by its directory** in a `--workspace`
+  build, also where another member depends on it (e2e 839).
+- **`mcpp pack` summarises many outputs.** A format that reports more than
+  eight outputs is reported by the entry each lies in below their common
+  directory, with a count; `--verbose` names every output, and
+  `--message-format json` lists every one as before (e2e 841).
+- **Build database set names (SPEC-005 v1.6).** A set is named by its package;
+  a document of several configurations prefixes each name with the
+  configuration's build directory name, instead of `<member>/`.
+
 ## [2026.9.29.4] - 2026-09-29
 
 This release links a program that a workspace member ships through

docs/07-workspace.md

@@ -441,6 +441,14 @@ member that several members use is compiled once.
 - **Resources.** A member's `[resources]` and `windows_code_page` are
   compiled against the member's directory and include directories and embedded
   into that member's programs and shared libraries only (2026.9.29.2+).
+- **Build programs.** The members' build programs run dependencies first, and
+  a program's result is reused by every command whose inputs to it are
+  unchanged, whichever members the command selects (2026.9.29.5+).
+- **Compile database.** `mcpp build --configure-only` and `mcpp emit
+  build-database` plan as the build does, one plan per configuration with each
+  member's tests, so a package the members share is described once per
+  configuration. A command that planned several configurations writes the root
+  `compile_commands.json` once, as the union of their databases (2026.9.29.5+).
 - **No-op builds.** A command repeated with nothing changed is answered by one
   check per configuration, without planning.
 - **Module names.** Members built in one graph share one module namespace:

docs/10-pack-and-release.md

@@ -265,6 +265,12 @@ the last is the distributable and only it is printed as `Packed`. A format
 whose chain ends in two files is refused by `mcpp run --format`, naming both,
 because a runner takes one operand.
 
+A format may report many outputs, one per file of a distribution tree. Up to
+eight are printed one per line; more are printed by the entry each lies in
+below their common directory, with a count (`Packed Release/app (1309
+files)`), and `--verbose` prints every one (2026.9.29.5+).
+`--message-format json` lists every output in either case.
+
 An unknown `<name>` is refused naming the format set the resolved graph
 provides, the same set `mcpp pack --format bogus` reports. `--format` together
 with `--no-runner` is refused — an `.apk` or an installed `.app` cannot be

docs/30-build-mcpp.md

@@ -1045,6 +1045,11 @@ one. `mcpp::graph_file()` names a JSON document that states the resolved graph:
   `""`.** The root decides the graph, and when its program runs every input of
   that decision is final, which is the reason `dep_linkage` is offered to it
   alone.
+- **In a workspace plan each selected member's program receives the document
+  of its own closure**, in which it is `root`, and `requested_by` lists the
+  requests made inside that closure (2026.9.29.5+). The document, and so the
+  program's re-run key, is therefore the same whichever members a command
+  selects. The members' programs run dependencies first.
 - **`[package.metadata.<tool>]` is the package's statement about itself.** The
   engine does not interpret the table. A path in it is resolved by the reader
   against the entry's `manifest_dir`, because only the reader knows which values
@@ -1513,8 +1518,9 @@ variable, emit `mcpp:rerun-if-changed=config.h` / `mcpp:rerun-if-env-changed=USE
 This replaces the old "process exited 0, so assume it's fine" guesswork with an
 explicit input/output contract — incremental builds stay correct.
 
-When nothing changed the output is `build.mcpp up to date (cached)`; otherwise
-`build.mcpp compiling` / `running`.
+When nothing changed the output is `build.mcpp up to date <package> (cached)`;
+otherwise `build.mcpp compiling <package>` / `running <package>` (the package
+is named from 2026.9.29.5 on).
 
 ## Host tools from a dependency (mcpp 2026.8.5.1+)
 

docs/40-baremetal.md

@@ -206,8 +206,8 @@ Measured output:
    Resolving toolchain
     Resolved llvm@22.1.8 → riscv64-none-elf → @mcpp/registry/data/xpkgs/xim-x-llvm/22.1.8/bin/clang++
     Resolved host toolchain for build.mcpp: clang 22.1.8 (x86_64-unknown-linux-gnu)
-  build.mcpp compiling
-  build.mcpp running
+  build.mcpp compiling blinky
+  build.mcpp running blinky
     Inferred sources [src/**/*.{cppm,cpp,cc,c,S,s,asm}]
     Inferred target blinky (bin from src/main.cpp)
    Compiling blinky v0.1.0 (.)

docs/specs/README.md

@@ -34,7 +34,7 @@
 | [SPEC-002](target-side.md) | 目标侧模型与能力声明(`mcpp:` 保留命名空间、五层、三条规则) | 评审中 v1.0 | 2026-08-24 | mcpp >= 2026.8.24.2 |
 | [SPEC-003](exit-codes.md) | 退出码契约(分类、语义、稳定性承诺) | 评审中 v1.0 | 2026-09-01 | mcpp >= 2026.9.1.1 |
 | [SPEC-004](manifest-semantics.md) | `mcpp.toml` 的平面划分、条件化形状、解析轴与命名规约 | 草案 v1.10 | 2026-09-28 | 条件化形状 mcpp >= 2026.8.29.1;目标轴 mcpp >= 2026.9.6.4;`linkage` 默认值 mcpp >= 2026.9.15.2;链接 flag 的词读法 mcpp >= 2026.9.26.2;条件化的 `dialect_cxxflags` 与 `-p` 的包身份 mcpp >= 2026.9.28.1;条件表按具体程度生效 mcpp >= 2026.9.28.2 |
-| [SPEC-005](build-database.md) | 构建数据库:`mcpp emit build-database` 的内容、取值规则与不写工程目录的保证 | 评审中 v1.5 | 2026-09-28 | mcpp >= 2026.9.15.1;v1.3 条款 mcpp >= 2026.9.26.2;v1.4 条款 mcpp >= 2026.9.27.1;v1.5 条款 mcpp >= 2026.9.28.1 |
+| [SPEC-005](build-database.md) | 构建数据库:`mcpp emit build-database` 的内容、取值规则与不写工程目录的保证 | 评审中 v1.6 | 2026-09-29 | mcpp >= 2026.9.15.1;v1.3 条款 mcpp >= 2026.9.26.2;v1.4 条款 mcpp >= 2026.9.27.1;v1.5 条款 mcpp >= 2026.9.28.1;v1.6 条款 mcpp >= 2026.9.29.5 |
 | [SPEC-006](toolchain-management.md) | 工具链管理:身份、来源、选择与载荷契约 | 草案 v0.4 | 2026-09-28 | 逐条标注;已实现条款 mcpp >= 2026.9.24.1;§3.7 mcpp >= 2026.9.28.1;§3.7.1 mcpp >= 2026.9.28.2 |
 | [SPEC-007](build-plugins.md) | 构建插件:配置、施工与校验的分工,运行时与规划期的义务 | 草案 v0.6 | 2026-09-28 | 逐条标注;mcpp >= 2026.9.26.2;v0.3 条款 mcpp >= 2026.9.27.1;v0.4 条款 mcpp >= 2026.9.28.1;v0.5 条款 mcpp >= 2026.9.28.2;v0.6(§9)mcpp >= 2026.9.28.3 |
 | [SPEC-008](library-interface.md) | 库的接口:公开模块、发布闭包与两种形态的一致 | 草案 v0.1 | 2026-09-28 | 第一阶段(只警告)mcpp >= 2026.9.28.3 |

docs/specs/build-database.md

@@ -4,10 +4,10 @@
 |---|---|
 | 规范编号 | SPEC-005 |
 | 标题 | mcpp 输出的构建数据库:内容、取值规则与不写工程目录的保证 |
-| 状态 | 评审中 v1.5 |
-| 版本 | 1.5 |
-| 最后修改 | 2026-09-28 |
-| 对应实现 | mcpp >= 2026.9.15.1;v1.3 修改的 R2.5、R3.7、R3.8、R4.1、R5.2 为 mcpp >= 2026.9.26.2;v1.4 修改的 R2.5 为 mcpp >= 2026.9.27.1;v1.5 修改的 R3.7、R3.12、R5.1、R5.2 为 mcpp >= 2026.9.28.1 |
+| 状态 | 评审中 v1.6 |
+| 版本 | 1.6 |
+| 最后修改 | 2026-09-29 |
+| 对应实现 | mcpp >= 2026.9.15.1;v1.3 修改的 R2.5、R3.7、R3.8、R4.1、R5.2 为 mcpp >= 2026.9.26.2;v1.4 修改的 R2.5 为 mcpp >= 2026.9.27.1;v1.5 修改的 R3.7、R3.12、R5.1、R5.2 为 mcpp >= 2026.9.28.1;v1.6 修改的 R2.1、R3.3、R3.4、R3.5、R4.1、R5.2 为 mcpp >= 2026.9.29.5 |
 | 相关设计文档 | `.agents/docs/2026-09-14-636-build-database-and-the-latest-xlings.md`<br>`.agents/docs/2026-09-26-compile-database-and-issue-699-design.md` |
 | 相关 issue | #636, #648, #655, #699, #702, #707 |
 | 依据的外部规范 | S1「C++ Build Database: IDE Profile」profile 0.3.0(§7.2 的 `generated`,Sunrisepeak/mcpp-language-server#28;此前为 0.2.0)与 S2 0.2.0 §3.4,取自 https://github.com/Sunrisepeak/lsp-mcpp-private 提交 `b82859d`(schema 自提交 `28ecd6e` 起未变);S2 0.3.0 §3.4 的部分回答(S2-3.4-12、S2-3.4-13,Sunrisepeak/mcpp-language-server#25);JSON Compilation Database |
@@ -42,7 +42,7 @@ Database 定义,本规范不重复它们的字段定义,只规定 mcpp 作为生
 ## 2. 不写工程目录
 
 - **R2.1** 命令**禁止**写入工程目录,即根包、工作区成员与 path 依赖的源码树。规划
-  写入 `$MCPP_HOME/cache/build-database/<key>`,`<key>` 由工程根与成员决定。该目录
+  写入 `$MCPP_HOME/cache/build-database/<key>`,`<key>` 由工程根与一次规划的成员决定。该目录
   是缓存,可以随时删除。**已实现**
 - **R2.2** 命令不编译:标准库模块被描述而不被编译,也不生成只供链接使用的输入(GCC 的
   `mcpp-clean-link.specs`)。工具链照常被查询(版本、目标三元组、sysroot 等),与
@@ -84,14 +84,18 @@ mcpp 输出的 S1 文档满足 S1 等级 2,不输出 `ide.options`。等级 3 
 
 ### 3.2 集合
 
-- **R3.3** 每个包一个集合,名为包的限定名(`<namespace>.<name>` 或 `<name>`)。根包
-  测试目标的源文件归入集合 `<包>:test`,标准库模块的单元归入集合 `mcpp:std`。工作区
-  文档中,每个集合名带前缀 `<成员>/`。**已实现**
-- **R3.4** `visible-sets` 列出同一成员的其余所有集合。引擎在一次调用的一张模块图上
+- **R3.3** 每个包一个集合,名为包的限定名(`<namespace>.<name>` 或 `<name>`)。根包与
+  工作区被选成员的测试目标的源文件归入集合 `<包>:test`,标准库模块的单元归入集合
+  `mcpp:std`。工作区按配置规划,与 `mcpp build` 相同:每个配置一次规划,成员共用的包
+  在一个配置中只有一个集合。文档描述多个配置时,每个集合名带前缀 `<配置>/`,`<配置>`
+  为该配置构建目录的名字;只有一个配置时不带前缀。两次规划描述同一配置的同一集合时
+  (见 R5.2 的逐成员规划),该集合只出现一次。**已实现**
+- **R3.4** `visible-sets` 列出同一次规划的其余所有集合。引擎在一次调用的一张模块图上
   解析 import,更窄的闭包会描述一条构建并不执行的规则。**已实现**
 - **R3.5** `family-name` 为包名,`mcpp:std` 集合的为 `mcpp:std`;`ide.configuration`
-  为 profile 名;`ide.kind` 在测试集合为 `test`,在根包集合按其目标为 `library`、
-  `executable` 或 `other`,在依赖包集合与 `mcpp:std` 为 `library`。**已实现**
+  为 profile 名;`ide.kind` 在测试集合为 `test`,在根包与工作区被选成员的集合按其
+  目标为 `library`、`executable` 或 `other`,在依赖包集合与 `mcpp:std` 为 `library`。
+  **已实现**
 - **R3.6** 单元的 `arguments` 依次是驱动、集合的 `baseline-arguments`、单元的
   `local-arguments`,以及单元自己结尾的 `-c <source> -o <object>`(若有;两个操作数
   相对 `work-directory` 指向 `source` 与 `object`)。`baseline-arguments` 是集合中每个
@@ -170,7 +174,8 @@ mcpp 输出的 S1 文档满足 S1 等级 2,不输出 `ide.options`。等级 3 
 ## 4. `--spec compile-commands`
 
 - **R4.1** 文档为 `mcpp build --configure-only` 在同一组选择器下写入
-  `compile_commands.json` 的条目,差别只在输出路径位于 §2 的工作目录之下。标准库
+  `compile_commands.json` 的条目,差别只在输出路径位于 §2 的工作目录之下;同一文件与
+  同一输出只有一条条目,文档描述多个配置时,一个文件在每个编译它的配置中各有一条。标准库
   模块的单元也在其中,遵循 S1-12-1 的导出规则:S1 文档里 `mcpp:std` 集合的每个
   单元同样导出为一条 `compile_commands.json` 条目。**已实现**
 
@@ -179,8 +184,9 @@ mcpp 输出的 S1 文档满足 S1 等级 2,不输出 `ide.options`。等级 3 
 - **R5.1** `kind` 为 `mcpp.build-database`,`kindVersion` 为 1。`data` 含 `spec`
   (`{"name": "s1", "version": "0.3.0"}` 或 `{"name": "compile-commands"}`)、
   `database`、`watch` 与 `inputs-fingerprint`。**已实现**
-- **R5.2** 命令独立规划每一个被选中的成员:一个成员规划失败只影响它自己,不影响
-  其余成员的集合(#699 第 1 项)。规划失败的成员不贡献任何集合,只贡献一条 `error`
+- **R5.2** 一个成员规划失败只影响它自己,不影响其余成员的集合(#699 第 1 项)。命令
+  按配置规划被选中的成员;一个配置的规划失败时,该配置的成员逐个规划,因此失败仍归于
+  各自的成员。规划失败的成员不贡献任何集合,只贡献一条 `error`
   诊断,`path` 为该成员的 `mcpp.toml`,相对工作区根目录;诊断码为:不在工程中时
   `MCPP_BUILD_DATABASE_NO_PROJECT`;该成员的规划因离线而需要下载时
   `MCPP_OFFLINE_DOWNLOAD_REQUIRED`,消息指出需要下载的第一项;其他规划失败为
@@ -226,3 +232,4 @@ mcpp 输出的 S1 文档满足 S1 等级 2,不输出 `ide.options`。等级 3 
 | 1.3 | 2026-09-26 | R2.5:`emit` 下构建失败的宿主工具是警告。R3.7:`work-directory` 是输出目录,模块接口单元的 `arguments` 带语言 flag。R3.8:标准库单元的 `provides` 指向 std 缓存中的 BMI,工具链带 `build-id`。R4.1:compile-commands 文档包含标准库单元(S1-12-1)。R5.2:成员各自规划,构建程序失败的包不带其指令地被描述(#699,#702)。 |
 | 1.4 | 2026-09-26 | R2.5:命令不构建宿主工具;工具库中没有的工具被推迟,输出说明 `MCPP_BUILD_DATABASE_HOST_TOOL_DEFERRED`,取代 1.3 的警告 `MCPP_BUILD_DATABASE_HOST_TOOL_UNBUILT`(#707)。 |
 | 1.5 | 2026-09-28 | R3.7:规则声明的设备源不是编译单元,不进入 S1 与 `compile_commands.json`(#724)。新增 R3.12:集合的 `ide.generated` 列出规则生成的文件与目录,给出构建写入的路径与生成它的步骤,S1 0.3.0(#724,Sunrisepeak/mcpp-language-server#28)。R5.1:S1 版本为 0.3.0。R5.2:以构建程序的指令为前提的检查不对其构建程序已失败的包运行,失败路径保留已记录的说明(#724)。 |
+| 1.6 | 2026-09-29 | 工作区按配置规划,与 `mcpp build` 相同(R2.1、R3.3、R3.4、R5.2):成员共用的包在一个配置中只描述一次;集合名的前缀由 `<成员>/` 改为只在文档描述多个配置时出现的 `<配置>/`;一个配置的规划失败时逐成员规划。R3.5:被选成员的集合按其目标给出 `ide.kind`。R4.1:同一文件与输出一条条目。 |

docs/zh/07-workspace.md

@@ -407,6 +407,12 @@ mcpp test --workspace --workspace-timeout 1800   # whole fan-out (default 0 = no
 - **Hooks。** 每个被选成员的 `[hooks]` 按成员顺序在构建前后运行。
 - **资源。** 成员的 `[resources]` 与 `windows_code_page` 按该成员的目录与 include 目录编译，
   只嵌入该成员自己的程序与共享库（2026.9.29.2+）。
+- **构建程序。** 成员的构建程序按依赖在前的顺序运行；只要程序的输入不变，无论命令选中哪些
+  成员，程序的结果都被复用（2026.9.29.5+）。
+- **编译数据库。** `mcpp build --configure-only` 与 `mcpp emit build-database` 按构建的方式
+  规划，每个配置一次规划并包含各成员的测试，因此成员共用的包在每个配置中只描述一次。规划了
+  多个配置的命令只写一次根目录的 `compile_commands.json`，内容为各配置数据库的并集
+  （2026.9.29.5+）。
 - **无事可做的构建。** 在没有任何改动时重复执行的命令，每个配置只做一次检查，不重新规划。
 - **模块名。** 在同一张图中构建的成员共享一个模块命名空间：两个成员各自提供同名模块时，不能在
   同一条 `--workspace` 命令中构建；分别用 `-p` 构建。