Remove accidental ~ directory

[mattheworiordan]

Summary

• Removes a literal ~ directory containing .npm-reshim-hook.zsh (an asdf npm reshim hook) that was accidentally committed in the initial "Add web CLI" commit (0616432)
• The shell didn't expand ~ to the home directory, so a literal directory called ~ was created in the repo instead
• This is a local dev environment artifact with no purpose in the repository

Test plan

• Verify no code references ~/.npm-reshim-hook.zsh
• Confirm it's not in .gitignore or any build config

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
cli-web-cli	Ready	Preview, Comment	Apr 2, 2026 11:25am

[cursor]

You have used all of your free Bugbot PR reviews.

To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[claude-code-ably-assistant]

Walkthrough

This PR removes a literal ~ directory that was accidentally committed in the initial "Add web CLI" commit. The shell did not expand ~ to the home directory when the file was committed, so a directory named ~ containing .npm-reshim-hook.zsh (an asdf npm reshim hook) ended up in the repository instead. This is purely a cleanup of a local dev environment artifact.

Changes

Area	Files	Summary
Other	~/.npm-reshim-hook.zsh	Deleted accidental local dev artifact (asdf npm reshim hook) committed as a literal ~ directory

Review Notes

• No code impact: This deletion removes only a local dev environment artifact with no references in code, build config, or .gitignore.
• Root cause: The ~ was not shell-expanded when the file was staged, creating a literal directory named ~ in the repo root.
• No test coverage needed: Pure deletion of an extraneous file — no behavior changed.

[sacOO7]

Security audit started failing today, seems vulnerability for the same was posted some hours ago.
As per info, The lodash vulnerability advisory (GHSA-r5fr-rjxr-66jc, GHSA-f23m-r3pf-42rh) was likely published between Apr 1-2, or the oclif update pulled in a lodash version that now matches a newly-flagged advisory.

[mattheworiordan]

Security audit started failing today, seems vulnerability for the same was posted some hours ago.

Ok, so what are you suggesting here. This PR has nothing to do with that security issue.