1.19.0 - it said xhigh because ultracode IS xhigh

1.19.0 - it said xhigh because ultracode IS xhigh, and nothing on disk says which

Reported as "the usage thingy still thinks I'm on xhigh and not ultra". The
plugin was not misreading anything. Claude Code's own words, out of its binary:
"ultracode: xhigh + dynamic workflow orchestration (this session only)".

So ultracode is not a sixth effort level. It is xhigh effort plus workflow
orchestration, and it is session-scoped: settings.json keeps effortLevel at
xhigh, every one of this session's 971 transcript lines records effort xhigh,
and neither can name the MODE because the mode is never written down. Both
sources were right and neither could answer the question.

usage.effortNow() is the chain, and every reading says where it came from,
because xhigh from a stale settings file and xhigh from a live override deserve
different confidence:

1. CLAUDE_CODE_EFFORT_LEVEL - Claude Code's own session override, which hooks
   inherit, so it is live and authoritative.
2. An override recorded here by hand - the workaround for the one case
   nothing can see, /effort ultracode typed in the session.
3. settings.effortLevel - the persisted default.
4. The transcript - stamped at session start and never re-stamped.

node scripts/usage.js --effort              what it reads, and from where
node scripts/usage.js --effort ultracode    tell it what the picker did
node scripts/usage.js --effort clear        forget it

A hand-set override expires after twelve hours, because it describes one
session and left lying around it would outlive the thing it was true for. A
value that is not a real level is refused rather than stored.

634 tests.

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com