fix(cli): correct tab completion script path resolution

[jdalton]

Summary

Fixes incorrect path to socket-completion.bash when running the CLI from built distribution.

Before: /Users/jdalton/projects/socket-cli/packages/data/socket-completion.bash ❌
After: /Users/jdalton/projects/socket-cli/packages/cli/data/socket-completion.bash ✓

Problem

When running socket install completion, the CLI failed with:

✗ Tab Completion script not found: Expected to find completion script at 
`/Users/jdalton/projects/socket-cli/packages/data/socket-completion.bash` but it was not there

The root cause was in src/constants/paths.mts:46-48. The rootPath calculation didn't account for code running from the build/ directory (in addition to dist/), causing path resolution to go one level too high (/packages/ instead of /packages/cli/).

Solution

Updated path resolution logic to check if __dirname ends with either 'dist' or 'build', correctly determining the root path in all execution contexts:

• Running from source: src/constants/ → root is packages/cli/
• Running from build: build/ → root is packages/cli/
• Running from dist: dist/ → root is packages/cli/

Changes

• Fixed rootPath calculation in src/constants/paths.mts
• Updated comments to reflect both build/ and dist/ directories
• Fixed import extensions from .mjs to .mts for consistency

Test Plan

• All 2,255 unit tests pass
• socket install completion works correctly
• socket uninstall completion works correctly
• Paths resolve correctly from both source and built versions
• Verified fix with pnpm build && node dist/index.js install completion socket

🤖 Generated with Claude Code