Request recording in transcripts gets a new default and refuses unsafe extra-body values

What

Claude Code can write a record of each API request it sends into the session transcript, the file on disk that holds the conversation. Two things changed about that recording:

• The recording is controlled by a server-side switch, tengu_elegant_meadow. Its built-in fallback, used when no server value is present, moved from false to true. The environment variable CLAUDE_CODE_ELEGANT_MEADOW overrides the switch either way. The same switch also controls restartReplayIndex and the fork-context-ref entries written to the transcript, including sealing them when Claude Code shuts down. Nothing has been read about the state of tengu_elegant_meadow.
• If CLAUDE_CODE_EXTRA_BODY (extra settings merged into every API request) sets a field that the recorder would write into the session file, that request is now not recorded at all. Claude Code logs "Request not recorded for replay" with the reason extra_body_unrecordable. Before, the matching keys were quietly left out.

Why

Transcripts may now contain request records where they did not before, unless the server switch or CLAUDE_CODE_ELEGANT_MEADOW says otherwise. If you use CLAUDE_CODE_EXTRA_BODY, the values you inject are kept out of the session file by skipping the recording rather than writing a partial one.