@@ -212,7 +212,7 @@ No runtime generation becomes a dependency version or build-cache identity.
 | C++ runtime | 0.19.0 | [Runtime 66](https://github.com/mcpplibs/openkal-llvm-runtime/pull/66) |
 | Platform | 0.24.0 | Publication follows its public lower dependencies |
 | OS composition | 0.3.0 | [OS 17](https://github.com/mcpplibs/os/pull/17) |
-| Core | 2026.11.6.1 | [mcpp 889](https://github.com/mcpp-community/mcpp/pull/889) |
+| Core | 2026.11.7.1 | [mcpp 889](https://github.com/mcpp-community/mcpp/pull/889) |
 
 OS advances to 0.3.0 so an explicit range such as `^0.2.3` cannot silently
 absorb a different OpenKal minor group. Bare package versions name exact wire
@@ -229,16 +229,16 @@ changes the state output from `empty` to `unknown`.
 
 Source-group controls establish implementation behaviour. The lower versions,
 including platform 0.24.0 and OS 0.3.0, are now publicly released and indexed;
-their ordinary consumers have been checked. Core 2026.11.6.1 uses those pins
+their ordinary consumers have been checked. Core 2026.11.7.1 uses those pins
 and still requires full exact-head CI, an independent ecosystem review,
 canonical tag archives, byte-identical CN mirrors, a published index entry and
 ordinary GLOBAL/CN consumers. Plugins PR 52 retains the published
-2026.11.5.1 pin until core 2026.11.6.1 is published, then runs its actual
+2026.11.5.1 pin until core 2026.11.7.1 is published, then runs its actual
 sidecar integration and final CI.
 
 ## 2026-11-06 final-head CI failure controls
 
-The first 2026.11.6.1 CI run exposed four distinct boundaries. Clang/libc++
+The first 2026.11.7.1 CI run exposed four distinct boundaries. Clang/libc++
 uses a wider file-clock tick representation than `std::to_string` accepts;
 the journal now rejects values outside its signed 64-bit schema and preserves
 in-range ticks. A direct exact-toolchain control compiled the failing expression
 
@@ -5,7 +5,7 @@ status: active
 
 # Launch configuration and named test runners
 
-Status, 2026-11-06: implemented for candidate 2026.11.6.1. Focused local
+Status, 2026-11-06: implemented for candidate 2026.11.7.1. Focused local
 controls pass; final public-dependency and cross-platform CI remain pending.
 
 A consumer choosing a debugger runner needs the configuration of the program
 
@@ -4,7 +4,7 @@
 > 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.11.6.1] - 2026-11-06
+## [2026.11.7.1] - 2026-11-07
 
 ### Fixed
 
 
@@ -1049,7 +1049,7 @@ with two behaviours has to be.
 `bmi_schedule` decides when importers are unblocked.
 
 With GCC and `bmi_schedule = "on"`, ordinary compilation and detached code
-generation share the same total `jobs` limit (2026.11.6.1+). Additional
+generation share the same total `jobs` limit (2026.11.7.1+). Additional
 scheduling and join tasks do not increase the number of compiler processes.
 Cancelling the build ends its ordinary and detached compilers. An immediately
 following build waits for their cleanup before starting another compiler;
 
@@ -170,7 +170,7 @@ or a QEMU exit code is what a bare-metal runner is chosen to produce.
 `--no-runner` exists for a host that can execute the binaries natively and
 should not pay for an emulator.
 
-`--runner <name>` (2026.11.6.1+) selects a named runner instead of the default,
+`--runner <name>` (2026.11.7.1+) selects a named runner instead of the default,
 using the same declarations and argument substitution as `mcpp run --runner`.
 It also applies to `--print-launch` and tests read from an archive. An absent
 runner name is refused; `--runner` and `--no-runner` cannot be combined.
 
@@ -411,7 +411,7 @@ Nothing else is declared (2026.10.27.1+): the target table selects
 `openkal-platform` for both rows, and the platform states the toolchain, the
 layers, the tools, the conventions below and the runner ([35](35-platforms.md)).
 
-Both built-in openkal targets select platform 0.24.0 by default (2026.11.6.1+).
+Both built-in openkal targets select platform 0.24.0 by default (2026.11.7.1+).
 An explicit `platform` configuration overrides that selection. This platform
 preserves the emulated TLS convention through the final ThinLTO link.
 
 
@@ -90,7 +90,7 @@ configuration, so it remains usable while the network is broken.
 An install tracks byte progress and source changes separately for each active
 download. Time spent waiting for a download slot does not consume that budget.
 Progress on another file does not renew a stalled file's budget.
-From 2026.11.6.1, a stalled-download diagnostic names the file, elapsed interval
+From 2026.11.7.1, a stalled-download diagnostic names the file, elapsed interval
 and source attempt. Provider preparation and process timeouts are reported
 separately. Mirror selection
 uses `mcpp self config --mirror auto`, `CN` or `GLOBAL`.
 
@@ -1097,7 +1097,7 @@ none to rely on), and the only interpolations are a closed set:
 | `${mcpp.out_dir}` | the build output directory |
 | `${mcpp.bin_dir}` | where produced binaries land: `bin/`, or, for an action a workspace member's build program declares, that member's product directory (2026.9.29.4+) |
 | `${mcpp.compile_db}` | path to `compile_commands.json` (what clang-tidy's `-p` wants) |
-| `${mcpp.contract}` *(2026.10.30.1+)* | path to the configuration's contract, `mcpp-contract.json`, beside its compile database: the compiler of each language with the words every unit is compiled with (target, sysroot, target-side headers, platform and profile flags), and the link driver, its words and the archiver. A foreign build system reads it to compile for the target as the engine does; a package's own include directories are not in it, nor the engine's C++ dialect and module words (`-std=`, `-fmodules`), which are its choice for its own units. Since 2026.11.6.1, link arguments describe the target configuration; the consuming package's link flags and libraries are excluded, since they can name outputs the foreign build has yet to produce |
+| `${mcpp.contract}` *(2026.10.30.1+)* | path to the configuration's contract, `mcpp-contract.json`, beside its compile database: the compiler of each language with the words every unit is compiled with (target, sysroot, target-side headers, platform and profile flags), and the link driver, its words and the archiver. A foreign build system reads it to compile for the target as the engine does; a package's own include directories are not in it, nor the engine's C++ dialect and module words (`-std=`, `-fmodules`), which are its choice for its own units. Since 2026.11.7.1, link arguments describe the target configuration; the consuming package's link flags and libraries are excluded, since they can name outputs the foreign build has yet to produce |
 | `${mcpp.target_file:<name>}` | the built file of target `<name>` |
 | `${mcpp.stage_dir}` *(2026.9.11.1+)* | the tree `mcpp pack` staged, absolute. `artifact` role only, and only under `mcpp pack --pkg-format <name>` |
 | `${mcpp.self}` *(2026.9.13.1+)* | the engine's own executable, absolute. An action's command is an argv with no shell, so a build program has no portable way to copy a file; the engine is present wherever a build runs, and `${mcpp.self} stage --verify content --output <dst> <src>` copies one file, creates the destination's parent, and writes only when the bytes differ. That argument shape is a contract from 2026.9.13.1 on; a build program that names it declares that release as its floor |
 
@@ -1002,7 +1002,7 @@ starting it. `data` is `program`, `argv`, `cwd`, `env` and `via`, as
 `launch` above. `--print-launch` takes no `--format`: on `mcpp run`, `--pkg-format`
 names a distributable.
 
-`data.configuration` (2026.11.6.1+) contains the selected program's `triple`,
+`data.configuration` (2026.11.7.1+) contains the selected program's `triple`,
 `profile` and resolved `platform`, using the same fields as the build record's
 configuration. For a target set it describes the leg selected for this launch.
 `configuration.runners` lists the available named runners, including project
 
@@ -7,7 +7,7 @@
 | 状态 | 评审中 v1.1 |
 | 版本 | 1.1 |
 | 最后修改 | 2026-11-06 |
-| 对应实现 | 基础保证: mcpp >= 2026.10.26.1; §5.1: mcpp >= 2026.11.6.1 |
+| 对应实现 | 基础保证: mcpp >= 2026.10.26.1; §5.1: mcpp >= 2026.11.7.1 |
 | 相关设计文档 | `.agents/docs/2026-10-26-control-contract-runtime-and-ide-ecosystem-design.md` §3、§4、§5.4 |
 | 相关 issue | #839 |
 | 使用文档 | [50 — 机器可读输出](../zh/50-machine-output.md) §9、§11 |
@@ -88,7 +88,7 @@ CI。在 2026.10.24.1 上,同一配置的两次冷构建相隔 0.1–0.5 s 启
 
 ### 5.1 分离编译的执行单元与恢复
 
-以下保证适用于 GCC 的 `bmi_schedule = "on"`（2026.11.6.1+）:
+以下保证适用于 GCC 的 `bmi_schedule = "on"`（2026.11.7.1+）:
 
 1. 普通编译与分离代码生成**必须**共用实际的 `jobs` 总上限。等待任务与调度任务
    **禁止**作为编译名额的替代。内核锁已释放而原编译单元仍被占用或状态未知时,