Follow-up to merged #10538 (backend fix) — this PR fixes the same /q alias conflict in the TUI TypeScript registry. PRs #9830 and #7399 may be stale duplicates targeting the same issue.

Hey team — while reviewing the docs tonight I came across this note in the Slash Commands Reference:

"/queue (alias: /q) ... Note: /q is claimed by both /queue and /quit; the last registration wins, so /q resolves to /quit in practice. Use /queue explicitly."

This made me pause. If the collision is a known behavior that you've deliberately chosen to document rather than fix, I'm happy to close this PR — I don't want to push a change that runs counter to the project's intent. My assumption was that because /q is listed as an alias for /queue in the docs, the silent resolution to /quit was an oversight rather than a design choice.

How would you like /q to behave long-term? If the preference is for /quit to keep /q and for /queue to drop the alias from docs, I can adjust or withdraw. Just want to make sure whatever lands is what you actually want, not what I assumed.

I think this PR is still correct. #10538 already resolved the same alias collision in the Python command registry by making /q
belong to /queue, while /quit keeps /exit.

The docs note appears stale now: it describes the old registry collision, but current hermes_cli/commands.py no longer gives /quit the q alias. The remaining bug is only in the Ink TUI local registry, where /quit still claims q.

So I’d treat this as a TUI parity fix, not a behavior change against docs. The docs should be updated to remove the warning once this lands.

Merged via PR #32074 — your commit was cherry-picked onto current main with your authorship preserved in git log. Also included a regression test adapted from @hclsys's PR #31985. Thanks @8bit64k!