# FIELD-TRUTH W0 re-verification — 2026-07-27

Core: `3d9ec73a834bdbbb18e1287d5021dce82c534faf` (later than required `cc3a054`).
Installed `omp-spt` remained pinned at `0.3.29`; `0.3.30` was not applied or bounced. Each item ran in its own worktree and isolated `SPT_HOME`. No suites and no source fixes.

## 1. omp-spt F-032 — shutdown leaves harness/listener alive

**Verdict: ABSENT.** Exact core binary reported `spt 0.44.0`; installed adapter reported `0.3.29`.

Evidence lines:

```text
ENDPOINT_RUN:w0f032-target adapter=omp-spt session=21e6971468c162d6 pid=44572
SHUTDOWN:w0f032-target (Active -> Suspended)
broker_rows_for_target on return: []
broker_rows_for_target after 3s: []
broker_rows_for_target after 52s: []
original target process identities alive on return/3s/52s: []
replacement command lines containing w0f032-target: []
endpoint projection: address=null ready=false alive=false
```

The live precondition was a real 14-process job-object tree:

```text
44572 omp-spt.exe -> 17440 omp.exe -> 18336 bun.exe -> 22332 spt.exe api ... listen w0f032-target
```

Sibling/control: an independently launched omp-spt endpoint established the same live topology; shutdown removed its broker row and complete PID+exe+command-line descendant identity. Bare PID reuse was ignored; process identity and command line were checked.

**W1 ownership:** none. Close this reported survivor shape with the process/broker evidence above; no fix is justified.

## 2. F-034 shape 1 — dead relay retains `ONLINE - HARNESS ONLY`

**Verdict: PRESENT.** Corrected rerun used a fresh isolated `CARGO_TARGET_DIR`; binary reported `spt 0.44.0` (SHA-256 prefix `00e15f`). The earlier stale `0.43.0` run was discarded.

Evidence lines:

```text
relay PID 38764 killed at 2026-07-27T06:21:01Z
owner PID 12156 remained live
at 2026-07-27T06:23:29Z info.json: pid=38764 status=online
endpoint-list JSON: ready=true alive=true address=127.0.0.1:57709
TCP 127.0.0.1:57709 reachable=false
human list: f034-victim ... live_agent ONLINE - HARNESS ONLY
```

Sibling/control:

```text
live sibling relay PID 44892; socket 127.0.0.1:57773 reachable=true
send -> SENT; relay received the EVENT
clean sibling endpoint stop -> status=offline ready=false alive=false; human list OFFLINE
```

**W1 ownership:** fix relay-death convergence. A dead/unreachable harness relay must clear its ready/address/liveness projection and cannot remain `ONLINE - HARNESS ONLY` merely because the owner parent is alive.

## 3. F-034 shape 2 — successful `run --create` retains suspended rest state

**Verdict: PRESENT.** Exact isolated binary reported `spt 0.44.0`.

Evidence lines:

```text
endpoint stop restshape2 -> STOPPED:restshape2
raw before create: status=offline rest_state=suspended session_id=5c93255098571bf7
endpoint run --adapter dummyharness --id restshape2 --create --start
ENDPOINT_RUN:restshape2 adapter=dummyharness session=714260b31d440df3 pid=24176
raw after successful bind: status=online session_id=714260b31d440df3 rest_state=suspended
```

Independent repeat:

```text
new session_id=595f3c0c95cd48c6 status=online rest_state=suspended
```

Sibling/control:

```text
fresh create with no prior perch: no rest_state field
explicit endpoint wake on the reproduced live row: rest_state suspended -> active
```

**W1 ownership:** successful fresh create/bind must normalize rest intent to active in the same lifecycle transition; it must not require a later explicit wake.

## 4. F-034 shape 3 — dead-owner re-pin fails after pid/parent death

**Verdict: ABSENT.** Exact isolated binary reported `spt 0.44.0`.

Evidence lines:

```text
recorded owner pid 30624: ABSENT
recorded parent pid 41248: ABSENT
spt api presence w0-repin-dead --session-id w0-new-dead-sid
exit=0
SESSION_REPIN:w0-repin-dead: dead owner (pid 30624) — re-pinned session w0-old-dead-sid -> w0-new-dead-sid (dead-owner rescue)
PRESENCE:w0-repin-dead
persisted info.json session_id=w0-new-dead-sid
```

Sibling/control: with the old owner and parent still live, a mismatched new session was refused and `info.json.session_id` remained unchanged.

**W1 ownership:** none. The dead-owner rescue and live-owner squat guard both behave as specified.

## 5. F-034 shape 4 — childless zombie shim conflicts while list says offline

**Verdict: ABSENT.** Exact isolated binary reported `spt 0.44.0`.

Evidence lines:

```text
zombie shim PID 44676 alive; child PID 44468 absent; no descendants of 44676
endpoint list: w0-zombie ... OFFLINE
rc w0-zombie: Endpoint 'w0-zombie' has a defunct session — its client process tree is gone.
endpoint run --create --start: zombie reaped; fresh session spawned; no ENDPOINT_CREATE_CONFLICT
```

Sibling/control:

```text
live shim PID 31400 -> live mock-session child PID 7412: typed create conflict
fully dead sibling root/child absent: fresh create succeeded without conflict
```

**W1 ownership:** none. Current dup-guard distinguishes childless zombie, live tree, and fully dead/no-session cases consistently with the rendered effective status.

## W0 disposition

Present and owned by W1:

1. dead relay remains `ONLINE - HARNESS ONLY`;
2. successful `run --create` leaves `rest_state=suspended`.

Absent and closed by sibling-backed evidence:

1. omp-spt shutdown survivor;
2. dead-owner re-pin failure;
3. childless-zombie false create conflict.