Games installed from an install link get a row on the game page (where it came from, the installed version) with Check for updates, and the same entry in the page's menu: it asks the link now instead of waiting for the 6-hourly check. Manifests that named no version (e.g. an app's first release) were never checked; the installed APK's own versionName (from the analysis) is now the version to compare with, in the automatic check, the button and frameport link-updates.
Sections now run from what most users need to what only some need:
Updates, Installing, Library folders, Appearance, Data, Problems and
feedback, Install links, Tools, This PC, About, Uninstall. Updates gains a
Games part: game recipes from GitHub (moved from Data) and the new
"Check games from install links for new versions" switch with its last
check and Check now. Inside sections the common options come first
(Installing: parallel uploads and video before keep-copies; Updates: dev
build last; Appearance: language first when a translation exists).
The demo manifest (site + built-in copy) names version 1.0.0 as an example;
the demo link is still never fetched or checked (test).
A manifest may name its build's version (top-level "version" or
"frameport": {"version"}). FramePort keeps it with the game's link record
and, at start (at most every 6 h), fetches remembered web manifests again;
a newer version marks the game link_update. The Library bar and the game
page offer to download and install it (one confirmation, same download path
as a first install, a name the user gave is kept). CLI: frameport
link-updates [--install]. Docs: INSTALL_BUTTON.md.
spoopyghosty0