[John-David Dalton (jdalton)]

Show users the supported socket wrapper off command after enabling the shell wrapper, so the instructions actually remove the aliases.

Implementation and validation

A real CLI process test enables and disables the wrapper using temporary home, configuration, and shell-profile files, then checks that both aliases are removed.

Validation: build:cli, the wrapper integration suite (four tests), type:cli, and scoped lint passed.

Automated review notes

---

[!NOTE]
Low Risk
User-facing copy fix and test coverage only; no change to wrapper enable/disable behavior beyond messaging.

Overview
Updates the post-enable success message so users are told to run socket wrapper off instead of the unsupported socket wrapper --disable, matching the documented on / off subcommands.

Adds an integration test that runs wrapper on and wrapper off against a temporary home and shell profile: it asserts the CLI output shows the correct disable command, and that npm / npx aliases are written to the profile on enable and removed on disable.

^{Reviewed by Cursor Bugbot for commit 1d6acaa. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{Bugbot Autofix is ON, but none of the reported issues met your autofix severity threshold.}

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 1d6acaa. Configure here.}