statusLine not rendering on Windows native binary (v2.1.90)

Bug Description

statusLine configuration in ~/.claude/settings.json is completely ignored on the native Windows binary (v2.1.90). Neither type: "static" nor type: "command" produce any visible output in the terminal. The status line area remains empty regardless of configuration.

Environment

• OS: Windows 10 Pro (10.0.19045)
• Claude Code version: 2.1.90 (native binary at ~/.local/bin/claude)
• Terminal: Git Bash (standalone)
• Installation method: Native installer (not npm)

Steps to Reproduce

1. Add any statusLine config to ~/.claude/settings.json:

Static (simplest case):

{
  "statusLine": {
    "type": "static",
    "content": "test"
  }
}

Command (per official Windows docs):

{
  "statusLine": {
    "type": "command",
    "command": "~/.claude/statusline.sh"
  }
}

1. Start Claude Code (claude)
2. Send any message
3. Observe: no status line appears at the bottom of the interface

Expected Behavior

Status line should render at the bottom of the Claude Code TUI, as documented at https://code.claude.com/docs/en/statusline#windows-configuration

Actual Behavior

Nothing appears. No error, no "statusline skipped" notification — just completely silent failure.

What Was Tested

| Configuration | Result |
|---|---|
| type: "static", content: "test" | ❌ Nothing |
| type: "command", command: "echo test" | ❌ Nothing |
| type: "command", command: "whoami" | ❌ Nothing |
| type: "command", command: "~/.claude/statusline.sh" (official docs example) | ❌ Nothing |
| type: "command", command: "node ~/.claude/statusline.js" | ❌ Nothing |
| type: "command", command: "bash ~/.claude/statusline.sh" | ❌ Nothing |
| type: "command" with absolute Git Bash path | ❌ Nothing |

All scripts work correctly when tested manually — correct output, exit code 0.

Additional Context

• Other settings from the same settings.json are being read (hooks, model, permissions all work)
• The settings.json is valid JSON (verified programmatically)
• disableAllHooks is not set
• Workspace trust was accepted
• This appears to be the same underlying issue as #27057 and #27161, which were closed but the problem persists on v2.1.90

Related Issues

• #27057 — statusLine command broken on Windows (v2.1.49) — closed as Not Planned
• #27161 — "Session environment not yet supported on Windows" — closed as duplicate
• #14125 — StatusLine not rendering in Windows Terminal — was fixed, but regression returned