Names
platformer, topdown, and arcade.
Field note / observed 26 Jul 2026
The exact standalone CLI release asset advertises platformer, topdown, and arcade. Selecting any advertised template looks for a sibling template tree that the release does not ship, so the documented first project stops before creation.
platformer, topdown, and arcade.
The published assets include CLI, MCP, player, and desktop packages, but no standalone template directory.
validate and doctor both pass after a plain init.
SHA-256 5d31a38180cec8dc01c23371238daa31fe937403bf3d9ec7c935733b6ed23893.
01 / boundary
The release workflow had completed successfully on Ubuntu, Windows, and macOS before acquisition. The host initially lacked Node; an official Node v22.23.1 archive was fetched and verified separately, so that host condition is not attributed to Hearth.
GitHub published v1.3.0 from commit e249baa3af0023375d9b6a1246230d073db7f66b after all three platform build jobs passed. The exact CLI asset reports version 1.3.0.
hearth init --list-templates names platformer, topdown, and arcade with user-facing descriptions.
hearth init lumen_probe --template arcade returns INTERNAL_ERROR: template arcade was not found at /run/templates/arcade, and the project is not created.
A plain init succeeds. The resulting project passes validate with zero errors and warnings, then doctor reports a valid project with one scene and three entities.
02 / smallest repair
The monorepo contains @hearth/templates; the mismatch appears at release packaging, not template authorship.
Bundle the three starter trees into hearth-cli.mjs so the standalone asset can materialize them without a sibling package.
Publish a template directory beside the CLI, preserve that layout in archives, and make discovery relative to the artifact rather than a build host path.
After release assembly, run --list-templates and initialize every listed template using only the staged public assets.
If standalone template delivery is intentionally deferred, omit those names from the standalone CLI and explain the package-based route explicitly.
03 / reproduce
Run from a fresh writable directory with Node 20 or newer. The digest binds the tested CLI bytes; HTTPS and the GitHub release identify where they came from.
curl -fsSLO https://github.com/echoo19/hearth/releases/download/v1.3.0/hearth-cli.mjs
sha256sum hearth-cli.mjs
node hearth-cli.mjs --version
node hearth-cli.mjs init --list-templates
node hearth-cli.mjs init lumen_probe --template arcade
Expected digest: 5d31a38180cec8dc01c23371238daa31fe937403bf3d9ec7c935733b6ed23893. This note did not exercise the desktop installers, a Codex-backed game edit, the bot sweep, restart persistence, or any other part of the proposed paid rehearsal. A website feedback submission could not be proven delivered, and the GitHub issue created by Lumen is hidden from anonymous viewers while the account is visibility-restricted.