diff --git a/README.md b/README.md
index e88ca17..5b1b850 100644
--- a/README.md
+++ b/README.md
@@ -20,6 +20,12 @@ Use `python3 tools/setup-native.py --check --cargo-manifest catalog/rust/Cargo.t
 to check the local dependency graph. Existing platform rendering backends remain
 part of their applications; the framework controls the shared VM and UI sources.
 
+**Known gap:** the lock (and the matching Cargo revs) currently select
+Octoscript-Makepad `b1596d9c`, which is not on its `main`; the other OctoSense
+consumers are on `463e3da8` (makepad `cd812acd`). Until [#4](https://github.com/OctoSense-org/OctoScript-Android/issues/4)
+is fixed, prepare this repository in its own workspace rather than beside an
+OctoScript-App-Design-Flow checkout.
+
 
 Octoscript DSL rendered to **native Android widgets** from Rust — the Android peer of
 [Octoscript-OH](https://github.com/OctoSense-org/Octoscript-OH), which does the same against
diff --git a/README.zh-CN.md b/README.zh-CN.md
index e0da775..d60e869 100644
--- a/README.zh-CN.md
+++ b/README.zh-CN.md
@@ -17,6 +17,11 @@ OctoSense 外壳、App Hub 的 `card-host`、Mail 以及其他 OctoSense 应用
 用 `python3 tools/setup-native.py --check --cargo-manifest catalog/rust/Cargo.toml`
 检查本地依赖图。现有的各平台渲染后端仍然属于各自的应用；框架负责的是共享的 VM 和 UI 源码。
 
+**已知差异：** 目前锁文件（以及对应的 Cargo 版本）选定的是 Octoscript-Makepad `b1596d9c`，
+它不在该仓库的 `main` 上；其他 OctoSense 使用方都在 `463e3da8`（makepad `cd812acd`）。
+在 [#4](https://github.com/OctoSense-org/OctoScript-Android/issues/4) 修复之前，请把本仓库放在单独的工作区里准备，不要和
+OctoScript-App-Design-Flow 的 checkout 放在一起。
+
 
 用 Rust 把 Octoscript DSL 渲染成 **Android 原生控件**——它是
 [Octoscript-OH](https://github.com/OctoSense-org/Octoscript-OH/blob/master/README.zh-CN.md)
diff --git a/catalog/README.md b/catalog/README.md
index 7585953..1558c0f 100644
--- a/catalog/README.md
+++ b/catalog/README.md
@@ -67,7 +67,8 @@ views. The DSL — not Java — decides what the screen says.
 
 ## VM constraints discovered (the hard-won part)
 
-The makepad-script rev `e1c2164b` that `octoscript-render` pins has three shapes
+The makepad-script rev `e1c2164b` that `octoscript-render` pinned when these were
+found (the runtime is now selected by `native-runtime.lock.json`) has three shapes
 that silently produce a wrong tree rather than an error. All were found by
 host-side probing (`examples/probe.rs`) after they showed up as blank screens:
 
diff --git a/catalog/README.zh-CN.md b/catalog/README.zh-CN.md
index ba331cb..0edb4e9 100644
--- a/catalog/README.zh-CN.md
+++ b/catalog/README.zh-CN.md
@@ -65,7 +65,8 @@ cd .. && gradle assembleDebug && adb install -r app/build/outputs/apk/debug/app-
 
 ## 发现的 VM 限制（来之不易的部分）
 
-`octoscript-render` 锁定的 makepad-script 版本 `e1c2164b` 有三种写法会悄无声息地
+发现这些问题时，`octoscript-render` 锁定的 makepad-script 版本 `e1c2164b`（如今运行时由
+`native-runtime.lock.json` 选定）有三种写法会悄无声息地
 生成错误的树，而不是报错。三者都是先表现为空白页面，再通过宿主机侧探测
 （`examples/probe.rs`）找出来的：