[Zhanfg]

Objective

One PatchNest runtime with two deployment backends:

1. Kernel Integrated / AK3: native Kbuild port (currently only status ioctl, NOT KPM loading).
2. Image Patched / standalone module: existing kpimg/kptools foundation (unified patched ABI adapter pending).

Implemented

• Shared, versioned ABI v1 header and a read-only native /dev/patchnest status ioctl; capability mask remains 0, NOT_READY by design.
• Native Kconfig/Makefile development port, not yet integrated into actual device source tree.
• Read-only patchnest-status CLI that verifies native ABI rather than guessing from root.
• KPM loader refactoring: serialized load publication; kernel spinlock-guarded module registry; callback lifetime pins; return -EBUSY when control/event callback is still active; bounded event snapshot; per-call ctl0 arguments.
• Bounded ELF header, section, memory budget, symbol strings and relocation index/offset validation, plus missing callback guards.
• GCC/Clang host ABI test and concurrent pthread lifetime tests; current ARM64 kpimg/kptools build CI.
• Companion manager PatchNest PR #12: read-only dual-backend detection and WebUI label with Vitest tests.

Hard blockers — draft / do not flash

This is not a completed KPM runtime and cannot be shipped as AK3 or a reliable patched ZIP.

• The current callback reference scheme does NOT encompass every arbitrary KPM inline hook or asynchronous task. Module executable lifetime may still be unsafe on unloading; Issue #10 remains open.
• Need comprehensive ELF fuzzing/relocation validation (Issue [P0][ELF Parser] 未验证 e_shstrndx、sh_name 与 sh_link 边界，恶意 KPM 可触发内核越界读写 #13), other auth/security open issues [P0][AuthZ] 已授权 UID 无需超级密钥即可授权其他 UID、关闭安全模式并改写全局隐藏策略 #6–[RCU Leak] 查询不存在的 KPM 时直接返回，未释放 rcu_read_lock() #15, and persistent crash safety boot-counter correction.
• No target ARM64 kernel in-tree compile, AK3 pack/unpack/boot verification or physical device boot + recovery regression.
• Patched adapter with shared ABI and common KPM lifecycle still missing.
• Do not change main, historical releases, tags or public install links.

See docs/PATCHNEST_DUAL_BACKEND.md for the exact acceptance gates.

2026-10-14 continuation: native integration workflow

• Added ports/linux-native/integrate.sh: defaults to dry-run; explicit opt-in to stage Kconfig/Makefile/driver into an existing kernel tree; repeatable without duplicate stanzas; refuses conflicting driver or ABI rather than overwriting.
• Added host integration smoke tests and CI checks for dry-run, conflict rejection, and idempotence.
• This is still status-only. A functioning KPM runtime has not been linked into an actual OnePlus kernel, and no AK3 has been built or device-tested from this PR. Do not merge until true kernel and boot gates pass.