New CLAUDE_CODE_ environment variables for startup and remote session tuning

What

Environment variables are settings passed to a program when it starts. Five new ones appear in this release. All of them are added to the lists of variables passed on to remote (CCR) sessions, next to the existing CLAUDE_CODE_CCR_* and startup-tuning names. CLAUDE_CODE_TRANSCRIPT_SLIM_TOOL_RESULTS is added to only one of the two lists.

• CLAUDE_CODE_JIT_POLICY_AFTER_STARTUP: ten seconds after startup, Claude Code always set the JIT policy of the Bun runtime to 1. The JIT policy controls how the runtime compiles code while it runs. If this variable is set, Claude Code now calls setJitPolicyAfterStartup(), which passes the variable's value (default 1) to Bun.unsafe.setJITPolicy. Without the variable, the old behaviour stays.
• CLAUDE_CODE_SETTLE_TOUCHED_FILES: a check that skips re-reading changed files Claude Code is tracking used to depend only on the gate tengu_fallow_plover, with a fallback of false. It now also turns on when this variable is true and a second check passes. What that second check tests was not worked out. For tengu_fallow_plover, the flag server returned off for this site's account and for the anonymous baseline, and no reading has been taken under this release yet.
• CLAUDE_CODE_MCP_ALWAYS_LOAD_JOIN_BEFORE_INPUT: a helper returns true only when this is exactly true, its argument is set, and a further check is false. The places that use it were not read.
• CLAUDE_CODE_CCR_WORKER_SOCKET and CLAUDE_CODE_TRANSCRIPT_SLIM_TOOL_RESULTS: these appear only in the lists, and what reads them was not traced.

Why

These are switches for tuning startup and remote sessions. Nothing in the members shows any of them is set by default. Unless you set them, behaviour stays as before.