unom/punktfunk-plugin-index
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

pin: playnite 0.4.0, and add lutris + heroic + steam + epic + gog #4

Merged
enricobuehler merged 4 commits from pin/launcher-tile-wave into main 2026-08-08 01:32:39 +00:00
Conversation 0 Commits 4 Files Changed 1
+101 -12
enricobuehler commented 2026-08-07 23:09:36 +00:00
Owner
Copy Link
Copy Source

Ready to merge except for one thing: verification.reviewedAt is unset on all six new/changed entries and the validator requires it. Set those six dates and validate goes green. That field asserts a human read those tarballs — I built them, so it is not mine to write.

What changed

entry change parity on a live host sample
playnite 0.3.0 → 0.4.0 n/a (not a scanner port) —
steam new, 0.1.0 ✅ OK — 5 entries identical 5 games
lutris new, 0.1.0 ✅ OK — 1 entries identical 1 game
heroic new, 0.1.0 ✅ OK — 1 entries identical 1 of 89 owned
epic new, 0.1.0 ✅ OK — 1 entries identical 1 game (Fortnite)
gog new, 0.1.1 ✅ id/title/launch/meta identical — art diff explained below 1 game

minHost is 0.25.0 on all six — now confirmed correct, since v0.25.0 is tagged and it is the first release containing role/launcher_ui (6f07bd94), the playnite launch kind (8ff2c2e1), and the operator-only command rule (81039581). v0.24.0 has none of them, so pinning lower would break released-host users.

Every parity run was made with the plugin unregistered, so the host was still on its built-in scanner — the comparison is real, not self-referential.

gog is 0.1.1, not 0.1.0, and why its art diff is not a regression

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 [] always. Fixed in plugin-kit 0.3.2 (punktfunk#107); 0.1.1 is the first working build. Verified against the published kit on hardware: detect: present (was absent), scan: 1 games (was 0).

Parity reports art.hero/logo/header: true → false. That is expected:

  • this plugin deliberately emits no art;
  • the host's own built-in gog scanner doesn't read art from disk either — it attaches cached_art(&id);
  • a background pf-art-warmer thread resolves art host-side every 300 s for exactly gog and xbox, because "Other stores carry their own art (Steam CDN template, Heroic CDN URLs, Lutris data: URLs, custom user URLs) and are skipped";
  • entry ids are byte-identical (gog:<product id>), which is what the store claim exists to preserve — so the warmer repopulates these entries exactly as it did the scanner's.

The baseline was captured from a host whose art cache was already warm. Everything parity compares that the plugin actually owns — id, title, launch recipe, role, metadata — matches exactly.

Still NOT included: xbox

Published at 0.1.0, deliberately unpinned. It is not merely untested — it is structurally unable to see a typical Game Pass library. Forza Horizon 3, installed via the Xbox app, is a pure-UWP package (Microsoft.OpusPG) under WindowsApps with no MicrosoftGame.config — and that file is the only marker both this plugin and the host's built-in xbox.rs key on. Neither can see it, which is why the built-in Xbox scanner has never appeared to work.

It cannot be fixed inside the plugin: %ProgramData%\Microsoft\Windows\AppRepository\Packages throws UnauthorizedAccessException for NT AUTHORITY\LocalService (the runner principal), while the host service as LocalSystem reads all 348 entries. Pure-UWP discovery needs exactly that enumeration, so it needs a host-side path first.

Integrity — cross-checked, not assumed

checking 8 pinned package(s) against their registries...
  ok  @punktfunk/plugin-heroic@0.1.0      integrity matches registry
  ok  @punktfunk/plugin-virtualhere@0.1.0 integrity matches registry
  ok  @punktfunk/plugin-lutris@0.1.0      integrity matches registry
  ok  @punktfunk/plugin-steam@0.1.0       integrity matches registry
  ok  @punktfunk/plugin-epic@0.1.0        integrity matches registry
  ok  @punktfunk/plugin-gog@0.1.1         integrity matches registry
  ok  @punktfunk/plugin-playnite@0.4.0    integrity matches registry
  ok  @punktfunk/plugin-rom-manager@0.3.2 integrity matches registry

OK: v1/index.json is valid -- 8 plugin(s), 0 security advisory(ies).

Known limits, stated rather than buried

  • Four of the five parity runs were n=1. Only steam's was n=5.
  • steam's platforms includes windows, but only the Linux arm was exercised.
  • epic publishes no launcher tile — it doesn't implement the kit's launchers() hook.
  • Art is compared by presence, not value, so covers still want a by-eye check.
  • rom-manager's pin is stale — 0.3.2 here, 0.4.0 on the registry. Pre-existing, untouched by this PR.

To merge

Set verification.reviewedAt on the six new/changed entries after working the checklist against each published tarball. bun run validate turns green immediately.

> **Ready to merge except for one thing:** `verification.reviewedAt` is unset on all six new/changed entries and the validator requires it. Set those six dates and `validate` goes green. That field asserts a human read those tarballs — I built them, so it is not mine to write. ## What changed | entry | change | parity on a live host | sample | |---|---|---|---| | **playnite** | `0.3.0` → **`0.4.0`** | n/a (not a scanner port) | — | | **steam** | new, **`0.1.0`** | ✅ `OK — 5 entries identical` | **5 games** | | **lutris** | new, **`0.1.0`** | ✅ `OK — 1 entries identical` | 1 game | | **heroic** | new, **`0.1.0`** | ✅ `OK — 1 entries identical` | 1 of 89 owned | | **epic** | new, **`0.1.0`** | ✅ `OK — 1 entries identical` | 1 game (Fortnite) | | **gog** | new, **`0.1.1`** | ✅ id/title/launch/meta identical — art diff explained below | 1 game | `minHost` is **`0.25.0`** on all six — **now confirmed correct**, since `v0.25.0` is tagged and it is the first release containing `role`/`launcher_ui` (`6f07bd94`), the `playnite` launch kind (`8ff2c2e1`), and the operator-only `command` rule (`81039581`). `v0.24.0` has none of them, so pinning lower would break released-host users. Every parity run was made with the plugin **unregistered**, so the host was still on its built-in scanner — the comparison is real, not self-referential. ## gog is 0.1.1, not 0.1.0, and why its art diff is not a regression **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 `[]` always. Fixed in plugin-kit **0.3.2** (punktfunk#107); 0.1.1 is the first working build. Verified against the *published* kit on hardware: `detect: present` (was absent), `scan: 1 games` (was 0). Parity reports `art.hero/logo/header: true → false`. That is **expected**: - this plugin deliberately emits no art; - the host's own built-in gog scanner doesn't read art from disk either — it attaches `cached_art(&id)`; - a background `pf-art-warmer` thread resolves art **host-side** every 300 s for exactly `gog` and `xbox`, because *"Other stores carry their own art (Steam CDN template, Heroic CDN URLs, Lutris data: URLs, custom user URLs) and are skipped"*; - entry ids are byte-identical (`gog:<product id>`), which is what the store claim exists to preserve — so the warmer repopulates these entries exactly as it did the scanner's. The baseline was captured from a host whose art cache was already warm. Everything parity compares that the plugin actually owns — id, title, launch recipe, role, metadata — matches exactly. ## Still NOT included: xbox Published at `0.1.0`, deliberately unpinned. It is not merely untested — it is **structurally unable to see a typical Game Pass library**. Forza Horizon 3, installed via the Xbox app, is a pure-UWP package (`Microsoft.OpusPG`) under `WindowsApps` with **no `MicrosoftGame.config`** — and that file is the only marker both this plugin *and* the host's built-in `xbox.rs` key on. Neither can see it, which is why the built-in Xbox scanner has never appeared to work. It cannot be fixed inside the plugin: `%ProgramData%\Microsoft\Windows\AppRepository\Packages` throws `UnauthorizedAccessException` for `NT AUTHORITY\LocalService` (the runner principal), while the host service as LocalSystem reads all 348 entries. Pure-UWP discovery needs exactly that enumeration, so it needs a host-side path first. ## Integrity — cross-checked, not assumed ``` checking 8 pinned package(s) against their registries... ok @punktfunk/plugin-heroic@0.1.0 integrity matches registry ok @punktfunk/plugin-virtualhere@0.1.0 integrity matches registry ok @punktfunk/plugin-lutris@0.1.0 integrity matches registry ok @punktfunk/plugin-steam@0.1.0 integrity matches registry ok @punktfunk/plugin-epic@0.1.0 integrity matches registry ok @punktfunk/plugin-gog@0.1.1 integrity matches registry ok @punktfunk/plugin-playnite@0.4.0 integrity matches registry ok @punktfunk/plugin-rom-manager@0.3.2 integrity matches registry OK: v1/index.json is valid -- 8 plugin(s), 0 security advisory(ies). ``` ## Known limits, stated rather than buried - **Four of the five parity runs were n=1.** Only steam's was n=5. - **steam's `platforms` includes `windows`, but only the Linux arm was exercised.** - **epic publishes no launcher tile** — it doesn't implement the kit's `launchers()` hook. - Art is compared by presence, not value, so covers still want a by-eye check. - **`rom-manager`'s pin is stale** — `0.3.2` here, `0.4.0` on the registry. Pre-existing, untouched by this PR. ## To merge Set `verification.reviewedAt` on the six new/changed entries after working the checklist against each published tarball. `bun run validate` turns green immediately.
enricobuehler added 1 commit 2026-08-07 23:09:38 +00:00
pin: playnite 0.4.0, and add lutris + heroic 0.1.0
validate / validate (pull_request) Failing after 19s
Details
f1148cf87f 
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 added 1 commit 2026-08-07 23:42:55 +00:00
pin: add steam 0.1.0
validate / validate (pull_request) Failing after 18s
Details
96f876940b 
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.
enricobuehler changed title from pin: playnite 0.4.0, and add lutris + heroic 0.1.0 to pin: playnite 0.4.0, and add lutris + heroic + steam 0.1.0 2026-08-07 23:43:18 +00:00
enricobuehler added 1 commit 2026-08-08 00:04:49 +00:00
pin: add epic 0.1.0
validate / validate (pull_request) Failing after 10s
Details
2c4c2bb614 
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).
enricobuehler changed title from pin: playnite 0.4.0, and add lutris + heroic + steam 0.1.0 to pin: playnite 0.4.0, and add lutris + heroic + steam + epic 0.1.0 2026-08-08 00:05:17 +00:00
enricobuehler added 1 commit 2026-08-08 01:30:58 +00:00
pin: add gog 0.1.1
validate / validate (pull_request) Failing after 16s
Details
8c3e657641 
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.
enricobuehler changed title from pin: playnite 0.4.0, and add lutris + heroic + steam + epic 0.1.0 to pin: playnite 0.4.0, and add lutris + heroic + steam + epic + gog 2026-08-08 01:31:25 +00:00
enricobuehler merged commit 63db78a2c8 into main 2026-08-08 01:32:39 +00:00
enricobuehler deleted branch pin/launcher-tile-wave 2026-08-08 01:32:42 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
enricobuehler (Enrico Bühler)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unom/punktfunk-plugin-index#4