jackwener 84a3108df3 review: stop overstating the trade-off and condition the init warning ... Per codex review on PR #64: 1. src/cli/init.rs warning was unconditional but the wording presumed the user had taken the ad-hoc re-sign path. If init goes through the tier 2 path (Apple-signed WeChat + GUI Terminal + Developer Tools TCC authorization), the warning would mis-fire. Reword conditionally and point to the GitHub URL of the doc instead of a relative path that release-binary / npm-installed users won't have on disk. 2. docs/macos-permission-guide.md §六 and the matching README callout said "restoring official WeChat = giving up macOS memory-scan". This contradicts the same guide's §一 实测表 which shows "Apple 签名 + 本机 Terminal sudo = ✅". Restoring the official signature only gives up the default re-sign path; the local-Terminal + Developer-Tools route still works on Apple-signed WeChat. Only SSH + Apple-signed WeChat actually requires re-signing.		2026-05-15 15:23:23 +08:00
..
macos-3x-vs-4x-decryption-guide.md	fix: replace nonexistent scan_keys.js with actual tools in quickstart	2026-03-05 23:26:55 +08:00
macos-permission-guide.md	review: stop overstating the trade-off and condition the init warning	2026-05-15 15:23:23 +08:00