---
name: v0430-published
description: v0.43.0 (counter 77) STALE-ONLINE shell-liveness cut published 2026-07-26 — asset hashes + ledger detail.
metadata: 
  node_type: memory
  type: project
  originSessionId: 600922b5-736a-4dce-be8d-9d89847e08d6
  modified: 2026-07-26T07:23:32.658Z
---

spt v0.43.0 = release counter 77 (monotonic, NOT semver). Published to BigscreenVR/spt-bs-releases 2026-07-26T06:55:11Z, flipped public + repo Latest. The STALE-ONLINE shell-liveness cut (dead shells now read offline; `shell relink` / `shell cmd` recovery works). Tag v0.43.0 == main @ c6fd914 == the PR #77 (`release/v0.43.0`) merge commit. doyle gated it; I signed + published.

**Counter verified, not recalled:** pulled v0.42.0's published `update-set.json` and read its signed metadata — `"version":76` — before signing 77. Do this every cut; the counter is read from published metadata at authoring time and drifts silently otherwise.

**Published asset hashes (ledger):**
- windows `spt-x86_64-windows.exe` sha256 `8839c52870cee7a979d3caf86f3713557fedb5961478ed31bdb49a20409fa58a`
- linux-gnu `spt-x86_64-linux` sha256 `e7b0d74d223b22f6120836015bc1b79cba5f4abd85cc39c8250b021b99a9755f`
- linux-musl `spt-x86_64-linux-musl` sha256 `53984662020d2196b70d57832244d1e0f0c1284b1cc5c02125cc49da5e5aed56`
- docs `spt-docs.tar.gz` sha256 `e284630bb55b53aec5a370f79900adf35b4b8f7bd408178d12501f6a3b22ccc8`
- signing pubkey `54188f127f9c361090c90f85ac072e623d7001b311d25eca0dd5f57ad05e3ec9` (key_id rel-primary-2026 — matches the BUILTIN_RELEASE_KEYS anchor)
- `update-set.json` v77 "0.43.0", platforms x86_64-pc-windows-msvc + x86_64-unknown-linux-gnu + x86_64-unknown-linux-musl (musl is in the set as of this cut)
- https://github.com/BigscreenVR/spt-bs-releases/releases/tag/v0.43.0

Rollout order still CORE FIRST, then adapter (`min_spt_core` is not enforced on acquisition — see [[v0250-published]]). Seed path used: see [[release-seed-machine-env-ruling]].

**Field-verified 2026-07-26, wave CLOSED (doyle).** flynn's alchemy-0 run = PASS end-to-end: list derived offline off a still-poisoned on-disk status=online record, relink admitted (no SHELL_ALREADY_ONLINE), identity/binding/armed-state intact, no spontaneous relaunch. Cursor moved across the daemon restart (gen:seq 48:333→49:49) — ruled SCOPE not gap: first field firing of alchemy REQ-TAG-SCANNER's missed-rows leg (after_predates_window → warn, never silent re-baseline of an armed cursor); byte-identity holds within one daemon generation only. Verdict banked in REQ-HAZARD-SHELL-STALE-ONLINE (PR #79 with todlando's v0.42.0-verdicts + bits-ambiguity-RCA commits). liam's specimen (pid 35464 clean corpse, ~8.5h gap) HELD un-relinked for liam's own return — its cursor datum closes the last thread.