statusLine configuration not working in Claude Code 2.1.1

Environment

• Version: Claude Code 2.1.1
• Platform: macOS (Darwin 25.2.0)
• Terminal: Standard macOS Terminal

Issue Description

The statusLine setting in ~/.claude/settings.json is completely ignored. Commands configured in the statusLine are never executed.

Configuration Tested

Multiple configurations were tested in ~/.claude/settings.json:

Simple test command:

{
  "statusLine": {
    "type": "command",
    "command": "printf 'TEST STATUS LINE'"
  }
}

Diagnostic command with logging:

{
  "statusLine": {
    "type": "command",
    "command": "{ date '+%Y-%m-%d %H:%M:%S.%3N' >> /tmp/claude-statusline-debug.log; echo '--- EXECUTION DETECTED ---' >> /tmp/claude-statusline-debug.log; printf 'TEST'; }"
  }
}

Expected Behavior

• The command should execute when Claude Code starts
• The output should appear in the status line area (bottom of terminal)
• For the diagnostic command, a log file should be created at /tmp/claude-statusline-debug.log

Actual Behavior

• No status line appears anywhere in the interface
• Commands are never executed (confirmed via diagnostic logging that would create a file)
• The log file /tmp/claude-statusline-debug.log is never created, proving the command never runs
• Only vim mode indicators (e.g., "-- INSERT --") appear in the status area when vim mode is enabled

Steps to Reproduce

1. Add statusLine configuration to ~/.claude/settings.json
2. Restart Claude Code completely
3. Check for status line output (none appears)
4. For diagnostic test: check if /tmp/claude-statusline-debug.log exists (it doesn't)

Verification Done

• ✅ JSON syntax is valid (verified with jq)
• ✅ No conflicting managed settings files
• ✅ Tested with vim mode both enabled and disabled
• ✅ Tested with and without trailing newlines
• ✅ Commands work correctly when executed manually in shell
• ✅ Diagnostic logging confirms commands are never executed by Claude Code

Additional Context

The statusLine configuration appears to be defined in Claude Code's settings schema but is not being read or executed at runtime. This may be a feature that's partially implemented or disabled in version 2.1.1.