Custom statusline doesn't refresh after /rename

Description

After running /rename to change the session name, the custom statusline does not refresh to show the new name. The session name only updates on the next assistant message or other qualifying event (permission change, vim toggle).

The built-in prompt bar updates the session name instantly, but the custom statusline subprocess is not re-invoked after /rename.

Steps to Reproduce

1. Configure a custom statusline that displays session_name from the stdin JSON
2. Run /rename my-new-name
3. Observe: the built-in prompt bar shows "my-new-name" immediately
4. Observe: the custom statusline still shows the old session name
5. Send any message to trigger an assistant response
6. Observe: the custom statusline now shows "my-new-name"

Expected Behavior

The custom statusline should re-render immediately after /rename, just like it does after /model (fixed in v2.1.86).

Precedent

v2.1.86 fixed "statusline showing another session's model when using /model" — the same fix (triggering a statusline re-render after the local command) should be applied to /rename.

Ideally, all display-affecting local commands (/rename, /color, /model) should trigger a custom statusline refresh.

Environment

• Claude Code v2.1.86
• Windows 11
• Custom statusline using statusLine.type: "command" in settings.json