commit - 90c588541e98eb7d71db2a6fb4f2da7cf15f5143
commit + 32a9a63b07ec43fcd0d3100fadfcea52fab6ed0c
blob - 293d4950c17fbcc9aa75311535f6428d92327496
blob + e8af57475d109b5c013829db53b40a12098fc695
--- docs/release-live-checks.md
+++ docs/release-live-checks.md
@@ -74,8 +74,9 @@ exits.
 
 The Codex Tool check also isolates the Journal created by that invocation and
 requires a committed `responses-continuity` Provider-state envelope for the
-fixed profile and model. It checks only the envelope metadata; the backend's
-opaque encrypted-state bytes are neither assumed nor printed.
+fixed profile and model with a nonempty function-call identity array. It checks
+only that structural metadata; the backend's opaque encrypted-state bytes are
+neither assumed nor printed.
 
 The opt-in must run as the ordinary Owner account, never root. Record the date
 and profile identifier in the release transcript; do not record request
blob - 5e8f971090ff39eb92103d3e209588bbbda0a1dd
blob + a0d582a0446f829a8eb7822ad01aaecd3936273e
--- scripts/live-check
+++ scripts/live-check
@@ -436,10 +436,11 @@ codex_continuity_present()
 {
 	journal=$1
 	marker='"provider_state":"{\"provider\":3,\"profile\":\"chatgpt-codex-2026-07-17\",\"model\":\"gpt-5.5\",\"kind\":\"responses-continuity\",\"data\":'
+	calls_marker='\"calls\":[{'
 
 	[ -f "$journal" ] || return 1
 	grep -F '"t":"msg","role":"assistant"' "$journal" 2>/dev/null |
-	    grep -Fq "$marker" || return 1
+	    grep -F "$marker" | grep -Fq "$calls_marker" || return 1
 	grep -F '"t":"turn-end"' "$journal" 2>/dev/null |
 	    grep -Fq '"outcome":"ok"'
 }