v1.0.5

What's Changed

• Fixed the package's Mole pre-install. The postinstall script fetched Mole's installer from mole.fit/install.sh, which returns 404, so Mole was never pre-staged. It now uses the same GitHub URL as the in-app installer and writes its log to /Library/Logs/MacMoleManager-mole-install.log (it previously went to /tmp, which is cleared on reboot). Mole's installer needs admin access to write /usr/local/bin, so on a standard-user Mac the pre-install is still expected to fall through to the in-app "Install Mole" flow with Privileges.
• One-click repair for a broken Mole install. If mole is present but the support files it loads from ~/.config/mole are missing (deleted by hand, removed by a cleanup tool, or never created for that user), the app previously showed a raw shell error with no way forward. It now explains the problem and offers a "Reinstall Mole" button, including when the error comes from "Check for Mole Updates". The Homebrew repair button now works from that path too.
• PPPC template: pre-approve System Events. Mole triggers a "MacMoleManager wants to control System Events" prompt during Clean, and the template only covered Finder. Packaging/PPPC-template.mobileconfig now grants both.
• PPPC template: removed the deprecated Allowed key. Each entry carried both Allowed and Authorization, and macOS rejects a payload with both ("the key 'Authorization and Allowed' is not allowed"). Only Authorization remains.
• Packaging docs. The PPPC template and Packaging/README.md now note that Mosyle's Security & Privacy form keeps only one Apple Events receiver per app, so this profile should be uploaded under Certificates / Custom Profiles.

Full Changelog: v1.0.4...v1.0.5