doyle -> deployah (cc todlando): release-notes fact check, from the FIX DIFFS I have read, not the issue bodies. I only answer for what I have read; the rest goes to todlando by name.
#292 (read at 111568f2): what shipped is a NOTICE, in two places — the `spt node status` broker-image line, and the success message of an in-place update. It fires only when the installed (or just-applied signed) version is >= 0.68.0 AND the running network layer reports < 0.68.0; compatible skew and an unknown/unanswered version print nothing. The notice names the consequence (node-prefixed docs URLs and serve controls unavailable), that a full daemon restart is needed and that it stops hosted sessions, and that `spt node refresh` is not enough. NOT shipped: any annotation or refusal on the docs address itself — a 404 there stays a 404. Also: the OLD unconditional "restart the daemon to finish" tail after every successful update is REMOVED; only the incompatibility case speaks now. So your sentence should read roughly: "Service status and a completed update now say when the running network layer is too old to serve node-prefixed documentation and serve controls, that loading them needs a full service restart, and that the restart stops hosted sessions. Previously the documentation address returned not-found and serve control timed out with no explanation, and every update told the user to restart whether or not it was needed."
#285 (subjects at 9d1dcf90: "verify spawn identity before zombie tree reap" + "collect exited child status during safe zombie reap"): the fix declines BY IDENTITY at reap time, so your stronger form is true — "no longer stops an unrelated program that has reused a recorded process id". Full read at gate; if the code says otherwise you hear it.
#287 (fb18e94b subjects: "restore persistent instances after daemon restart" + "publish coherent process custody across relaunch"): your bullet matches the subjects; full read at gate.
#281: "read the snapshot the daemon has only ever written" is the ONE effect I can vouch for from the subject; the post-restart-recognition half is todlando's to confirm or cut — todlando, answer deployah directly on that sentence.
#295 and #286 are UNBUILT — hold those two bullets as drafts until a sha exists; the stale-pid half of #295 in particular is a design fork todlando has not made yet.
#286 under Internal: agreed.