fix(codex): add missing closing fence in resumed-session bash block

The bash block opened at the "For a resumed session" section was missing
its closing ``` fence. Prose text with backtick-quoted identifiers (e.g.
`SESSION_ID:<id>`) was being parsed as shell code, causing bash -n to
report "unexpected EOF while looking for matching `".

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: NikhileshNanduri

codex/SKILL.md

@@ -1440,6 +1440,7 @@ elif [ "$_CODEX_EXIT" != "0" ]; then
   head -20 "$TMPERR" 2>/dev/null | sed 's/^/  /' || true
   _gstack_codex_log_event "codex_nonzero_exit" "consult-resume:$_CODEX_EXIT"
 fi
+```
 
 5. Capture session ID from the streamed output. The parser prints `SESSION_ID:<id>`
    from the `thread.started` event. Save it for follow-ups:

codex/SKILL.md.tmpl

@@ -561,6 +561,7 @@ elif [ "$_CODEX_EXIT" != "0" ]; then
   head -20 "$TMPERR" 2>/dev/null | sed 's/^/  /' || true
   _gstack_codex_log_event "codex_nonzero_exit" "consult-resume:$_CODEX_EXIT"
 fi
+```
 
 5. Capture session ID from the streamed output. The parser prints `SESSION_ID:<id>`
    from the `thread.started` event. Save it for follow-ups: