One release repository reduces ambiguity
If the website, GitHub Release assets, and desktop updater all point at different places, users cannot tell which version is real. The release repository fixes that by becoming the single factual source for installable artifacts.
This lets contextgo.io render download information from the same place the desktop client checks for updates.
What belongs in the release repository
Build artifacts, checksums, manifests, and release notes belong there. Long-form docs, blog posts, and marketing pages do not. Those should stay on the website side.