@@ -187,3 +187,54 @@ A deterministic cancellation control kills a real wrapper, retains that
187187history, then starts a command returning seven without inflating peak one.
188188The prior false failure and its dead-process/empty-reservation evidence remain
189189part of the experiment record.
190+
191+ ## 2026-11-06 publication dependencies and remaining qualification
192+
193+ The source group carries the same four additive C operations through the
194+ native implementation, C library, C++ runtime, image runner and platform.
195+ The core consumes the OS composition rather than native process identifiers.
196+ No runtime generation becomes a dependency version or build-cache identity.
197+
198+ | Package | Candidate version | Review |
199+ | ---| ---| ---|
200+ | OpenKal | 0.24.0 | [ OpenKal 62] ( https://github.com/mcpplibs/openkal/pull/62 ) |
201+ | Linux implementation | 0.25.0 | [ Linux 51] ( https://github.com/mcpplibs/openkal-linux/pull/51 ) |
202+ | macOS implementation | 0.22.0 | [ macOS 43] ( https://github.com/mcpplibs/openkal-macos/pull/43 ) |
203+ | Windows implementation | 0.20.0 | [ Windows 44] ( https://github.com/mcpplibs/openkal-windows/pull/44 ) |
204+ | Emscripten implementation | 0.13.0 | [ Emscripten 15] ( https://github.com/mcpplibs/openkal-emscripten/pull/15 ) |
205+ | Image loader, runner, tools and binding | 0.5.0 | [ Image 29] ( https://github.com/mcpplibs/openkal-image/pull/29 ) |
206+ | C library | 0.28.0 | [ musl 86] ( https://github.com/mcpplibs/openkal-musl/pull/86 ) |
207+ | C++ runtime | 0.19.0 | [ Runtime 66] ( https://github.com/mcpplibs/openkal-llvm-runtime/pull/66 ) |
208+ | Platform | 0.24.0 | Publication follows its public lower dependencies |
209+ | OS composition | 0.2.10 | [ OS 17] ( https://github.com/mcpplibs/os/pull/17 ) |
210+ | Core | 2026.11.5.2 | [ mcpp 889] ( https://github.com/mcpp-community/mcpp/pull/889 ) |
211+
212+ Emscripten receives dependency metadata alignment; it does not acquire process
213+ support. The image runner retains its existing generated binding mechanism,
214+ format, prefetch and cache policies. Its generated table retains all 153 prior
215+ C names and adds exactly the four declared-unit names, for 157 total. The new
216+ image consumer calls all four operations through the image convention,
217+ including the fifth retirement argument and an invalid continuation that
218+ changes the state output from ` empty ` to ` unknown ` .
219+
220+ Source-group controls establish implementation behaviour. They do not establish
221+ that public versions are installable. Release gates remain full repository CI,
222+ canonical tag archives, byte-identical CN mirrors, published index entries and
223+ ordinary GLOBAL/CN consumers. Temporary image source overrides are removed
224+ before its final exact-head public-dependency CI. Platform and OS qualification
225+ follow the lower public group; core then updates its OS and default platform
226+ pins and runs full exact-head CI before independent ecosystem review. Plugins
227+ PR 52 retains the public 2026.11.5.1 pin until core 2026.11.5.2 is published,
228+ then runs its actual sidecar integration and final CI.
229+
230+ ## Separate Windows build-program defect
231+
232+ The released 2026.11.5.1 engine can try to install ` msvc@system ` as an indexed
233+ ` xim ` package when a Windows host with the MSVC default executes a ` build.mcpp `
234+ for a bare cross target. The specification's ABI-layout fixture exposed this
235+ path because its build program only supplied an include directory. Declaring
236+ that directory through the existing ` [build].include_dirs ` preserves the real
237+ 32/64-bit target-layout assertions and removes that unnecessary host build.
238+ It does not fix the engine's MSVC host-toolchain selection. This is a core
239+ build-program/toolchain issue, separate from unit lifetime and recovery, and
240+ remains an explicit review limitation of this source group.
0 commit comments