docs: purge chain-of-thought leakage from prose

Delete design-session citations (decision/audit/plan ordinals, stack
positions), change narration, review choreography, and reviewer-addressed
justification from comments, JSDoc, docs, READMEs, Agent Notes, tests, and
generator templates; restate every affected fact as current-state contract
prose. Fix generated docs at their sources and regenerate the catalogs and
cordis-surface regions; re-paste type-equiv blocks; update every bilingual
counterpart and re-record the pairs. Record the citation rule in the
committed-artifact-citations Agent Note.

native/landlock-run/README.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write native/landlock-run/README.md
-README.md: fcb8e8249e6728d925fd08c938a780b155d3d4ac
-README.zh.md: 6ae8d7d1d5ae4f2bda90cbf6aa74321a0dab3cb9
+README.md: bf9b163d42a9b7402dbf4c045d47e7b8d36e15ab
+README.zh.md: 7bd4765a73f0d5df2a4710ce06ff319f6c902db6

native/landlock-run/README.md

@@ -4,7 +4,7 @@ English | [中文](README.zh.md)
 
 A [Landlock](https://landlock.io/) self-restrict-then-exec launcher for confining subprocesses on Linux, distributed as prebuilt per-platform npm packages plus a thin JS entry package that resolves the binary and speaks its CLI contract. Built for agent harnesses and other hosts that need to run untrusted commands under a filesystem allow-list without confining themselves.
 
-The first tool is **`landlock-run`** — a self-restrict-then-exec [Landlock](https://landlock.io/) launcher (~300 lines of C11 over the raw kernel UAPI, statically linked against musl). It installs a Landlock ruleset on itself and `exec`s the wrapped command; the ruleset is inherited across `execve`, so the command and every process it spawns run confined while the invoking process stays unrestricted. Fail-closed: if the kernel cannot enforce, it exits without running the command.
+The tool is **`landlock-run`** — a self-restrict-then-exec [Landlock](https://landlock.io/) launcher (~300 lines of C11 over the raw kernel UAPI, statically linked against musl). It installs a Landlock ruleset on itself and `exec`s the wrapped command; the ruleset is inherited across `execve`, so the command and every process it spawns run confined while the invoking process stays unrestricted. Fail-closed: if the kernel cannot enforce, it exits without running the command.
 
 ## Install
 

native/landlock-run/README.zh.md

@@ -4,7 +4,7 @@
 
 一个 [Landlock](https://landlock.io/)「先限制自身、再执行」启动器，用于在 Linux 上限制子进程。它以按平台预构建的 npm 包以及一个轻量 JS 入口包的形式发布；入口包负责解析二进制文件并遵循其 CLI（命令行界面）约定。该启动器面向需要让不可信命令在文件系统允许清单约束下运行、同时保持自身不受限制的 agent harness（智能体框架）和其他宿主。
 
-第一个工具是 **`landlock-run`**：一个「先限制自身、再执行」的 [Landlock](https://landlock.io/) 启动器（基于原始内核 UAPI 编写，约 300 行 C11，并与 musl 静态链接）。它在自身上安装 Landlock 规则集，再 `exec` 被包装的命令；该规则集会跨 `execve` 继承，因此命令及其产生的每个进程都在限制下运行，调用进程仍不受限制。它采用失败闭合：如果内核无法强制执行，则不运行命令并直接退出。
+该工具是 **`landlock-run`**：一个「先限制自身、再执行」的 [Landlock](https://landlock.io/) 启动器（基于原始内核 UAPI 编写，约 300 行 C11，并与 musl 静态链接）。它在自身上安装 Landlock 规则集，再 `exec` 被包装的命令；该规则集会跨 `execve` 继承，因此命令及其产生的每个进程都在限制下运行，调用进程仍不受限制。它采用失败闭合：如果内核无法强制执行，则不运行命令并直接退出。
 
 ## 安装
 

native/landlock-run/packages/entry/src/main.c

@@ -89,8 +89,7 @@ struct landlock_path_beneath_attr {
 
 /*
  * Newest ABI this build knows; the negotiation below scales the actual
- * ruleset down to what the running kernel supports (the best-effort compat
- * stance of the previous Rust launcher, made explicit).
+ * ruleset down to what the running kernel supports.
  */
 #define MAX_ABI 5L
 
@@ -141,8 +140,7 @@ struct cli {
 };
 
 /*
- * Hand-rolled argv parsing — four flags do not justify a parsing library,
- * and the previous Rust launcher made the same call for the same reason.
+ * Hand-rolled argv parsing — four flags do not justify a parsing library.
  * Returns 0 on success, else the process exit code (message already printed).
  */
 static int parse(int argc, char **argv, struct cli *cli) {
@@ -204,8 +202,7 @@ static int add_rule(int ruleset_fd, const char *path, uint64_t access) {
   }
   /* The kernel rejects directory-only accesses on a non-directory rule
    * (EINVAL), so a file grant keeps only the file-compatible bits — how the
-   * `--rw /dev/null` grant works. Same clamp the Rust crate's
-   * path_beneath_rules helper applied. */
+   * `--rw /dev/null` grant works. */
   struct stat st;
   if (fstat(path_fd, &st) == 0 && !S_ISDIR(st.st_mode)) {
     access &= LL_FS_EXECUTE | LL_FS_WRITE_FILE | LL_FS_READ_FILE | LL_FS_TRUNCATE | LL_FS_IOCTL_DEV;