v1.0.1

New Features

• None.

Improvements

• Member data is no longer stored in the autoloaded cron option. Queued Telegram deliveries now keep their payload in a randomized, non-autoloaded transient and pass only an opaque ticket as the cron argument, so phone numbers, names, and message bodies are not loaded on every request and are not displayed by cron-inspection plugins. Payloads are deleted on success, on abandonment after the retry cap, on non-retryable rejection, and on uninstall. Events queued by 1.0.0 are still accepted, so no migration is required.
• Per-chat pacing now enforces a real interval. The previous comparison only deferred deliveries queued within the same second; the queue now spaces messages to one every four seconds per chat, roughly 15 per minute, staying under Telegram's per-group limit.
• The Telegram bot token settings sanitizer only inspects the clear-token checkbox inside a nonce-verified settings save, so an unrelated option update in an admin request can no longer blank the stored credential.
• Uninstall removes queued delivery payloads, pacing markers, and dedupe markers in addition to plugin options.
• Releases now publish explicit notes from release-notes/<version>.md, along with a SHA-256 checksum and a GitHub build provenance attestation for the plugin ZIP.

Bug Fixes

• Sending an admin test message with a malformed bot token now reports the format error instead of silently testing the previously saved token and reporting success.