Eidolon runtime 1.3.1 — 2026-09-16 (sphere sync names what is left to claim)

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, hours after cipher-runtime-20260916. --version 1.3.1. One change over 1.3.0: sphere sync also names what the genesis treasury still holds for the vault (claimable, from the anchor's /claim/instances, status treasury; errors.claimable when the anchor could not say). A genesis sphere not yet claimed has no head and was counted in neither final nor waiting, so a client could only guess that a claim was missing — the Spheres tab of Cipher ≥ 465a8e9 reads the field and shows N to claim. Everything else is 1.3.0: the sphere custody client (sphere list|claim|transfer|import|export|sync|mailbox|queue|burn|reissue-key|verify|trust), Escrow Nexus (escrow deposit|list|show|retrieve|verify|delete), 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 75c42eb (public tree v1.3.0), plus the owner's uncommitted edits in the two optional viewer modules the spec lists as hidden imports (src/holo/avatar_system/threejs_renderer.py, src/blockchain/avatar_visualization.py — reachable only through the ceremony's viewer button; the same edits were in the tree when cipher-runtime-20260916 was frozen).

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	541ea3d2c98b8b32a4700b2ac40937b4add10fff199b8d55efb7666e270adf69
cipher-runtime.exe (Windows x64)	Windows 11, CPython 3.12.14	ac5ad809712b503754f42dd5d04ca212bafe7f1c7243bd7c90d9ca5f2243b309

Verified: Windows — --version → 1.3.1, sphere trust (pinned issuer and root), sphere sync against the production anchor on the owner's vault → final: 8, waiting: 0, claimable: [] (the field is present), sphere queue → count: 0, sphere burn without --confirm → error_code: confirmation_required and nothing signed. 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.