punktfunk-plugin-index

4 Commits

Author	SHA1	Message	Date
enricobuehler	34ccacd07e	chore(index): pin rom-manager 0.3.2 and playnite 0.2.0 validate / validate (pull_request) Successful in 7s Details 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.	2026-07-21 00:06:50 +02:00
enricobuehlerandClaude Fable 5	05e772fedd	chore(index): repin to the signing key held in this repo's secret publish / publish (push) Successful in 26s Details 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>	2026-07-20 23:05:39 +02:00
enricobuehlerandClaude Fable 5	575ea1a371	chore(index): repin to the operator-held signing key publish / publish (push) Failing after 18s Details 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>	2026-07-20 22:57:38 +02:00
enricobuehlerandClaude Fable 5	ce8b13c52b	chore(index): bootstrap signature for the seed catalog 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>	2026-07-20 20:28:08 +02:00