---
name: v0260-core-wave
description: "2026-07-06 spt-core v0.26.0 published (counter 46) — floor enforcement LIVE (REMOTE-TRUTH core half closed), no adapter floor bump, box update pending operator window"
metadata: 
  node_type: memory
  type: project
  originSessionId: 92f4e8f1-7e75-4907-a410-923bc13d4448
---

**spt-core v0.26.0 published 2026-07-06** (doyle GO, counter 46, tag @1dcfcfa, update-set v46 live).

Adapter-relevant:
- **min_spt_core floor now ENFORCED on adapter add AND update** — the REMOTE-TRUTH core half I filed at the F-030 close is SHIPPED. Decorative/overstated floors now refuse loudly. claude-spt's floor (0.25.0) assessed HONEST (F-030 psyche driver requirement, proven on real 0.25.0) — enforcement-safe, no change. Free v0.13.2-class brick protection (old core + new adapter = refuse, not silent brick). **Follow-up: drop the "update spt-core first" advisory framing from release notes once fleet ≥0.26.0** — the gate says it now. REMOTE-TRUTH adapter legs (D-2 sessions.log adapter field) still arrive separately.
- **Floor ruling: NO forced bump** — bump only when consuming a 0.26.0-only verb. v0.14.1 doesn't. Floor stays 0.25.0.
- **from-stamp fix** (spt-hosted sends stamp endpoint, not cli@NODE) — doyle confirms the parity-close from="perri" mangle fits the E-1 root exactly (spt-hosted sender fell to parent-pid cli@NODE stamping pre-fix). **STANDING ASK: report the next cross-agent exchange's from-stamp result to doyle EITHER WAY post-box-0.26.0; a recurrence = FRESH finding, never folded into E-1.**
- **input-translation: FAILED (<reason>)** now rendered on endpoint list/whoami — translate faults operator-visible without wtrace.
- Also: resume-from-history follows recorded adapter; rc attach auto-reconnect; soft session-end preserves listener address; picker UX.

**Box state: core 0.25.0, adapter v0.14.1. Box → 0.26.0 = operator-timed window** (running daemon hosts perches). Surfaced to operator 2026-07-06.

**Counter 48 (2026-07-06): core v0.28.0 published (JOIN-TRUTH, tag @0639b12, update-set v48).** Adapter impact NONE — no api/manifest/verb change, floor stays 0.27.0 for worker verbs, consumables unchanged. Shipped: NTP multihome + loud-fail + clock-step self-heal in join ceremony clock; `join --verbose` step/offset/NTP-state; interactive join defers elevation until member FOUND. Human-UX only, nothing adapter glue parses. Five-proof HFENDULEAM bounce window unchanged (box still core 0.25 + adapter 0.14.3 pinned); operator bounce now lands ≥0.28.0 presumably.

**Counter 49 (2026-07-07): core v0.29.0 published (LIFECYCLE-TRUTH, Latest on spt-releases, update-set v49 signed+live).** My CC `SPT_INJECT_VERIFY_ECHO` wiring (adapter v0.15.8, [[resume-rebind-wedge]] sibling REQ-INJECT-VERIFY-ECHO) now SELF-ACTIVATES once a session runs 0.29.0 (broker arms Layer-2 inject echo-verify). **Floor ruling: HELD at 0.27.0 — NOT bumped to 0.29.0.** Discipline: bump only when a SHIPPED adapter feature CONSUMES a 0.29.0-only surface; the echo-verify flag is floor-safe by design (inert below, self-activates on deploy), so a bump for it would be dishonest. New 0.29.0 lifecycle surfaces = **adoption candidates** (bump floor when building a consumer): endpoint-survival, rc connect-only, idle-parked delivery, inject-integrity. **Box still on 0.28.0** — echo-verify self-activation + any 0.29.0 surface needs an operator-coordinated core update to 0.29.0 (bounces live agents incl perri). doyle's counter-49 wave verify owns the broker-arms Layer-2 E2E.

Related: [[boundary-rename-v0141]], [[psyche-ephemeral-redesign]], [[resume-rebind-wedge]].