Version 2026.9.15.2; CHANGELOG; the plan's ledger and refinements

Author: speak-agent

.agents/docs/2026-09-15-641-642-implementation-plan.md

@@ -28,16 +28,16 @@ the parallel work trees of §8.
 
 | id | task (triage §) | owner | depends on | status |
 |---|---|---|---|---|
-| M1 | a required compiler family's version is taken from pins that name the same payload; the refusal no longer states a false reason (§3.1) | lead | - | todo |
-| M2 | `mcpp pack --features` reaches every build pass `pack` performs (§3.6) | lead | - | todo |
-| M3 | a dependency's C++ shared library in a graph whose C++ runtime is a package is refused before compiling, unless `cxx_runtime` states `self-contained` for shared libraries; under that statement the library links the provider's objects (§3.3) | lead | - | todo |
-| M4 | `linkage = "static" \| "shared"` in `[targets.<n>]` and `[target.<sel>.targets.<n>]` states the package's default form; precedence and the information line (§3.4) | W1 | - | todo |
-| M5 | dependency link forms are computed once before the root's build program and applied where they are today; `MCPP_DEP_<NAME>_LINKAGE` and `mcpp::dep_linkage` for the root's program (§3.5) | W1 | M4 | todo |
-| M6 | a C++-layer provider that states `[package] standard` compiles its implementation units at that level; module units stay at the graph's (§3.2) | W2 | - | todo |
-| M7 | the object address of a source outside its declaring package is relative to its owning package, or a hashed directory when no package owns it (§3.7 item 3) | W3 | - | todo |
-| M8 | the host-tool sub-build runs in a short key-named scratch directory (§3.7 item 2) | W3 | - | todo |
-| M9 | files the engine opens from ninja-invoked subcommands go through one extended-length path helper on Windows (§3.7 item 1) | W3 | - | todo |
-| M10 | CI: the llvm-dependent e2e scripts of M3 and M6, and the existing 663, run on a job that has llvm, with their PASS lines asserted (§1.8) | lead | M3, M6 | todo |
+| M1 | a required compiler family's version is taken from pins that name the same payload; the refusal no longer states a false reason (§3.1) | lead | - | branch: unit `RequiredFamilyPins.*`; M1 probe reads `llvm@30.0.16248370` on 2026.9.15.1 |
+| M2 | `mcpp pack --features` reaches every build pass `pack` performs (§3.6) | lead | - | branch: e2e 689 (fails on 2026.9.15.1: `pack --features installer failed`) |
+| M3 | a dependency's C++ shared library in a graph whose C++ runtime is a package is refused before compiling, unless `cxx_runtime` states `self-contained` for shared libraries; under that statement the library links the provider's objects (§3.3) | lead | - | branch: e2e 690, four legs (fails on 2026.9.15.1: the refusal is absent) |
+| M4 | `linkage = "static" \| "shared"` in `[targets.<n>]` and `[target.<sel>.targets.<n>]` states the package's default form; precedence and the information line (§3.4) | W1 | - | branch: unit `LinkageForm.*`, manifest cases; e2e 692 (fails on 2026.9.15.1: no libfw.so for a silent consumer) |
+| M5 | dependency link forms are computed once before the root's build program and applied where they are today; `MCPP_DEP_<NAME>_LINKAGE` and `mcpp::dep_linkage` for the root's program (§3.5) | W1 | M4 | branch: e2e 693 (fails on 2026.9.15.1: `'dep_linkage' is not a member of 'mcpp'`) |
+| M6 | a C++-layer provider that states `[package] standard` compiles its implementation units at that level; module units stay at the graph's (§3.2) | W2 | - | branch: unit `CxxLayerStandard.*` (9), `CacheKey` case; e2e 696 (fails on 2026.9.15.1: `new.cpp` at `-std=c++20`) |
+| M7 | the object address of a source outside its declaring package is relative to its owning package, or a hashed directory when no package owns it (§3.7 item 3) | W3 | - | branch: unit `ObjectAddress.*`; e2e 698 leg A (fails on 2026.9.15.1: `obj/installer/__up/__up/dep/...`) |
+| M8 | the host-tool sub-build runs in a short key-named scratch directory (§3.7 item 2) | W3 | - | branch: unit `ToolStoreScratch.*`; e2e 698 leg B |
+| M9 | files the engine opens from ninja-invoked subcommands go through one extended-length path helper on Windows (§3.7 item 1) | W3 | - | branch: unit `PlatformFs.*`; e2e 698 leg C (Windows readings from CI) |
+| M10 | CI: the llvm-dependent e2e scripts of M3 and M6, and the existing 663, run on a job that has llvm, with their PASS lines asserted (§1.8) | lead | M3, M6 | branch: `ci-linux-e2e.yml` hermetic job step |
 | M11 | user documentation with its Chinese mirror; SPEC changes; CHANGELOG; version 2026.9.15.2 | lead, W1-W3 | M1-M9 | todo |
 | M12 | the triage and plan records closed with their readings | lead | all | todo |
 
@@ -158,6 +158,36 @@ which has never run in CI, directly on the `hermetic` job (which already
 installs `llvm@22.1.8`) and asserts each script's final PASS line, and the
 line of the run step inside it.
 
+### 1.9 Refinements found while implementing
+
+- **M5's computation follows the layer-conditional pass (L1b), not only the
+  dependency programs.** L1b changes dependency manifests, so a computation
+  placed before it would read facts that are not final. The p1689 scanner had a
+  source enumeration of its own that ignored `!` exclusions; it now reads the
+  function the resolution reads. Form B descriptors read `linkage` as
+  `mcpp.toml` does, and SPEC-001 records the precedence (v1.4, criterion 9).
+- **M6's level enters the dependency cache key and the fingerprint** when a
+  provider states one, because the graph's level alone no longer says which
+  level the provider's sources were compiled at. The opt-in p1689 scan runs
+  before planning and still preprocesses these units at the graph's level,
+  which affects import detection only.
+- **M7 and M8 shorten the issue's case to about 170 characters,** so crossing
+  260 now needs nesting deep inside the dependency; e2e 698 leg C does that and
+  is the Windows reading of whether ninja and the compilers cope. M9 had to
+  guard two things beyond opens: a path string ninja reads back (the copied
+  depfile's target keeps ninja's spelling) and an ANSI Win32 call
+  (`CreateFileW` for the detached compile's log).
+- **M3's static remedy depends on who made the library shared.** A package that
+  constrains its form (`declaredShared`) cannot be linked static from its edge,
+  so that remedy is offered only when a request or the package's default
+  decided, and the refusal names the package's statement otherwise. `mcpp run
+  --format` built its pack without the run's features; it now passes them.
+- **F3, recorded and not addressed.** The std module object is linked into every
+  C++ image, so a program over a C++ shared library that imports `std` reports
+  its module initialiser as provided twice (`symbol_provision`). This predates
+  the work: under gcc on 2026.9.15.1 the same shape reports 882 symbols; under
+  the private copy of M3 it reports two, `_ZGIW3std` and `_ZGIW3stdW6compat`.
+
 ## 2. Engine tasks
 
 ### 2.1 M1

CHANGELOG.md

@@ -5,6 +5,47 @@
 
 ## [Unreleased]
 
+### 链接形态、标准档位与路径长度:#641 与 #642(2026.9.15.2)
+
+一个 UI 框架迁到 macOS 12 下限与 Android 独立共享库时报告的七项,全部在引擎内处理。
+设计与实测记录:`.agents/docs/2026-09-15-641-642-*.md`。
+
+- **必需编译器族的版本取自同一载荷的 pin(#641 项 1)。** 全新 home 上
+  `requires = ["mcpp:compiler=llvm"]` 此前按族比较行 pin,取到 NDK 的
+  `llvm@30.0.16248370`;`compiler=emsdk` / `compiler=android-ndk` 则一个都匹配不到,
+  并谎称没有行固定版本。现按 `to_xim_package` 的包名比较(`pinned_versions_for`)。
+  (单测 `RequiredFamilyPins.*`)
+- **C++ 层提供者按自己声明的标准编译实现单元(#641 项 2)。** 提供
+  `hosted-standard-library` / `mcpp:c++-abi=` 的包若写了 `[package] standard`,其既不
+  提供也不导入模块的 C++ 单元按该档位编译,模块单元(含 std 模块)仍按图的档位;
+  于是 c++20 的程序可以使用 `llvm.libcxx`。该档位进入依赖缓存键与指纹;不写的提供者
+  逐字节不变。(单测 `CxxLayerStandard.*`,e2e 696)
+- **工具构建的路径有界(#641 项 3)。** 位于声明包之外的源文件,对象地址改为
+  `obj/<声明包>/__pkg/<所属包>/<包内路径>`,无所属包时为 `obj/<声明包>/__ext/<目录哈希>/`;
+  host 工具子构建的暂存目录改为 `<cache>/tool/.build/<16 位哈希>`;ninja 调用的引擎子命令
+  在 Windows 上以扩展长度路径打开文件。(单测 `ObjectAddress.*`、`PlatformFs.*`、
+  `ToolStoreScratch.*`,e2e 698)
+- **`mcpp pack --features`(#641 项 4)。** 作用于打包的每一次构建(每条 `--target` 腿、
+  分派格式的两次构建);`mcpp run --format` 把自己的 feature 交给它执行的打包。(e2e 689)
+- **图中的 C++ 运行时之上的依赖共享库(#641 项 5)。** 运行时包的对象只链进程序,依赖
+  的 C++ 共享库此前没有任何 C++ 运行时(Linux 上 lld 拒绝链接程序,macOS 上 dylib
+  链接失败)。现在编译前拒绝,reason 为 `shared-library-cxx-runtime`,并给出出路;
+  写明 `cxx_runtime = { shared = "self-contained" }` 时,共享库链接运行时包对象的私有
+  副本。实测:每个镜像一份副本时,共享库抛出的 `std::runtime_error` 在程序中不能按该类
+  捕获,拒绝消息写明这一后果。(e2e 690,在 hermetic llvm job 上运行)
+- **包声明默认链接形态(#642 E1)。** `[targets.<n>]` 与
+  `[target.<sel>.targets.<n>]` 中的 `linkage = "static" | "shared"` 是包的默认值,
+  `kind = "shared"` 仍是约束;根的边 `linkage`、显式的 `[build] dependency_linkage`
+  依次优先于它,覆盖默认值时打印一行信息而非降级,`--strict` 接受。解析记录的 reason
+  为 `package-default` 或 `requested`。(单测 `LinkageForm.*`,e2e 692)
+- **根构建程序读取依赖的链接形态(#642 E2)。** 依赖的链接形态在根构建程序之前计算一次,
+  应用位置不变;根构建程序得到 `MCPP_DEP_<NAME>_LINKAGE` 与 `mcpp::dep_linkage(name)`。
+  依赖的构建程序不提供该值:只有根决定链接形态,且它运行时排在其后的包的输入尚未齐备。
+  `hasSources` 取自扫描器导出的 `package_source_files`,p1689 扫描器由此也遵循 `!` 排除。
+  (e2e 693)
+- CI:`ci-linux-e2e` 的 hermetic job 直接运行 663、690、696 并断言其结束行;这三份脚本
+  需要 llvm,分片上一向被跳过。
+
 ### `mcpp emit build-database`:不写工程目录的构建数据库(#636,2026.9.15.1)
 
 新命令按 `mcpp build --configure-only` 的方式、用相同的选择器规划,把计划打印为

mcpp.toml

@@ -1,6 +1,6 @@
 [package]
 name        = "mcpp"
-version = "2026.9.15.1"
+version = "2026.9.15.2"
 description = "Modern C++ build & package management tool"
 license     = "Apache-2.0"
 authors     = ["mcpp-community"]

modules/versioning/src/version.cppm

@@ -31,6 +31,6 @@ import std;
 
 export namespace mcpp {
 
-inline constexpr std::string_view MCPP_VERSION = "2026.9.15.1";
+inline constexpr std::string_view MCPP_VERSION = "2026.9.15.2";
 
 } // namespace mcpp