Overmind won't start if directory name results in Tmux socket name being too long

[boardfish]

system  | Tmux socket name: overmind-origin-legacy-react-refactor-on-table-load-controller--4rBA9yZftMp6wMpAH-FH
system  | Tmux session ID: origin-legacy-react-refactor-on-table-load-controller
system  | Listening at ./.overmind.sock
error connecting to /private/tmp/tmux-501/overmind-origin-legacy-react-refactor-on-table-load-controller--4rBA9yZftMp6wMpAH-FH (File name too long)
overmind: Tmux client unexpectedly exited

Seeing this on Overmind v2.5.1 (installed via Brew) on an M4 MacBook Pro, running macOS Sequoia 15.7.1. The issue goes away if I remove origin- from the start of the filename.

I'm encountering this now because I'm starting to use Git worktrees, where the created folder will be named after the branch by default. This has the potential to result in some pretty long folder names.

Not familiar with Overmind's internals, but I would suggest that if we set the socket name using the -L flag, we truncate the folder name to make room for the identifier on the end.

[boardfish]

I've found an interim fix for this, which is to truncate the name of the current directory yourself:

overmind start --title="$(basename "$PWD" | cut -c1-40)"

But it would be good to bake this into Overmind as functionality.