Eidolon runtime 1.3.2 — 2026-09-16 (sphere status carries the template's appearance)

Frozen Eidolon runtime consumed by scripts/bundle-eidolon-runtime.mjs, pinned by name and SHA-256. Not a Cipher release: install Cipher from the v* releases.

Why a new runtime after cipher-runtime-20260916b. --version 1.3.2. One change over 1.3.1: every sphere status (sphere list / sync / claim) carries a visual field — what the revealed template says of the sphere's appearance: theme, manifestation, essence and the cosmic signature (shell_pattern, quantum_glow, reality_particles, cosmic_aura), short strings, null before the sphere is claimed or when the template has no appearance field. Nothing else of the template leaves by that path (the narrative, rewards and cycles stay in the file). The Spheres tab of Cipher ≥ 7e28006 reads it to draw each sphere as a WebGL orb (theme shell and glow, rarity aura, form per manifestation); with 1.3.1 or older every orb falls back to the void theme. Everything else is 1.3.1: the sphere custody client (sphere list|claim|transfer|import|export|sync|mailbox|queue|burn|reissue-key|verify|trust, claimable on sync), Escrow Nexus (escrow deposit|list|show|retrieve|verify|delete, a failed read of the document now reported as invalid_input with the OS error code, a failed write as store), the genesis trust root of 2026-09-16 compiled in (sphere trust → issuer 6dad3cb1…3e31f8, genesis root 89fb26b1…f0053e, anchor eidolon-anchor-1). Built from the private core at d96fb3a (public tree v1.3.0), with the same uncommitted owner edits in the two optional viewer modules as the two previous lots.

Asset	Built on	SHA-256
cipher-runtime (Linux x86_64)	WSL Ubuntu 22.04.5, glibc 2.35 (measured floor 2.35), CPython 3.10.12	a3ce57e1e2998df500a32fcfa88efb24a24f64d4a1d5de621c161cec9465e876
cipher-runtime.exe (Windows x64)	Windows 11, CPython 3.12.14	b960b35fd61599efb8dca4109776f4caf6af602ead20d56929eca5c51078d13c

Verified: Windows — --version → 1.3.2, sphere trust (pinned issuer and root), sphere list and escrow list on the test-vector vault in a throwaway data dir (empty, well-formed answers), escrow list --help; the visual field is covered by the core's private suite (tests/private/test_sphere_wallet.py: a claimed RARE template yields the four keys, a COMMON one its theme only, no template → null). Linux — the build script's own checks (--version, keybundle/ceremony --help, sphere trust, escrow list --help, requests/urllib3/certifi present, glibc floor 2.35).

Verify a download with sha256sum -c SHA256SUMS.