Status line: ULTRA never lights up — ultracode is not exposed via output_style.name #2168

Versions: LifeOS v7.40.4 (same code on main as of 2026-09-19), Claude Code 2.1.278, macOS.

What happens: with ultracode on, the status line EFFORT row stays on XHIGH; ULTRA never lights up.

Cause: LIFEOS_StatusLine.sh (around lines 1791-1794) promotes XHIGH to ULTRA only when output_style.name contains "ultracode". Claude Code never puts it there. With ultracode on, the status-line stdin carries effort.level: "xhigh" and output_style.name: "default", and the Claude Code status-line docs say: "Ultracode is not a distinct level and reports as xhigh."

Where the state does show up: in the session transcript (transcript_path in the stdin JSON):

• attachment entries "type":"ultra_effort_enter" (reminderType "full" or "sparse", repeated while ultracode stays on) and "type":"ultra_effort_exit";
• the local command output <local-command-stdout>Set effort level to ultracode (this session only): … which lands about 3 s before the first enter attachment; Set effort level to <any other level> ends it;
• workflow_keyword_request is the one-turn "ultracode" keyword opt-in, not the setting, so it should be ignored.

Suggested fix: when effort.level is xhigh, take the last of those markers in file order (skip "isSidechain":true and tool-result lines); enter or "Set effort level to ultracode" means ULTRA. A fixed-string grep keeps it cheap: about 0.2 s for a cold scan of a 16 MB transcript. Caching inode and size and rescanning only the grown tail (with a small overlap for a half-written line) brings each refresh down to about 10 ms.

Workaround in use meanwhile: a small wrapper in front of the status line reads the transcript as above and, when ultracode is on, passes output_style.name as "<name>+ultracode", so the existing check lights ULTRA without touching the file.

Thanks for LifeOS.