fix(cli): /whoami no longer reports Unknown command in the classic CLI (salvage #26047)

[teknium1]

Summary

/whoami now dispatches in the classic CLI instead of printing Unknown command: /whoami.

Salvage of #26047 by @kronexoi (earliest of 4 independent fixes for this bug), cherry-picked onto current main with authorship preserved.

Root cause: the command exists in the shared COMMAND_REGISTRY (so it appears in /help and autocomplete on every surface), but cli.py's process_command() never had a dispatch branch for it. Refs #74594, #35892.

Changes

• cli.py: _handle_whoami_command() + dispatch branch in process_command()
• tests/cli/test_cli_init.py: regression test — /whoami must not fall through to Unknown command

Validation

	Before	After
/whoami in hermes chat	Unknown command: /whoami	prints access summary (verified live in tmux sandbox)
targeted test	n/a	tests/cli/test_cli_init.py -k whoami → 1 passed

Duplicate cluster to close on merge: #26047 (salvaged, credit), #52170 (also fixed /indicator — already fixed on main), #61416, #77920.

Infographic

[github-actions]

૮ >ﻌ< ა ci review

_{ran on 1de5414 — fix(cli): wire /whoami slash command in classic CLI}

⚠️ Warnings

OSV vulnerability scan · View job

7 known vulnerabilities found in pinned dependencies.

• CVE-2026-67213 in package-lock.json
• CVE-2026-67213 in website/package-lock.json
• CVE-2026-71554 in uv.lock
• CVE-2026-70608 in package-lock.json
• CVE-2026-56876 in package-lock.json
• CVE-2026-70606 in package-lock.json
• CVE-2026-71554 in uv.lock

How to fix:

Review the findings in the Security tab. Update the affected dependencies if a patched version is available.

---

debug info

CI timings

CI timings · View report · View job

Wall time 7m54s vs 9m28s (-16.5%). 10 job(s) slower, 10 faster, 4 unchanged.

• Python tests / Run tests slice 1/12: -42.0s
• Python tests / Run tests slice 5/12: -34.0s
• Python tests / Run tests slice 12/12: +23.0s
• Python tests / Run tests slice 9/12: -22.0s
• Python tests / Run tests slice 8/12: -21.0s