v1.0.2 - Weekly quiet cron deployment

Weekly quiet synchronization: deployment and documentation

This release adds a ready-to-install system cron example and explains how to
deploy the script for automatic weekly execution.

What changed

• Added gitea-github-sync.cron: every Monday at 03:00, as root, in --apply-quiet mode.
• Added installation, permissions, timezone and log-verification instructions.
• Added CHANGELOG.md explaining the changes and their motivation.
• Included the existing GPL-3.0-only license in the downloadable bundle.

Why

The original server had an older installed script without quiet mode and no
weekly cron entry. Deploying the published version and installing the schedule
resolved these deployment gaps. This release makes that setup reusable.

The Bash script is unchanged from v1.0.1. --apply-quiet was already available;
this release does not introduce it again. The cron file and documentation are new.

Installation

Keep your existing configuration and tokens. From the extracted bundle:

sudo install -o root -g root -m 755 ./gitea-github-sync.sh /usr/local/bin/gitea-github-sync.sh
sudo install -o root -g root -m 644 ./gitea-github-sync.cron /etc/cron.d/gitea-github-sync

Check for an equivalent existing cron job before installing. The cron service
must be active. Schedule times follow the server timezone. The installation does
not trigger an immediate synchronization. Large accounts can take hours to finish.

Inspect /var/log/gitea-github-sync.log (or QUIET_LOG_FILE) for the worker's final
exit_status=0. The background launcher's success is not the synchronization result.

Validation: unchanged script verified against v1.0.1, Bash syntax checked, cron
schedule/line endings validated. The deployed cron service, files, dependencies
and read-only API access were checked; a scheduled run was not manually triggered.