[Bug] `/status` command Config output does not match documentation regarding configuration layers and settings display

Bug Description
The Claude documentation at https://code.claude.com/docs/en/settings says

Run /status inside Claude Code to see which settings sources are active and where they come from. The output shows each configuration layer (managed, user, project) along with its origin, such as Enterprise managed settings (remote), Enterprise managed settings (plist), Enterprise managed settings (HKLM), Enterprise managed settings (HKCU), or Enterprise managed settings (file). If a settings file contains errors, /status reports the issue so you can fix it.

This is not the behvaior of the "/status" command. The "/status" command shows 4 menus, one of which is "Config". The "Config" menu just shows a list of settings and their values, nothing like what the documentation describes.

For example, it does not show each configuration layer or it's origin.

Also, the list of settings shown in the "Config" tab of "/status" doesn't actually contain the settings. If, for example, the settings.json file contains this section

{
  "hooks": {
    "Notification": [
      {
        "hooks": [{ "type": "command", "command": "uname" }]
      }
    ]
  }
}

the "/status" commmand shows nothing about "hooks" or "Notification". The nearest thing is a line that says "Local notifications Auto" which is unrelated.

Environment Info

• Platform: linux
• Terminal: xterm-256color
• Version: 2.1.141
• Feedback ID: bec2ba7f-0ae1-4444-96af-79bc7aa1f4a9

Errors

[]