fix(cli): make slash-command IDE status subscription cleanup-safe

[jasonmatthewsuhari]

Summary

useSlashCommandProcessor adds and removes its IDE status listener through separate async calls to IdeClient.getInstance(). If the hook unmounts before the instance resolves, cleanup can run before registration and the listener can remain attached.

Evidence

In packages/cli/src/ui/hooks/slashCommandProcessor.ts, the effect adds the listener inside an async IIFE and removes it in another async IIFE from the cleanup function. There is no shared resolved-client state or cancellation guard tying the registration and cleanup together.

Impact

This can leak IDE status listeners and trigger redundant reloadCommands() calls after the hook has unmounted or reinitialized, especially in flows where command processors are recreated.

Expected behavior

Listener registration and removal should be coordinated by the effect so that cleanup always removes the exact listener that was successfully attached, and no listener is added after unmount.

Suggested fix

Track the resolved IdeClient instance inside the effect and gate registration on a local cancelled flag, similar to other async React subscription patterns.

[sahilkirad]

/assign

[gemini-cli]

@sahilkirad Thanks for taking interest but this issue is already assigned. We'd still love to have you contribute. Check out our Help Wanted list for issues where we need some extra attention.

[sahilkirad]

Hi @jasonmatthewsuhari , I have raised a PR in which I solved the issue and also I notified the mentor. So now what do I have to do , as it has been more than 2 days mentors have not yet replied, could you please guide me as this is my first open source contribution.