docs: distinguish exact pins from compatible OS ranges

Author: Sunrisepeak

.agents/docs/2026-11-06-compiler-attempt-recovery.md

@@ -209,8 +209,9 @@ No runtime generation becomes a dependency version or build-cache identity.
 | 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) |
 
-OS advances to 0.3.0 so an existing 0.2 constraint cannot silently absorb a
-different OpenKal minor group. The core updates all four OS requirements
+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
+addresses; `os = "0.2.3"` itself does not automatically upgrade. The core updates all four OS requirements
 together. Platform 0.24 is the corresponding explicit image/hosted boundary.
 
 Emscripten receives dependency metadata alignment; it does not acquire process

docs/24-openkal-cross.md

@@ -415,7 +415,7 @@ Both built-in openkal targets select platform 0.24.0 by default (2026.11.5.2+).
 An explicit `platform` configuration overrides that selection. This platform
 preserves the emulated TLS convention through the final ThinLTO link.
 
-OS 0.3 uses the OpenKal 0.24 dependency group. A project retaining OS 0.2
+OS 0.3 uses the OpenKal 0.24 dependency group. A project retaining OS 0.2.9
 selects a platform from the matching 0.23 group explicitly; incompatible
 OpenKal minor requirements are rejected during dependency resolution.
 

docs/zh/24-openkal-cross.md

@@ -364,7 +364,7 @@ mcpp run   --target x86_64-openkal      # okrun bin/app.oke
 两个内置 openkal 目标默认选择平台 0.24.0（2026.11.5.2+）。显式 `platform` 配置可覆盖默认选择；
 该平台的最终 ThinLTO 链接保持 emulated TLS 约定。
 
-OS 0.3 使用 OpenKal 0.24 依赖组。保留 OS 0.2 的工程显式选择匹配的 0.23 平台组；
+OS 0.3 使用 OpenKal 0.24 依赖组。保留 OS 0.2.9 的工程显式选择匹配的 0.23 平台组；
 不兼容的 OpenKal 次版本要求在依赖解析阶段被拒绝。
 
 | | 平台的陈述 | 原因 |