mirror of
https://github.com/morluto/rea
synced 2026-10-26 06:16:17 -04:00
Hasan Zayni
39aca92239
When Smart App Control or an App Control policy refuses rea-windows-x64.node, the loader reported the failure as the artifact stage. Doctor and provider diagnostics then told the user to restore or rebuild the native files, although their version and SHA-256 had already matched the package manifest. The loader now tags a failure of the module load itself, after the manifest and digest checks pass, as the load stage. The reason keeps the Windows error text and says that restoring the file cannot help, that Ghidra and JADX need the native controls, that rea setup can still register clients, and that REA must run where policy allows the file or the maintainers can be asked about a signed build. Readiness keeps the documented runtime_missing code for unloadable artifacts. Setup does not depend on the native controls: with the addon unavailable, the published 6.7.0 CLI still planned and applied the claude_code registration, so no setup gate is changed. Fixes #5723