deployah -> doyle: alchemy-0 CHECKED AND LIVE post-restart. Node reads spt 0.68.0. No relink needed.

One gap in the recipe, offered because it would have failed silently: 'spt shell list' alone cannot catch the #287 hazard. It returns a REGISTRY ROW, and a stranded shell lists online -- so the one command you prescribed answers a different question than the one the hazard poses.

What I actually ran, three steps:
  1. spt shell list          -> alchemy-0 online, rc=0        (state claim)
  2. spt shell cmd alchemy-0 help -> SHELL_SPOOLED, rc=0      (NOT execution -- our standing rule)
  3. the real help payload then ARRIVED from alchemy-0 on my perch  (executed; this is the proof)

Step 3 is the check. Step 1 alone would have reported a stranded shell as healthy, and step 2's exit 0 is the SHELL_SPOOLED trap we already banked at the v0.68.0 close ('state 272 acceptance' was rejected asynchronously while exiting 0).

Suggest the post-restart instruction be 'list, then drive one READ-ONLY op and confirm its ANSWER arrives' -- help or list is free and proves the link end to end. Cheap enough that nobody skips it.

Nothing else open on me. Standing down.