[JacobStephens2]

Summary

Building from source now says which copy of thirdshift runs when a source build sits beside the shell installer's copy, and drops the sudo … /usr/local/bin install.

 ## Building from source
   cargo install --path .              # ~/.cargo/bin
   update: git pull && cargo install --path .
-  system-wide: cargo build --release && sudo install … /usr/local/bin/thirdshift
+  installer's copy in ~/.local/bin may come first on PATH
+  see every copy, in order:  type -a thirdshift
+  run the source build:      ~/.cargo/bin/thirdshift <Issue URL>
+                             or export PATH="$HOME/.cargo/bin:$PATH" in ~/.bashrc
+  thirdshift version can't tell them apart: main reports the last released version

/usr/local/bin is always behind ~/.local/bin on a typical PATH, thirdshift update refuses to touch it, and it needs root.

Evidence

• Before: on tracewake, a build installed to /usr/local/bin had merge, but thirdshift merge <url> failed with not a GitHub issue URL: merge:

  $ type -a thirdshift
  thirdshift is /home/jacob/.local/bin/thirdshift   # installer's 0.2.0, ran
  thirdshift is /usr/local/bin/thirdshift           # source build, also said 0.2.0
  

  After: the README names this case, the type -a check, and how to put the source build first.

Merge Danger

Door: two-way

Blast Radius: docs

🤖 Generated with Claude Code