0.3.0 teaches the provider to report where a game is installed. Each exported
entry now carries `detect: { install_dir }` when Playnite knows one, which is
what lets the host recognize a title's process after Playnite's launcher hands
off and exits — the case where the host would otherwise lose the game the
moment the shim returns, and end the session with it.
The published delta is exactly that, and nothing else:
* `installDir` added to the exported-game schema (nullable, defaults null),
threaded into the entry as `detect.install_dir` when non-blank.
* `@punktfunk/plugin-kit` ^0.1.4 -> ^0.2.0.
* The version bump, embedded in both bundles.
The console UI rebuilt because plugin-kit moved, but did not change: the diff
against 0.2.0's chunk is minifier identifier churn (`Rt`->`kt`, `ar`->`lr`)
with zero prose added or removed, so there is no new user-visible text and no
new behaviour. Fonts and CSS are byte-identical.
No new outbound hosts. Every absolute URL in the tarball is a schema/XML
namespace, the plugin's own homepage and registry, or an effect/react error-doc
link — no telemetry, no beaconing. No install lifecycle scripts (`prepublishOnly`
is author-side and unchanged). No `eval`, `new Function`, or `child_process` in
any bundle.
minHost stays 0.15.0. The new `detect` key is additive and optional on the host
side (`#[serde(default)]`, and the host denies no unknown fields), so 0.3.0 on a
pre-`detect` host simply behaves like 0.2.0 rather than failing to ingest.
Integrity was fetched from the registry and independently recomputed from the
downloaded tarball; both agree.
Both entries were stale — the index still pinned rom-manager 0.3.1 and
playnite 0.1.1 while the registry had moved on.
rom-manager 0.3.2 is a bug-fix release: the API encoded absent optional fields
as `null`, which the UI's own decoder then rejected, so the Overview page broke
on a never-synced host and the Emulators page's Detect button broke on any box
with an emulator installed. The published delta is exactly that fix plus the
version bump — no new files, no new outbound hosts.
playnite 0.2.0 is a ground-up rewrite onto @punktfunk/plugin-kit: three
workspaces, a three-page console UI, per-game include/exclude overrides, and an
allow-listed cover-art proxy. Behaviour that matters is preserved verbatim — the
ingest inbox is still read first, the art modes are unchanged, and launches
still hand back to Playnite. The bundled C# exporter is untouched (same wire
schema), so an installed .pext keeps working.
Also: playnite's card icon now matches the icon the plugin registers for its own
console nav entry (`library-big`), and both descriptions mention the console UI.
minHost stays 0.15.0 for both — neither release needs anything newer from the
host than the plugin-UI surface and the ingest inbox already provide.
The previous key was pasted into unom/punktfunk's secret store rather than
this one. Gitea secrets don't cross repos and can't be read back, so that
key was unusable here and is abandoned; INDEX_SIGNING_KEY on THIS repo now
holds the private half of the key pinned below.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The bootstrap key generated during implementation was lost with its scratch
directory. Nothing shipped pinning it, so this is a straight replacement of
slot 0 rather than a rotation — the second slot stays reserved for a real one.
The private half now lives only in the INDEX_SIGNING_KEY secret, so CI is the
only thing that can sign. This push is what makes it do so: the committed
signature is still the old key's, and the verify self-check will fail loudly
if the secret does not match the public key pinned here.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed locally with the key whose public half the host pins. ed25519 is
deterministic, so the publish workflow re-signing this exact document with
the same key produces byte-identical output — this is the bootstrap for a
repo whose CI secret is not yet configured, not a parallel signing path.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
enricobuehler
