Magisk app loses root detection when zygisk_vector is active — SecurityException: Unknown calling package name on launch

Steps to reproduce/复现步骤

1. Install/enable zygisk_vector as a Magisk module
2. Reboot
3. Open the Magisk app — it shows no root, Modules tab greyed out
4. adb shell su -c id still returns uid=0 correctly — shell root is unaffected
5. Disabling zygisk_vector and rebooting restores Magisk app root immediately

Expected behaviour/预期行为

Root should be available upon reboot

Actual behaviour/实际行为

After any change to Vector's state (install, uninstall of manager app, module enable/disable), the next reboot temporarily restores Magisk app root — but a subsequent clean reboot (no further changes) breaks it again.

Ruled out:

Magisk's su policies table has a correct, persistent row for Magisk's own UID (policy=2, allow) — confirmed via magisk.db query, so this isn't a missing/wiped grant
adb shell su -c ls (the fresh-grant-handshake fix suggested for a related manager-app issue) does not resolve it
Not an HMA-OSS scoping conflict — HMA-OSS config correctly includes com.topjohnwu.magisk in extraOppositeAppList with proper applyTemplates: [] override

Xposed Module List/Xposed 模块列表

None active

Root implementation/Root 方案

Magisk 30.7 (Alpha)

System Module List/系统模块列表

HMA-OSS, TrickyStore, AlwaysStrong, zygisk-detach, zygisk-hide, zygisksu, LiveBoot

Vector version/Vector 版本

Vector: v2.2 (3111-0230b11a-JingMatrix-Vector)

Android version/Android 版本

LineageOS 22.2, Android 15, custom 4.19 kernel

Version requirement/版本要求

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

Logs/日志

Relevant log at Magisk app launch:

E GoogleApiManager: java.lang.SecurityException: Unknown calling package name 'com.topjohnwu.magisk'.

followed immediately by VectorZygiskBridge: onTransact: action=GET_BINDER calls for other app UIDs — Magisk's own UID (10200) never appears among them.

No source file or test is named. Reproduce with zygisk_vector enabled and inspect the Magisk launch failure alongside VectorZygiskBridge.onTransact GET_BINDER logs, especially the missing Magisk UID 10200; done means the Magisk app retains root and its Modules tab remains available after a clean reboot.