@@ -1,3 +1,8 @@
+---
+subject: compiler-scheduling
+status: active
+---
+
 # Compiler attempt lifetime and output recovery
 
 Status: source implementation and focused acceptance in progress. This record
@@ -207,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.5.2 | [mcpp 889](https://github.com/mcpp-community/mcpp/pull/889) |
+| Core | 2026.11.6.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
@@ -222,15 +227,43 @@ image consumer calls all four operations through the image convention,
 including the fifth retirement argument and an invalid continuation that
 changes the state output from `empty` to `unknown`.
 
-Source-group controls establish implementation behaviour. They do not establish
-that public versions are installable. Release gates remain full repository CI,
-canonical tag archives, byte-identical CN mirrors, published index entries and
-ordinary GLOBAL/CN consumers. Temporary image source overrides are removed
-before its final exact-head public-dependency CI. Platform and OS qualification
-follow the lower public group; core then updates its OS and default platform
-pins and runs full exact-head CI before independent ecosystem review. Plugins
-PR 52 retains the public 2026.11.5.1 pin until core 2026.11.5.2 is published,
-then runs its actual sidecar integration and final CI.
+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
+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
+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++
+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
+and the corrected one, including a real file identity. Native Clang, ARM and
+bootstrap jobs still require the next full CI run.
+
+An actual split-compiler control held a previously absent `.rc` observation
+until the controller had published status and exited. The earlier engine failed
+with `compiler controller ended without a status`; the corrected engine rereads
+status before treating controller loss as failure. Phase-one, quiet-unit and
+owner-witness observations use the same ordering rule. A real GCC build then
+passed its compiler-cap, cancellation, cached replay and same-invocation
+missing-object recovery controls. A missing status remains a bounded failure.
+
+On Windows, the unit fixture can derive its root from an 8.3 TEMP alias while
+the MSVC filesystem implementation records canonical long paths. Production
+`RunScope` already canonicalizes its root before admission. The fixture now
+does the same before deriving BMI, object and certificate paths; the native
+Windows suite must confirm the negative symlink controls remain intact.
+
+The generated Windows package launcher also named OS 0.2.9, whose OpenKal
+0.23 group conflicts with the current default platform 0.24. It now names
+OS 0.3.0. The older consumer platform selected by the application's own
+target remains independent of the launcher's build platform. The actual
+cross-platform packing control and complete CI remain release gates.
 
 ## Separate Windows build-program defect
 
 
@@ -1,3 +1,8 @@
+---
+subject: heterogeneous-build
+status: active
+---
+
 # Launch configuration and named test runners
 
 Status, 2026-11-06: implemented for candidate 2026.11.6.1. Focused local
 
@@ -18,7 +18,7 @@ superseded_by: 2026-09-07-....md  # when status is superseded
 ---
 ```
 
-350 records.
+352 records.
 
 ## By subject
 
@@ -38,6 +38,10 @@ Records that declare one. Everything else is listed by date below.
 
 - [BMI publication, compiler capacity and active download budgets](2026-11-06-bmi-publication-and-compiler-cap-closeout.md) — active
 
+### compiler-scheduling
+
+- [Compiler attempt lifetime and output recovery](2026-11-06-compiler-attempt-recovery.md) — active
+
 ### design
 
 - [升级的连续性：打包修订不在使用路径上替换载荷、替换失败不拆掉可用状态、home 中的悬空记录自愈、真实的升级 lane](2026-10-17-upgrade-continuity-design.md) — active
@@ -86,6 +90,7 @@ Records that declare one. Everything else is listed by date below.
 
 ### heterogeneous-build
 
+- [Launch configuration and named test runners](2026-11-06-launch-configuration-and-named-test-runners.md) — active
 - [异构构建语义与插件边界补充方案（mcpp#885、mcpp#887）](2026-11-05-heterogeneous-build-semantics-and-plugin-boundaries-supplement.md) — active
 - [异构构建补充方案的第二轮调研与实验](2026-11-05-heterogeneous-build-research-and-experiments.md) — active
 - [生态 885 与异构构建补充方案的实现依赖](2026-11-05-heterogeneous-build-implementation-plan.md) — active
@@ -171,6 +176,8 @@ Records that declare one. Everything else is listed by date below.
 
 ### 2026-11
 
+- [Launch configuration and named test runners](2026-11-06-launch-configuration-and-named-test-runners.md) — active
+- [Compiler attempt lifetime and output recovery](2026-11-06-compiler-attempt-recovery.md) — active
 - [BMI publication, compiler capacity and active download budgets](2026-11-06-bmi-publication-and-compiler-cap-closeout.md) — active
 - [异构构建语义与插件边界补充方案（mcpp#885、mcpp#887）](2026-11-05-heterogeneous-build-semantics-and-plugin-boundaries-supplement.md) — active
 - [异构构建补充方案的第二轮调研与实验](2026-11-05-heterogeneous-build-research-and-experiments.md) — active
 
@@ -8,6 +8,12 @@
 
 ### Fixed
 
+- A finished detached compiler is recognized when its final status appears
+  between status and liveness checks. Recovery still validates its output proof.
+- Windows launcher packages use the OS release required by the current default
+  platform, so their generated dependency resolves alongside openkal-platform 0.24.
+- Compiler attempt journals preserve file timestamps on Clang/libc++ when the
+  file clock uses a wider integer representation.
 - Launch descriptions include the selected target, profile, resolved platform
   and available named runners, including the reachable leg of a target set.
   Editor debug launches can retain the configuration that actually built the program.
 
@@ -1518,7 +1518,7 @@ the platform's own key names ([35 — Platforms](35-platforms.md)):
 
 ```toml
 [target.'cfg(os = "openkal")']
-platform = "openkal-platform@0.23.3"          # or { path = "…" }, or "none"
+platform = "openkal-platform@0.24.0"          # or { path = "…" }, or "none"
 
 [target.'cfg(platform = "openkal")'.layers]
 c-abi = { path = "../openkal-musl" }
 
@@ -956,7 +956,7 @@ and sha256. A provided format, `--merge` and `mcpp emit xpkg` read it
 ([SPEC-014](specs/packaging.md) §4.5):
 
 ```json
-{"schema": 1, "name": "hello", "version": "0.1.0", "platform": "openkal-platform@0.23.3",
+{"schema": 1, "name": "hello", "version": "0.1.0", "platform": "openkal-platform@0.24.0",
  "linkage": "shared", "mode": "vendored", "legs": ["x86_64-openkal", "aarch64-openkal"], "systems": [],
  "launch": {"runner": ["okrun", "{}"], "entry": {"x86_64": "lib/x86_64/hello.oke", "aarch64": "lib/aarch64/hello.oke"}},
  "files": [{"path": "lib/x86_64/hello.oke", "role": "image", "leg": "x86_64-openkal", "sha256": "…"}]}
 
@@ -40,13 +40,13 @@ mcpp run --target x86_64-openkal
 
 ```
     Resolved llvm@23.1.3 → x86_64-openkal → …/xim-x-llvm/23.1.3/bin/clang++
-             the platform's (openkal-platform 0.18.0), replacing your gcc@16.1.0 — override with `[target.x86_64-openkal] toolchain`
+             the platform's (openkal-platform 0.24.0), replacing your gcc@16.1.0 — override with `[target.x86_64-openkal] toolchain`
       Target x86_64-openkal → x86_64-unknown-none-elf
-             compiler-runtime  compiler-rt    (openkal-llvm-runtime@0.16.6, platform)
-             c-abi             musl           (openkal-musl@0.22.6, platform)
-             c++-abi           libc++         (openkal-llvm-runtime@0.16.6, platform)
-    Platform openkal-platform 0.18.0 (built-in)
-             tools             okld, okrun (openkal-tools@0.1.3, platform)
+             compiler-runtime  compiler-rt    (openkal-llvm-runtime@0.19.0, platform)
+             c-abi             musl           (openkal-musl@0.28.0, platform)
+             c++-abi           libc++         (openkal-llvm-runtime@0.19.0, platform)
+    Platform openkal-platform 0.24.0 (built-in)
+             tools             okld, okprof, okrun (openkal-tools@0.5.0, platform)
              runner            okrun (platform)
              link              lld, start ok_main (platform)
    Compiling app v0.1.0 (.)
@@ -113,9 +113,9 @@ The first of these that answers selects the target's platform:
 
 | Source | Spelling |
 |---|---|
-| the command line | `--platform openkal-platform@0.23.3`, `--platform path:../openkal-platform`, `--platform none` |
+| the command line | `--platform openkal-platform@0.24.0`, `--platform path:../openkal-platform`, `--platform none` |
 | the environment | `MCPP_TARGET_X86_64_OPENKAL_PLATFORM=…` |
-| the project | `[target.<selector>] platform = "openkal-platform@0.23.3"`, or `{ path = "…" }` |
+| the project | `[target.<selector>] platform = "openkal-platform@0.24.0"`, or `{ path = "…" }` |
 | this machine | the same key in `~/.mcpp/config.toml` |
 | the target table | the platform column (`mcpp toolchain list`) |
 
@@ -129,11 +129,11 @@ its own conventions. `[host] platform` selects a platform for them instead:
 
 ```toml
 [host]
-platform = "openkal-platform@0.23.3"
+platform = "openkal-platform@0.24.0"
 ```
 
 ```
-        Host platform openkal-platform 0.18.0 (mcpp.toml:2): build programs are x86_64-openkal images run by okrun
+        Host platform openkal-platform 0.24.0 (mcpp.toml:2): build programs are x86_64-openkal images run by okrun
 ```
 
 Every build program then compiles as an ok image of this machine's
@@ -151,7 +151,7 @@ implementation:
 
 ```toml
 [target.'cfg(any(linux, macos, windows))']
-platform = "openkal-platform@0.23.3"
+platform = "openkal-platform@0.24.0"
 ```
 
 On Windows the arrangement is the GNU ABI's row (`--target x86_64-windows-gnu`);
@@ -165,12 +165,12 @@ packages pin one another exactly. A graph that holds another version of one of
 them is refused before anything compiles:
 
 ```
-error: openkal-musl 0.22.2 is in this build, and the platform openkal-platform 0.18.0 is a version group that names openkal-musl 0.22.9.
+error: openkal-musl 0.22.2 is in this build, and the platform openkal-platform 0.24.0 is a version group that names openkal-musl 0.28.0.
        requested by: own
        The family's packages pin one another exactly, so two versions of one of
        them cannot be linked into one program. Either select the platform release
        of that version ([target.<selector>] platform = "openkal-platform@<version>"), or write
-       openkal-musl = "0.22.6" where it is requested.
+       openkal-musl = "0.28.0" where it is requested.
 ```
 
 A package taken from a directory or a repository is not bound by the group.
@@ -184,39 +184,40 @@ abridged:
 [package]
 namespace = "mcpplibs"
 name      = "openkal-platform"
-version   = "0.18.0"
-mcpp      = ">=2026.10.30.1"
+version   = "0.24.0"
+mcpp      = ">=2026.11.3.1"
 
 [platform]
 targets   = ["x86_64-openkal", "aarch64-openkal"]
 toolchain = "llvm@23.1.3"
-runner    = { cmd = ["okrun", "{}"], host = "same-arch" }
-carrier   = { package = "openkal-run@0.1.3", section = ".oke", main = "carrier/main.cpp" }
+runner    = { cmd = ["okrun", "{}"], host = "same-arch", hosts = ["linux-x86_64", "linux-aarch64", "macos-aarch64", "windows-x86_64"] }
+carrier   = { package = "openkal-run@0.5.0", section = ".oke", main = "carrier/main.cpp" }
 plugin    = "build.mcpp"
 
 [platform.layers]
-compiler-runtime = "openkal-llvm-runtime@0.16.6"
-"c++-abi"        = "openkal-llvm-runtime@0.16.6"
-c-abi            = { name = "openkal-musl", version = "0.22.6", default-features = false, features = ["posix"] }
+compiler-runtime = "openkal-llvm-runtime@0.19.0"
+"c++-abi"        = "openkal-llvm-runtime@0.19.0"
+c-abi            = { name = "openkal-musl", version = "0.28.0", default-features = false, features = ["posix", "malloc-mimalloc"] }
 
 [platform.tools]
-okld  = "openkal-tools@0.1.3"
-okrun = "openkal-tools@0.1.3"
+okld  = "openkal-tools@0.5.0"
+okprof = "openkal-tools@0.5.0"
+okrun = "openkal-tools@0.5.0"
 
 [platform.build]
-cxxflags = ["-fPIC", "-femulated-tls", "-fvisibility=hidden", "-fasynchronous-unwind-tables"]
+cxxflags = ["-fPIC", "-femulated-tls", "-fvisibility=hidden", "-fasynchronous-unwind-tables", "-Xclang", "-fstack-clash-protection", "-ffunction-sections", "-fdata-sections", "-fno-omit-frame-pointer", "-mno-omit-leaf-frame-pointer", "-fstack-protector-strong", "-mstack-protector-guard=global", "-ftrivial-auto-var-init=zero", "-D_LIBCPP_HARDENING_MODE=_LIBCPP_HARDENING_MODE_FAST"]
 
 [platform.build.'cfg(arch = "aarch64")']
-cxxflags = ["-ffixed-x18", "-mno-outline-atomics"]
+cxxflags = ["-ffixed-x18", "-mno-outline-atomics", "-mbranch-protection=pac-ret+bti"]
 
 [platform.link]
 driver = "lld"
 start  = "ok_main"
-flags  = ["-shared", "-z", "max-page-size=65536", "-z", "now", "--gc-sections", "--icf=safe", "--eh-frame-hdr"]
+flags  = ["-shared", "-z", "max-page-size=65536", "-z", "pack-relative-relocs", "-z", "now", "-z", "noexecstack", "--hash-style=both", "--gc-sections", "--icf=safe", "--eh-frame-hdr", "--build-id=sha1", "--emit-relocs", "-mllvm", "-emulated-tls"]
 inputs = [{ from = ["okld", "note-source"], as = "ok-notes.S" }]
 exe    = "{name}.oke"
 shared = "lib{name}.okso"
-seal   = [["okld", "note", "{}"], ["okld", "check", "{}", "--with", "{needed}"]]
+seal   = [["okld", "note", "{}"], ["okld", "place", "{}"], ["okld", "check", "{}", "--with", "{needed}"]]
 ```
 
 - **Programs are named, not located.** `okld` in `inputs` and `seal` is found among
 
@@ -527,7 +527,7 @@ installation, which is located on the machine rather than installed by mcpp. A
 target row is `{target, note, toolchain, pin, status, default}`, and `status` is
 one of `installed` / `available` / `via dependency graph` / `planned`.
 A target row also carries `platform` (2026.10.27.1+): the platform package the
-target table selects for it (`mcpplibs.openkal-platform@0.23.3`), or `null`.
+target table selects for it (`mcpplibs.openkal-platform@0.24.0`), or `null`.
 
 **`toolchain` and `pin` are not the same field twice.** `toolchain` is what
 the row is associated with — the installed payload on an installed row, the
 
@@ -127,5 +127,4 @@ CI。在 2026.10.24.1 上,同一配置的两次冷构建相隔 0.1–0.5 s 启
 | 版本 | 日期 | 变更 |
 |---|---|---|
 | 1.0 | 2026-10-26 | 首版:三段、构建目录锁、原子发布、`mcpp.lock` 的乐观写入、取消(#839) |
-
 | 1.1 | 2026-11-06 | 分离编译的单元观察、共享名额、绝对输出事务与有限恢复边界;对齐取消请求的 OS 接收方式。 |
@@ -237,7 +237,7 @@ openkal 目标上 `static` 为一个 `.oke`、无 `.okso`,`shared` 为 `.oke`
   "schema": 1,
   "name": "hello",
   "version": "0.1.0",
-  "platform": "openkal-platform@0.23.3",
+  "platform": "openkal-platform@0.24.0",
   "linkage": "declared",
   "mode": "vendored",
   "legs": ["x86_64-openkal", "aarch64-openkal"],