effortLevel updates are skipped when already satisfied

What

effortLevel sets how much effort the model puts into its answers. Claude Code used to apply it every time it arrived. Now:

• Skipped when satisfied: a settings or control update that carries effortLevel is applied only if a new check on the model, the level and the engine state says it is not already satisfied. Otherwise it is ignored entirely, including the report of the change.
• apply_flag_settings: the same skip applies when a controlling program, for example over Remote Control, changes session settings this way. Before, any effortLevel was always validated and applied.
• ultracode: an effort change that arrives without an explicit ultracode value now calls a new reset step.

Why

This avoids applying the same effort level twice, for example from Remote Control. It also means some effort changes may be dropped silently, so a setting that seems to have no effect may have been judged already in place.