No injection after a KernelSU emulated soft reboot spawns a duplicate daemon

Steps to reproduce/复现步骤

Install the latest version of the Vector module on a Redmi K80 Pro (HyperOS + Zygisk Next + KSU jailbreak environment).

Soft reboot the device.

In the license manager, click the "Action" / "Open" button for the LSPosed module.

Observe that the interface redirects to a Shell warning or becomes unresponsive, and the test module cannot be hooked.

Expected behaviour/预期行为

Correct startup and hooking
The v2.1 version of vector (vector-v2.1-3076 HSSkyBoy version) runs normally.

Actual behaviour/实际行为

Unable to start vector and unable to perform hooking

Xposed Module List/Xposed 模块列表

Module unrelated

Root implementation/Root 方案

Root access was gained by disabling SELinux through a Qualcomm 8E series vulnerability, followed by KSU entering jailbreak mode.

System Module List/系统模块列表

Vector v2.2 3080-88f8e1fa
Zygisk-next-780-9d7024c-release

Vector version/Vector 版本

Vector v2.2 3080-88f8e1fa

Android version/Android 版本

16 - xiaomi HyperOS 3

Version requirement/版本要求

• I am using the latest debug build from GitHub Actions./我正在使用 GitHub Actions 中最新的调试版本。

Logs/日志

locat-log.txt

Start with the attached locat-log.txt and reproduce the KernelSU soft reboot on the listed Android and Vector versions. Trace the startup sequence around the duplicate daemon, then verify that the Action/Open flow starts normally and the test module can be hooked after reboot.