Files
warp-engine-client/src/domain/models/SelectedGame.ts
T
mr.zeroandClaude Opus 5 06f3f2a3b1
ci/woodpecker/push/woodpecker Pipeline was successful
ci/woodpecker/tag/woodpecker Pipeline was successful
The store engine moves into the client, and Python goes with it
Reading the catalog, choosing the release that fits this machine, unpacking it,
writing the menu entry and remembering what went where all happen in process now.
There is no interpreter to find, no child process, and no JSON-lines protocol
between the two halves — `PythonEngineProcessRunner`, the runtime locator, the two
engine mappers and the version negotiation are all gone, and with them the one
unchecked cast this codebase had (engine stdout to a typed event).

What that buys a person: on Windows and on a fresh Mac the app simply works. It
used to look for `python3`, `python` and `py -3` and draw a link to python.org
where none answered.

What lands on disk is unchanged, deliberately. `config.json` and `state.json` keep
the shell engine's snake_case shape, its `<scope>:<name>` keys and its file modes,
so a machine whose library was installed by the CLI keeps it — verified against the
Python engine on the same catalog: the same 13-title listing with zero field
differences, byte-identical payloads, identical modes and an identical Info.plist,
and a re-sync over a Python-installed home that writes nothing. Remove, prune,
prune-suppression on a named sync and the v1 state migration were each exercised.

Three things worth knowing about the new code:

  - the zip reader is ~150 lines over `node:zlib`, because Node has none and this
    application has no runtime dependencies. It restores the executable bit from
    each entry's external attributes, without which nothing installed can start,
    and it refuses zip64, unknown compression and paths that escape the
    destination rather than guessing;

  - `SUPPORTED_WARP_ENGINE_VERSIONS` names the engine versions this client is
    written against, checked against the `WarpEngine-Version` header every
    response carries. `selectCatalogDialect` switches over that list exhaustively,
    so adding a version fails the build — type checker and linter both — until
    somebody says what its catalog reads like. An absent header is read as the
    oldest version, which is what an engine before 0.4.0 is;

  - refresh and the language picker are icons at the foot of the side menu now,
    both named for a tooltip and a screen reader, the picker still a real
    `<select>` under its glyph.

The repository is free of Python as well: the Makefile, the CI check and the
release script read package.json and the forge's JSON with Node.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-18 23:36:25 +02:00

58 lines
1.9 KiB
TypeScript

import type { UnavailableReason } from './Game'
/**
* A catalog entry the store can install here, with the release it chose.
*
* `scope` is how the host groups its library — for a desktop that is the catalog
* platform. It is what `state.json` is keyed by (`<scope>:<name>`), so two scopes
* can carry a game of the same name without colliding.
*/
export interface SelectedGame {
readonly name: string
readonly scope: string
readonly platform: string
readonly kind: string
readonly version: string
readonly asset: string
/**
* The catalog-side path, kept because not every asset is a download: an `html`
* build is a hosted directory, and the entry is a link to it.
*/
readonly assetPath: string
readonly title: string
readonly description: string
readonly author: string
readonly imageUrl: string | null
readonly createdAt: string | null
/** `app` for a native archive, `web` for a hosted page. */
readonly mode: string
}
/**
* A title the store offers but this machine cannot install.
*
* A store that hides these is lying about its catalog by omission: "there is
* nothing for your machine" is an answer, and an absent entry is not. Titles the
* store *chooses* not to offer — the wrong status, an `only`/`exclude` list — are
* not here, because that is editorial rather than a limitation of the machine.
*/
export interface UnavailableEntry {
readonly name: string
readonly title: string
readonly platform: string
readonly description: string
readonly author: string
readonly imageUrl: string | null
readonly version: string
readonly reason: UnavailableReason
/** The sentence behind the code, for a tooltip or the log. */
readonly detail: string
}
/** What a survey of the catalog found: installable, why not, and what was skipped. */
export interface CatalogSurvey {
readonly games: readonly SelectedGame[]
readonly skipped: readonly string[]
readonly unavailable: readonly UnavailableEntry[]
}