@hmos-library-adapter/fast 0.0.17-beta.0 → 0.0.17-beta.2

package/node_modules/@ohos-agent/pc-adapter/skills/pc-error-atlas/knowledge/errors/E356.md

@@ -0,0 +1,79 @@
+<!-- 本文件由同步脚本自动生成，请勿手改。如需修正请更新知识源数据后重新运行 `npm run sync:kb`。 -->
+
+# E356: Validate fixed-target compilers without mixing target ABIs
+
+> **严重度**: 🟡 medium | **分类**: compiler, testing, abi, path-c, source-provenance | **自动修复**: ❌
+
+---
+
+## 错误特征
+
+```
+make: inaccessible or not found
+Read-only file system
+features.h:.*no expression
+bits/alltypes.h:.*expected an expression
+in eval_const_expr: no expression
+in primary: expected an expression
+in paste: invalid preprocessing token
+cannot open file: No such file or directory
+```
+
+## 根因
+
+chibicc/1.0.24.1 builds and runs as an OHOS/armv8 executable but unconditionally generates x86-64 code. Upstream tests link and execute the generated x86-64 programs, so the armv8 worker cannot provide executable evidence. Injecting OHOS/armv8 libc headers mixes target ABIs. A musl x86-64 environment is also insufficient for this fork because its self-hosted source assumes glibc header and linker layouts; native execution evidence therefore requires a matching glibc x86-64 userspace.
+
+## 验证命令
+
+```bash
+CI_PACKAGES="〈外部知识库归档〉" zsh 〈外部知识库流水线〉; CHIBICC_SOURCE_DIR=<verified-source> CHIBICC_RESULTS_DIR=<results> bash test_package/test_native_x86_64.sh
+```
+
+## 解决方案
+
+**two-plane-fixed-target-validation**：Keep the OHOS/armv8 package gate fail-closed at the source-owned compile boundary, then run the complete upstream stage1 and genuinely self-hosted stage2 suites in a matching glibc x86-64 environment. Require exact source inventories, per-case terminal states, both driver suites, all 13 stage2 self-hosted objects, and explicit pass and execution denominators. Preserve deterministic XFAIL, target-header blockers, compile failures, runtime failures, and missing dependency blockers as non-PASS outcomes.
+
+```bash
+CHIBICC_SOURCE_DIR=<verified-source> CHIBICC_RESULTS_DIR=<results> CHIBICC_JOBS=4 bash test_package/test_native_x86_64.sh
+```
+
+## 回退方案
+
+**external-glibc-x86_64-runner**：Run the committed native harness in QEMU TCG or equivalent x86-64 Linux virtualization when no physical x86-64 worker is available. Verify the guest is glibc based and retain the result TSV and logs.
+
+```bash
+make LDFLAGS= test && make LDFLAGS= test-stage2
+```
+
+## 🚫 禁止策略
+
+### 🚫 禁止 1
+
+- **模式**：`merge OHOS armv8 libc or dependency headers into chibicc x86-64 code generation`
+- **原因**：Header declarations describe the worker ABI while chibicc emits another ABI; parse success would not prove a valid target build.
+- **后果**：Compile counts overstate validity and can hide ABI-level incompatibility.
+
+### 🚫 禁止 2
+
+- **模式**：`classify every cannot-open-file diagnostic as target-header-blocked`
+- **原因**：Missing local fixtures, path regressions, and undeclared dependencies would be silently accepted.
+- **后果**：The test package can pass while source-owned tests were not compiled.
+
+### 🚫 禁止 3
+
+- **模式**：`claim blocked inventory, compile-only coverage, or XFAIL as upstream executable pass`
+- **原因**：Inventory coverage does not execute generated x86-64 programs, and XFAIL remains a measured non-PASS result.
+- **后果**：PR evidence violates non-weakening and test-accounting requirements.
+
+### 🚫 禁止 4
+
+- **模式**：`accept only an aggregate failure count, allow XPASS silently, or call a hybrid stage2 build self-hosted`
+- **原因**：Aggregate counts can conceal replacement regressions; XPASS means the inventory is stale; host-object fallback does not validate self-hosting.
+- **后果**：Regressions and bootstrap failures can be mislabeled as successful validation.
+
+## 涉及软件
+
+Compiler packages whose generated-code target architecture or target libc differs from the OHOS worker environment.
+
+---
+*条目 E356 · 更新 2026-08-14 · 知识库同步生成物*

package/node_modules/@ohos-agent/pc-adapter/skills/pc-error-atlas/knowledge/errors/E357.md

@@ -0,0 +1,77 @@
+<!-- 本文件由同步脚本自动生成，请勿手改。如需修正请更新知识源数据后重新运行 `npm run sync:kb`。 -->
+
+# E357: Allowlist informational daemon probes before mandatory global configuration loading
+
+> **严重度**: 🟡 medium | **分类**: configure, testing, cli, daemon, fail-closed | **自动修复**: ❌ | **原则**: [P004](../principles.md#P004)、[P005](../principles.md#P005)
+
+---
+
+## 错误特征
+
+```
+Can't open options file.*No such file
+unable to open.*(system
+global).*(options
+config)
+--version.*(failed
+exit)
+--help.*(failed
+exit)
+```
+
+## 根因
+
+A privileged or system daemon loads mandatory global configuration before dispatching command-line informational options, so a packaged binary cannot answer version/help in an undeployed consumer environment even though those requests need no configuration, device or privilege.
+
+## 验证命令
+
+```bash
+Run the installed binary with exactly one version option and one help option, then pass an explicitly missing configuration file and require that operational path to remain nonzero.
+```
+
+## 解决方案
+
+**early-informational-option-allowlist**：Before mandatory global configuration, recognize only argc==2 with an exact allowlist of side-effect-free information options; delegate to the upstream parser/handler so output and exit semantics are preserved, and leave every other argv shape on the original path.
+
+```bash
+Add a platform-guarded argc==2 allowlist before configuration loading, call the existing argument parser, then test version, help, and a missing explicit config negative control.
+```
+
+## 回退方案
+
+**staged-config-consumer-test**：If the upstream parser cannot safely dispatch information handlers before initialization, stage a minimal package-owned configuration root for the consumer test and document that the binary has no pre-deployment probe.
+
+```bash
+Set the tool's supported config-root option to a temporary package-owned directory; do not write host /etc or /system paths.
+```
+
+## 🚫 禁止策略
+
+### 🚫 禁止 1
+
+- **模式**：`parse_args\(argc.*before.*config|skip.*config.*argc|--version.*in.*argv`
+- **原因**：Broad early parsing or substring detection can accept mixed operational arguments and bypass mandatory security or service configuration.
+- **后果**：A command that should initialize devices, credentials or network state can execute without its required policy input.
+
+### 🚫 禁止 2
+
+- **模式**：`echo.*version|printf.*version|stub.*--version|wrapper.*--help`
+- **原因**：Hard-coded package wrappers do not execute the delivered daemon and can drift from its actual version/help behavior.
+- **后果**：Consumer tests pass while the installed binary remains unusable before deployment.
+
+### 🚫 禁止 3
+
+- **模式**：`(touch|echo|install).*(/etc|/system).*options|create.*fake.*config`
+- **原因**：Mutating host configuration to make a smoke test pass hides the pre-deployment failure and can affect later tests or the device.
+- **后果**：Validation becomes non-isolated and may change system or network behavior.
+
+## 涉及软件
+
+Native daemons and system-management tools whose pure version/help handlers are side-effect free but occur after mandatory host configuration, identity, device or service initialization.
+
+## 相关模式
+
+- **相似模式**：[E214](E214.md)、[E246](E246.md)
+
+---
+*条目 E357 · 更新 2026-08-14 · 知识库同步生成物*

package/node_modules/@ohos-agent/pc-adapter/skills/pc-error-atlas/knowledge/errors/E358.md

@@ -0,0 +1,59 @@
+<!-- 本文件由同步脚本自动生成，请勿手改。如需修正请更新知识源数据后重新运行 `npm run sync:kb`。 -->
+
+# E358: 旧 Rust Unix 依赖锁图在 OHOS target_env 下的确定性迁移
+
+> **严重度**: 🟡 medium | **分类**: rust, cargo-ohos-lock-compatibility | **自动修复**: ❌ | **原则**: [P004](../principles.md#P004)、[P014](../principles.md#P014)
+
+---
+
+## 错误特征
+
+```
+unresolved import.*libc
+mismatched types.*nix
+target_env.*ohos
+could not compile.*libc
+```
+
+## 根因
+
+旧 Cargo.lock 固定的 libc/nix/ctrlc 版本早于 OHOS target_env 支持，并与现代 Rust 1.97 的目标 ABI/cfg 组合不兼容；仅设置 linker 无法修复依赖源码和锁图。
+
+## 验证命令
+
+```bash
+cargo build --release --locked && cargo test --workspace --release --locked --tests
+```
+
+## 解决方案
+
+**semver-bounded-deterministic-lock-migration**：先定位引入旧 nix/libc 的直接依赖，在上游 Cargo.toml 允许的 semver 范围内升级最小根依赖，让 Cargo 重解确定性传递锁图；把 Cargo.lock 差异作为可审计补丁导出，并保持 --locked 构建、上游测试和消费者负测。
+
+```bash
+cargo update -p ctrlc --precise 3.5.2 && cargo build --release --locked && cargo test --workspace --release --locked --tests
+```
+
+## 回退方案
+
+**patch-minimal-transitive-crate**：若上游直接依赖约束不允许兼容版本，拆分依赖适配或对最小传递 crate 提交独立平台补丁，不在消费者配方中修改 registry cache。
+
+## 🚫 禁止策略
+
+### 🚫 禁止 1
+
+- **模式**：`cargo build(?!.*--locked)|cargo update$`
+- **原因**：无边界更新或移除 --locked 会掩盖实际依赖图并破坏可复现性。
+- **后果**：CI 与真机解析到不同依赖版本，无法审计真正的 OHOS 修复。
+
+### 🚫 禁止 2
+
+- **模式**：`\.cargo/registry/src|site-packages.*cargo`
+- **原因**：禁止修改设备全局 Cargo registry cache。
+- **后果**：污染共享真机缓存并让其他任务结果不可复现。
+
+## 涉及软件
+
+在 HarmonyOS/OHOS 上使用现代 Rust 编译器构建、且 Cargo.lock 固定旧 libc/nix/ctrlc Unix 依赖图的 Rust CLI 和库。
+
+---
+*条目 E358 · 更新 2026-08-16 · 知识库同步生成物*

package/node_modules/@ohos-agent/pc-adapter/skills/pc-error-atlas/knowledge/errors/E359.md

@@ -0,0 +1,69 @@
+<!-- 本文件由同步脚本自动生成，请勿手改。如需修正请更新知识源数据后重新运行 `npm run sync:kb`。 -->
+
+# E359: 将 Conan 构建上下文编译器映射到自定义 HOSTCC/HOSTLD
+
+> **严重度**: 🟡 medium | **分类**: cross-compile, conan, build-context, custom-build-system | **自动修复**: ❌
+
+---
+
+## 错误特征
+
+```
+checking for program gcc\.\.\. no
+check_host_cc.*failed
+HOSTCC.*not found
+Exec format error.*build tool
+```
+
+## 根因
+
+自定义构建系统在生成目标产物之外，还需编译并立即运行构建机工具；上游使用 HOSTCC/HOSTLD，而 Conan GNU 工具链在 build profile 显式配置原生 compiler_executables 时可导出 CC_FOR_BUILD。变量未映射时会默认探测不存在的 gcc；异构交叉编译中缺失 CC_FOR_BUILD 时若回退目标 CC，会生成无法在构建机执行的工具。
+
+## 验证命令
+
+```bash
+grep -R "HOSTCC\|HOSTLD\|CC_FOR_BUILD" configure Makefile scripts; file <build-tool>; <build-tool> --help; conan create <recipe> -pr:h=<target> -pr:b=<build>
+```
+
+## 解决方案
+
+**map-conan-build-compiler-to-upstream-host-variables**：用 cross_building(self) 区分上下文。原生构建映射工具链 CC；真正交叉构建只接受由 build profile compiler_executables 或构建上下文 tool_requires 显式提供的 CC_FOR_BUILD，缺失时立即失败，禁止回退目标 CC。HOSTLD 使用同一原生编译器驱动。映射必须在 env=conanbuild 中展开。
+
+```bash
+if cross_building(self): require_nonempty("CC_FOR_BUILD"); host_compiler = "$CC_FOR_BUILD"
+else: host_compiler = "$CC"
+self.run(f'./configure LD="$CC" HOSTCC="{host_compiler}" HOSTLD="{host_compiler}" ...', env="conanbuild")
+```
+
+## 回退方案
+
+**explicit-native-build-tool-package**：若 build profile 没有提供构建机编译器，则通过 tool_requires 提供原生编译器并将其 buildenv_info/conf_info 映射到 CC_FOR_BUILD；不得使用目标交叉编译器生成随后要立即运行的工具。
+
+```bash
+conan create . -pr:h=<target-profile> -pr:b=<build-profile>
+```
+
+## 🚫 禁止策略
+
+### 🚫 禁止 1
+
+- **模式**：`HOSTCC=\$CC.*cross|HOSTCC=.*target.*clang`
+- **原因**：真正异构交叉构建时目标编译器生成的程序不能在构建机执行
+- **后果**：文档生成器或代码生成器运行时报 Exec format error，或者配置探针得到错误结果
+
+### 🚫 禁止 2
+
+- **模式**：`HOSTCC=gcc|HOSTLD=ld`
+- **原因**：硬编码工具名绕过 Conan build profile，且裸 ld 可能缺少编译器驱动提供的启动文件与默认库
+- **后果**：OHOS 环境找不到 gcc，或宿主工具链接失败
+
+## 涉及软件
+
+使用 HOSTCC/HOSTLD、BUILD_CC、CC_FOR_BUILD 等变量编译代码生成器、文档生成器或配置探针，并在构建阶段立即运行它们的 custom Make、Kbuild 或非标准 configure 项目
+
+## 相关模式
+
+- **相似模式**：[E095](E095.md)、[E097](E097.md)
+
+---
+*条目 E359 · 更新 2026-08-16 · 知识库同步生成物*

package/node_modules/@ohos-agent/pc-adapter/skills/pc-error-atlas/knowledge/errors/E360.md

@@ -0,0 +1,64 @@
+<!-- 本文件由同步脚本自动生成，请勿手改。如需修正请更新知识源数据后重新运行 `npm run sync:kb`。 -->
+
+# E360: CMake static-only 构建必须保持安装导出的逻辑包身份稳定
+
+> **严重度**: 🔴 blocking | **分类**: cmake, static-library, consumer, install-export | **自动修复**: ❌ | **原则**: [P005](../principles.md#P005)、[P012](../principles.md#P012)
+
+---
+
+## 错误特征
+
+```
+include could not find requested file:.*[A-Za-z0-9_]+Targets\.cmake
+```
+
+## 根因
+
+构建脚本把同时参与目标命名与 install(EXPORT)/Config.cmake 生成的可变库名在 static-only 分支改成带 -static 后缀，而 Config 模板仍以不可变 PROJECT_NAME 引用 Targets，导致包目录、Config、Targets 与 include 路径发生身份漂移。
+
+## 验证命令
+
+```bash
+cmake -S . -B build -DBUILD_SHARED_LIBS=OFF -DBUILD_STATIC_LIBS=ON -DCMAKE_INSTALL_PREFIX="$PREFIX" && cmake --build build && cmake --install build && cmake -S consumer -B consumer-build -DCMAKE_PREFIX_PATH="$PREFIX" && cmake --build consumer-build
+```
+
+## 解决方案
+
+**separate-logical-package-identity-from-artifact-variant**：先按项目变量图手工修改 CMake 源码：保持 PROJECT_NAME 或独立 PACKAGE_NAME 作为不可变的安装包身份；仅在真实 target 名、ALIAS 和 OUTPUT_NAME 上表达 static/shared 变体，并让 Config、Targets、安装目录和 include 根目录统一使用稳定包名。修改完成后执行 rec_command 验证安装结果。
+
+```bash
+cmake -S . -B build -DBUILD_SHARED_LIBS=OFF -DBUILD_STATIC_LIBS=ON -DCMAKE_INSTALL_PREFIX="$PREFIX" && cmake --build build && cmake --install build && cmake -S consumer -B consumer-build -DCMAKE_PREFIX_PATH="$PREFIX" && cmake --build consumer-build
+```
+
+## 回退方案
+
+**generate-explicit-stable-package-config**：若短期不能拆分变量，显式用稳定 PROJECT_NAME 生成并安装 Config/Targets，同时逐项断言 Config 引用的 Targets 文件和 include 路径确实存在。
+
+```bash
+cmake -S consumer -B consumer-build -DCMAKE_PREFIX_PATH="$PREFIX" --debug-find
+```
+
+## 🚫 禁止策略
+
+### 🚫 禁止 1
+
+- **模式**：`set\([^)]*(LIBNAME|PACKAGE_NAME)[^)]*-(static|shared)[^)]*\)`
+- **原因**：不要在变体分支修改后续还用于 install(EXPORT)、Config 生成或安装路径的逻辑包名。
+- **后果**：安装可成功但导出文件互相引用不存在的名称，标准 find_package 在消费者配置阶段失败。
+
+### 🚫 禁止 2
+
+- **模式**：`find_package\([^)]*-(static|shared)`
+- **原因**：不要让消费者改用带变体后缀的包名来掩盖生产者导出图不一致。
+- **后果**：非标准包身份泄漏到下游，而且 Config 内部 Targets/include 引用仍可能损坏。
+
+## 涉及软件
+
+所有用同一可变名称驱动 add_library、install(EXPORT)、configure_package_config_file 和安装目录，并在 static-only/shared-only 分支追加变体后缀的 CMake 工程。
+
+## 相关模式
+
+- **相似模式**：[E216](E216.md)、[E278](E278.md)
+
+---
+*条目 E360 · 更新 2026-08-15 · 知识库同步生成物*

package/node_modules/@ohos-agent/pc-adapter/skills/pc-error-atlas/knowledge/errors/E361.md

@@ -0,0 +1,63 @@
+<!-- 本文件由同步脚本自动生成，请勿手改。如需修正请更新知识源数据后重新运行 `npm run sync:kb`。 -->
+
+# E361: Gate detached-descendant canaries on post-cleanup release
+
+> **严重度**: 🟡 medium | **分类**: cleanup, mpi, openharmony, process-control, timeout | **自动修复**: ❌
+
+---
+
+## 错误特征
+
+```
+managed MPI command exceeded [0-9]+ seconds: .*test_process_control.*detach
+detached MPI descendant wrote delayed canary for detach
+```
+
+## 根因
+
+A managed MPI launcher may either return while a detached descendant remains or stay live until the bounded harness timeout. The initial timeout acceptance still used a canary written four seconds after startup even though timeout cleanup cannot begin until 15 seconds, so the canary measured pre-cleanup lifetime rather than post-cleanup escape. Substring mode matching also allowed detach to match detach-kill.
+
+## 验证命令
+
+```bash
+Execute exact returned-live and timeout positives plus wrong-timeout, wrong-executable, wrong-mode, malformed evidence, survivor, pre/post-gate canary, repeated-gate and unexpected-success negatives; compile and run the C gate harness and prove zero-residue assertion precedes the timeout raise.
+```
+
+## 解决方案
+
+**bound-timeout-plus-post-cleanup-token-gate**：Keep a finite timeout and parse its command list exactly. Make the child publish an armed token and wait; only after zero-residue cleanup and escape-PID absence may the host create-new the exact release token. Reject any canary before or after that gate, then run a fresh MPI smoke test.
+
+```bash
+python validate_r65_detached_cleanup_gate.py --conanfile <test_package/conanfile.py> --process-source <test_process_control.c> --scratch <E-drive scratch>
+```
+
+## 回退方案
+
+**returned-live-descendant-path**：Preserve the existing path where mpiexec returns while a tracked descendant remains; clean it by exact process identity and enforce the same postconditions.
+
+## 🚫 禁止策略
+
+### 🚫 禁止 1
+
+- **模式**：`except.*timeout.*pass|managed MPI command exceeded.*return`
+- **原因**：A generic timeout does not prove that the intended process-control probe ran or that cleanup completed.
+- **后果**：Real MPI hangs or foreign residue can be mislabeled as expected containment.
+
+### 🚫 禁止 2
+
+- **模式**：`outer_timeout\s*=\s*[3-9][0-9]+|sleep\([3-9][0-9]+\)`
+- **原因**：Increasing the budget hides the contract mismatch and does not prove descendant containment.
+- **后果**：Device time is consumed while the same launcher topology remains unresolved.
+
+### 🚫 禁止 3
+
+- **模式**：`kill.*pid(?!.*start)|terminate.*process(?!.*identity)`
+- **原因**：PID-only cleanup is vulnerable to reuse and may affect a foreign process.
+- **后果**：Cleanup can cross the task ownership boundary.
+
+## 涉及软件
+
+MPI test harnesses that intentionally create double-forked or session-detached descendants and manage the complete launcher tree with PID/starttime/token identity.
+
+---
+*条目 E361 · 更新 2026-08-15 · 知识库同步生成物*

package/node_modules/@ohos-agent/pc-adapter/skills/pc-error-atlas/knowledge/errors/E362.md

@@ -0,0 +1,72 @@
+<!-- 本文件由同步脚本自动生成，请勿手改。如需修正请更新知识源数据后重新运行 `npm run sync:kb`。 -->
+
+# E362: Materialize dependency-owned resources when the target filesystem forbids links
+
+> **严重度**: 🟡 medium | **分类**: hmdfs, conan, packaging, symlink, resource-layout | **自动修复**: ❌
+
+---
+
+## 错误特征
+
+```
+PermissionError.*os.symlink
+Permission denied.*symlink
+missing packaged resource.*link
+dangling symbolic link
+```
+
+## 根因
+
+An upstream resource package may install relative links to files owned by another runtime package. Archive extraction or package copy can omit dangling links, while explicit symlink creation can be rejected by the target filesystem. Blindly copying similarly named local files loses the ownership contract and can silently package stale or unrelated content.
+
+## 验证命令
+
+```bash
+Resolve the exact dependency node from self.dependencies, materialize each required resource into the consumer package as a regular file, reject missing source resources, then compare every installed file byte-for-byte with its dependency-owned source in test_package.
+```
+
+## 解决方案
+
+**dependency-derived-resource-materialization**：Keep the upstream public filename, but derive the source path from the exact Conan dependency package_folder. Copy each dependency-owned target as a regular file during package(), fail if the source does not exist, and expose no machine-specific cache path. In test_package, require a regular non-link file and compare its complete bytes with the same resolved dependency source. Validate the full expected resource inventory separately.
+
+```bash
+dependency_root = self.dependencies["<dependency>"].package_folder
+# Map each upstream linked name to its dependency-owned source.
+# copy(..., keep_path=False) into the package public resource directory.
+# In test_package: test -f "$dst" && test ! -L "$dst" && cmp -s "$src" "$dst"
+```
+
+## 回退方案
+
+**preserve-links-on-capable-filesystem**：Preserve the upstream relative links only when the packaging and runtime filesystems both support them and the installed dependency layout makes every target resolvable. Still validate targets and inventory from a clean package.
+
+## 🚫 禁止策略
+
+### 🚫 禁止 1
+
+- **模式**：`os\.symlink|ln -s`
+- **原因**：Recreating links does not solve a filesystem policy that rejects link creation and may fail late in package().
+- **后果**：The package build fails or produces missing public resources.
+
+### 🚫 禁止 2
+
+- **模式**：`(\.conan2|storage/Users|package_folder).*hard.?cod|copy.*source_folder.*shared`
+- **原因**：Hard-coded cache paths or unrelated source-tree copies are not bound to the dependency revision selected by Conan.
+- **后果**：A fresh cache can package stale or ABI-incompatible resource content.
+
+### 🚫 禁止 3
+
+- **模式**：`exists.*only|test -f.*without.*cmp|skip.*content`
+- **原因**：Existence alone cannot prove that materialization preserved the dependency-owned resource contract.
+- **后果**：Empty, stale, or wrongly mapped resources can pass the consumer test.
+
+## 涉及软件
+
+Conan packages whose upstream resource layout links to files supplied by a declared dependency, when the target package filesystem cannot preserve or create those links.
+
+## 相关模式
+
+- **相似模式**：[E292](E292.md)、[E274](E274.md)、[E316](E316.md)
+
+---
+*条目 E362 · 更新 2026-08-16 · 知识库同步生成物*

package/node_modules/@ohos-agent/pc-adapter/skills/pc-error-atlas/knowledge/errors/E363.md

@@ -0,0 +1,76 @@
+<!-- 本文件由同步脚本自动生成，请勿手改。如需修正请更新知识源数据后重新运行 `npm run sync:kb`。 -->
+
+# E363: Legacy Bash test harness setup failures must not be reported as a passing upstream suite
+
+> **严重度**: 🔴 blocking | **分类**: ohos, portability, shell, false-green, testing-infrastructure | **自动修复**: ❌ | **原则**: [P014](../principles.md#P014)
+
+---
+
+## 错误特征
+
+```
+cp: /tmp/.*Read-only file system
+/bin/bash: bad interpreter
+xargs: Unknown option 'I'
+install: Permission denied
+ASLTS.*PASS\s*:\s*$
+iasl compiler not found.*exit_code=0
+```
+
+## 根因
+
+Legacy upstream Bash harnesses can combine three independent portability assumptions: staging executable tools under hard-coded /tmp, executing transitive helpers through a fixed /bin/bash shebang, and using GNU-only utility flags such as xargs -I. If setup and phase errors use bare exit or are not returned to the top-level process, the harness can exit 0 with no test case executed and an empty PASS/FAIL/Tests summary.
+
+## 验证命令
+
+```bash
+TMPDIR="$PWD/.test-tmp" ASLTS_SKIP_TEMPLATE=yes ASLTS_SKIP_RESULT_COMPARE=yes bash ./aslts.sh -e -u -c constant -m n64 && grep -A12 '^TOTAL:' tests/aslts/tmp/RESULTS/*/Summary
+```
+
+## 解决方案
+
+**writable-temp-explicit-interpreter-fail-fast-positive-summary**：Honor caller-owned TMPDIR and verify it is writable; declare Bash as a reproducible tool dependency; invoke the top-level and transitive scripts through that Bash instead of a system shebang; use mkdir for pure directory creation instead of a policy-blocked install program; replace unsupported parallel dispatch with a portable selected-case loop; return every setup/compile/execute failure explicitly; and require a non-empty structured summary plus a generated artifact before declaring success.
+
+```bash
+conan create 〈外部知识库归档〉 --build=missing
+```
+
+## 回退方案
+
+**evidence-bounded-subset**：If an unrelated upstream phase is not portable, expose an explicit opt-in skip for that phase, run a named deterministic subset, retain independent consumer coverage, and report the exact inventory and selection without claiming the full suite.
+
+```bash
+ASLTS_SKIP_TEMPLATE=yes bash ./aslts.sh -e -u -c constant -m n64
+```
+
+## 🚫 禁止策略
+
+### 🚫 禁止 1
+
+- **模式**：`exit 0.*(iasl compiler not found|bad interpreter|Unknown option)|runner.*exit_code=0.*pass`
+- **原因**：A top-level zero code is insufficient when preparation or transitive dispatch failed before any test produced a result.
+- **后果**：CI records a false upstream-test pass while PASS, FAIL, and Tests are empty.
+
+### 🚫 禁止 2
+
+- **模式**：`ln -s.*(/bin/bash|/usr/bin/env)|mount.*rw.*(/tmp|/bin)`
+- **原因**：A package adaptation must not mutate the device system image to satisfy an upstream test harness.
+- **后果**：The result is non-reproducible, violates isolation, and may affect other queued jobs.
+
+### 🚫 禁止 3
+
+- **模式**：`full.*suite.*pass|1291/1291|100%.*ASLTS`
+- **原因**：Running one named collection and mode is not execution of every ASL source or every ASLTS mode.
+- **后果**：Test coverage is overstated and the B-class evidence is not auditable.
+
+## 涉及软件
+
+Upstream shell test suites on OHOS or other restricted/POSIX environments that stage tools in a global temporary directory, invoke nested Bash scripts by shebang, parallelize with implementation-specific xargs flags, or judge success only from the top-level exit code.
+
+## 相关模式
+
+- **相似模式**：[E253](E253.md)
+- **根因条目（应先修它们）**：[E002](E002.md)、[E201](E201.md)
+
+---
+*条目 E363 · 更新 2026-08-15 · 知识库同步生成物*

package/node_modules/@ohos-agent/pc-adapter/skills/pc-error-atlas/knowledge/errors/E364.md

@@ -0,0 +1,60 @@
+<!-- 本文件由同步脚本自动生成，请勿手改。如需修正请更新知识源数据后重新运行 `npm run sync:kb`。 -->
+
+# E364: Isolate generated MPI wrappers from Worker-local CPPFLAGS
+
+> **严重度**: 🟡 medium | **分类**: relocatable, autoconf, mpi, openharmony, wrapper | **自动修复**: ❌
+
+---
+
+## 错误特征
+
+```
+mpicc contains non-relocatable paths: /storage/Users/currentUser/usr/local
+```
+
+## 根因
+
+MPICH configure copies the active CPPFLAGS into WRAPPER_CPPFLAGS. The OHOS Conan profile adds the Worker-only $HOME/usr/local/include path, so packaging embeds that absolute path in mpicc and the recipe's relocation guard rejects the package after the long build and upstream test run.
+
+## 验证命令
+
+```bash
+Run the production recipe method with a poisoned Worker environment, require CPPFLAGS=-DNDEBUG in the configure command environment, rewrite a clean synthetic wrapper successfully, and reject a wrapper with the Worker-local include path reinserted.
+```
+
+## 解决方案
+
+**recipe-owned-wrapper-flags**：Override CPPFLAGS in the recipe's configure command environment with the minimal target-neutral value required by the package, before configure snapshots WRAPPER_CPPFLAGS. Keep a package-time forbidden-path scan as a fail-closed backstop.
+
+```bash
+Set CPPFLAGS=-DNDEBUG in the isolated MPICH native environment; run py_compile, the wrapper CPPFLAGS poison fixture, Pre-PR contract, independent W4, current-HEAD Review, and exact-current-HEAD CI.
+```
+
+## 回退方案
+
+**structured-wrapper-flag-sanitization**：If target-specific include flags are required, parse the flag vector and retain only paths bound to the package or SDK; do not use substring replacement over the finished script.
+
+## 🚫 禁止策略
+
+### 🚫 禁止 1
+
+- **模式**：`replace\(.*/storage/Users/currentUser/usr/local`
+- **原因**：Post-generation substring deletion can corrupt unrelated arguments and only handles one Worker layout.
+- **后果**：A different Worker prefix or quoted flag spelling can leak into the published wrapper.
+
+### 🚫 禁止 2
+
+- **模式**：`contains non-relocatable paths.*(warn|pass|return)`
+- **原因**：Downgrading the relocation guard publishes a wrapper that depends on the build Worker filesystem.
+- **后果**：Consumers fail after package relocation or resolve unintended user-local headers.
+
+## 涉及软件
+
+Autoconf projects that persist build-time CPPFLAGS or equivalent environment flags into installed compiler wrappers or metadata.
+
+## 相关模式
+
+- **相似模式**：[E236](E236.md)
+
+---
+*条目 E364 · 更新 2026-08-17 · 知识库同步生成物*