Completes the wave — all six library sources are now pinned.
gog 0.1.0 is published but CANNOT SEE A SINGLE GAME on any machine: the kit's
regSubKeys built its match prefix from the abbreviated HKLM\... key it was
handed, while reg.exe always echoes HKEY_LOCAL_MACHINE\..., so it returned [].
0.1.1 is the first build that works, on plugin-kit 0.3.2.
Verified on .173 against a live host with the PUBLISHED 0.3.2 (clean install),
this plugin unregistered so the host was still on its built-in scanner:
detect present (was absent), scan 1 games (was 0), and the id, title, launch
recipe and metadata all match the built-in scanner exactly.
Parity reports art.hero/logo/header changed, and that is EXPECTED rather than a
loss: this plugin deliberately emits no art, the host's own built-in gog scanner
does not read art from disk either (it attaches cached_art), and a background
pf-art-warmer thread resolves art host-side every 300s for exactly gog and xbox
because the other stores carry their own. Entry ids are byte-identical, so the
warmer repopulates these entries just as it did the scanner's.
reviewedAt stays unset — still the reviewer's to write.
Fortnite finished installing on .173, so the gate could finally run. Its manifest
is now in Manifests\ with bIsIncompleteInstall=False and the folder has real
content (Engine, FortniteGame); disk went 24.6 GB -> 69 GB free, which was the
actual blocker all along.
Parity against the live host, this plugin unregistered so the host was still on
its built-in scanner:
scan: present: 1 games, 0 launcher entries
parity: OK - 1 entries identical
exit: 0
Note the 0 launcher entries: unlike lutris/heroic/steam/playnite, this plugin
publishes no launcher tile. Nothing is wrong - it simply does not implement the
kit's launchers() hook.
minHost 0.25.0 is deliberately conservative. The `epic` launch kind this plugin
emits IS already in v0.24.0 (ecfa7121), and it sends no role/launcher_ui, so a
lower floor is probably correct - but it has only ever been verified against a
main-build host, so the floor is what was actually tested. Too high only delays
availability; too low breaks installs.
platforms is [windows] - it reads %ProgramData%\Epic\EpicGamesLauncher\Data\Manifests.
Still NOT pinned: gog (no hardware yet) and xbox (structurally cannot see
pure-UWP Game Pass titles - see the PR body).
Published and parity-verified. Run against a live host on .21 with this plugin
unregistered, so the host was still on its built-in scanner:
scan: present: 5 games, 1 launcher entries
parity: OK - 5 entries identical (+1 expected steam:big-picture tile)
That box has 10 appmanifests; 5 are real games and the rest are Proton and
redistributable tools the kit's isSteamTool filters. Both sides independently
produced the same 5 - the strongest parity sample of this wave (lutris and heroic
were n=1 each).
minHost 0.25.0 like the others: the launcher tiles need the role/launcher_ui wire,
which no released host has yet.
platforms is [linux, windows] because the kit's steamRoots() handles both (Program
Files + the HKLM InstallPath on win32, POSIX homes otherwise). ONLY THE LINUX ARM
HAS BEEN EXERCISED - the Windows path is untested.
epic, gog and xbox are published too but are deliberately NOT here: none has a
green parity run. .173 has no Epic game installed (Fortnite is an incomplete
download - 83 GB wanted, 24.6 GB free) and no GDK game at all, so there was
nothing for either to reconcile against.
reviewedAt stays unset - still the reviewer's to write.
All three are published and their integrity hashes cross-check against the live
registry (`bun run validate`: 5/5 ok). What is NOT done is the part only a person
can do, so this PR is deliberately RED.
* playnite 0.3.0 -> 0.4.0. The published 0.3.0 emits launch.kind = "command"
for every game, which the security review made operator-only, so on a host
carrying that change it syncs nothing at all. 0.4.0 publishes through the
host-owned `playnite` kind instead, and adds a fullscreen launcher tile.
* lutris 0.1.0 and heroic 0.1.0, both first releases. Parity verified against a
live host on .21 for each (lutris: 1 entry identical; heroic: 1 entry
identical). lutris only works at all on plugin-kit 0.3.1 — the kit's SQLite
reader never opened a database on Linux before that.
minHost is 0.25.0 on all three, NOT the 0.15.0 the older entries carry. Measured
against tag v0.24.0, the latest release: it contains neither 6f07bd94
(role/launcher_ui), nor 8ff2c2e1 (the playnite launch kind), nor 81039581 (the
operator-only command rule). So on a released host today, the currently pinned
playnite 0.3.0 still WORKS and 0.4.0 would not, and lutris/heroic launcher tiles
would be refused. 0.25.0 is the release that carries the wire; minHost is exactly
the field that keeps these entries from being offered before it exists.
verification.reviewedAt is unset on all three — including playnite, whose
2026-07-27 date attested to 0.3.0 and must not ride along to a different build.
The validator requires the field, so this cannot merge until a human reviews each
published tarball and dates it. That is the intended gate, not an oversight: a
merge here ships code to every host that trusts this index, under unom's key.
enricobuehler