Repository Maintenance Rule

Keep Forgejo main, the Pi4 service/runtime clone at /home/mehdifarah/riptide-src, and the live RG deployment notes current as work happens. When a session changes runtime behavior, launcher metadata, assets, or issue state:

• Commit the repo changes and push them to Forgejo before closing the task.
• Fast-forward /home/mehdifarah/riptide-src when the change should be reflected in the Pi runtime clone.
• Record deployed RG paths, verification results, and current issue status in docs or issue notes.
• Update Forgejo issues as work is opened, investigated, fixed, verified, or intentionally deferred.
• Continue to avoid autonomous EmulationStation restarts, reboots, or ES process kills. Stop at file verification and ask MjF to refresh ES manually.